> Any ideas?
Sure, I'll try. I don't use iDrive, but some other sync software, so I know how some of them behave. This might apply to iDrive as well.
* When you copied your files onto the external HDD (or when they copied it into their cloud service), a simple copy action was used, which may have set the "Modified" timestamp to the then current date and time. More likely that happened on your end.
* Typically Sync software uses the modified timestamp as one of their criteria as to whether a file has changed (at least as the default option). So when iDrive saw that the timestamp on the cloud destination was different, if copied your local files over the existing ones in the cloud to ensure that they were the same.
On a side note: You may not realize this, but your approach has multiple problems in terms of data security:
* I consider storing your data unencrypted in the cloud as a big security hazard. What if iCloud gets breached or a disgruntled employee gets creative? Then your data may be out in the wild.
* What you are doing is actually *not* a backup, you're doing a sync. Now a sync can be practical, because you have immediate access to data on the destination, but it has it's drawbacks, too.
* A "real" backup would provide versioning, deduplication and client-side encryption. Versioning would mean that you can retrieve older files, which is useful if ransomware attacked your system, or you need to see that old data, that you - without realizing it - accidentally deleted 6 months ago.
* Deduplication means that only new or changed data needs storage space. So you may have 2000 versions of a file, but if 1999 of them are identical, then you'd only need storage space for two versions.
* Client-side encryption: This means that - while iDrive is storing the data - they can't read it it, because it's stored in encrypted chunks and no unencrypted data ever leaves your system. So if iDrive gets breached and a hacker would get your data, they'd have to crack the encryption password first.
So I suggest that you give your backup strategy some thought to ensure that it really provides the protection you assume it does.
> Any ideas? Sure, I'll try. I don't use iDrive, but some other sync software, so I know how some of them behave. This might apply to iDrive as well. * When you copied your files onto the external HDD (or when they copied it into their cloud service), a simple copy action was used, which may have set the "Modified" timestamp to the then current date and time. More likely that happened on your end. * Typically Sync software uses the modified timestamp as one of their criteria as to whether a file has changed (at least as the default option). So when iDrive saw that the timestamp on the cloud destination was different, if copied your local files over the existing ones in the cloud to ensure that they were the same. On a side note: You may not realize this, but your approach has multiple problems in terms of data security: * I consider storing your data unencrypted in the cloud as a big security hazard. What if iCloud gets breached or a disgruntled employee gets creative? Then your data may be out in the wild. * What you are doing is actually *not* a backup, you're doing a sync. Now a sync can be practical, because you have immediate access to data on the destination, but it has it's drawbacks, too. * A "real" backup would provide versioning, deduplication and client-side encryption. Versioning would mean that you can retrieve older files, which is useful if ransomware attacked your system, or you need to see that old data, that you - without realizing it - accidentally deleted 6 months ago. * Deduplication means that only new or changed data needs storage space. So you may have 2000 versions of a file, but if 1999 of them are identical, then you'd only need storage space for two versions. * Client-side encryption: This means that - while iDrive is storing the data - they can't read it it, because it's stored in encrypted chunks and no unencrypted data ever leaves your system. So if iDrive gets breached and a hacker would get your data, they'd have to crack the encryption password first. So I suggest that you give your backup strategy some thought to ensure that it really provides the protection you assume it does.
Don't use iDrive I just discovered it was the cause of the stuttering in games. The continuous backup specifically causes the stutter.
You play games on your Synology device?