Backup forum

It is a good idea to understand the language in which Idrives speaks to you. Here are a few things IDrive support told me. Support are not necessarily 100% correct, and I may have slightly misunderstood. But hopefull the info will be be a starting point for clarification.


IDrive will log the backup as a failure if x% of files present in the backup set (IDrive's list of files to backup) are not found on your hard disk when the backup is run


IDrive will log the backup as a failure if x% of files present in the backup set (IDrive's list of files to backup) fail to backup, either because they are missing or for some other reason, when the backup is run

Niether value can be set to 0% or unticked. Not even in the settings text file. This is 'by design' according to IDrive.


This is the setting that tells IDrive how frequently to update it's backup set. You can also request an immediate update. After such an update if you run a backup there should be no or very few missing files. (It does not check that all files on your disk have backed up correctly).


In summary log. According to IDrive support. This means that an open file could not be backed up because Windows volume shadow copy could not take a copy of it, or the copy is corrupt. The previous version has been retained. (This happens I understand when the file is being written to pretty continuously). [I wonder if this is the full story. Maybe IDrive takes a local copy, either via VSS or otherwise. If this copy does not have the same hash as the original file it decides not to upload it. This may happen for a number of reasons including the file being written to]

Last edited by Mouse (2018-05-19 12:25:55)