If a scheduled backup cant run (ie computer switched off) is it set to run as soon as it can?

Does the scheduled backup check a file to decide whether to upload? What are these checks? (file date/size or md5 checksum etc)

Are these same checks used for real time backups?

Thanks!

>> If a scheduled backup cant run (ie computer switched off) is it set to run as soon as it can?

Yes. It is. Please make sure you have the latest version Online Backup build 248.

>> Does the scheduled backup check a file to decide whether to upload? What are these checks? (file date/size or md5 checksum etc)

All of these are checked to determine if the file needs to be uploaded again. Even if the physical file has not been changed in the case of "MagicCode" match, the file date on server is still updated but upload is skipped.

>> Are these same checks used for real time backups?

All DriveHQ Client software (FileManager, Desktop Express, Online Backup) uses the same advanced caching, date-time comparison and MagicCode comparison. MagicCode is a proprietary version of MD5 and is generally much more secure than MD5.

Thanks for the answers!

I have a problem in that I have a TrueCrypt file (encrypted mounted drive) that doesnt change size or change its date when you write to the drive (a fixed size file is allocated on creation) and I'm guessing MagicCode isnt picking up the changes so the latest file isnt being backed up.

Have you come accross this before? Is there anything I can do to ensure its backed up?

Well, I believe our backup program checks the file time and file size before it re-computes the MagicCode. If the file time and size never changes, it will assume the file has not been updated. I am surprised that TrueCrypt doesn't update file size and file date... It seems we need to do some tweak on this. Please also check if you can configure it so that it changes the file time.

Hi, Okay you can make truecrypt change the file modification date on modifications. Although this does limit the functionality of the program. ("plausible deniability" of modification). (Goto Truecrypt preferences uncheck "preserve timestamps") The accessed date does change when the drive is mounted - maybe this gives you an easy tweak to make to catch truecrypt mods. Although this could of course mean transfers are made (of what are reasonable large files as they're mounted drives) when no data has changed (ie the file's been mounted to retrieve data only). Maybe one for a configuration option & documentation. Or perhaps regular forced backups for some files could be allowed. Thanks PS I've tried this and it seems to work although I'm concerned the file modification timestamp isnt enough to push the upload (ie can magiccode overrule if it finds no changes?)