BUG: Not backing up TrueCrypt files
 

SuperDuper isn't backing up my TrueCrypt files on OS X 10.5.8.

They range in size from 30MB to 2GB. SuperDuper is not backing them up after I modify the contents.

They aren't locked, they don't have special permissions, and I don't have a copy script accidentally excluding them.

I *think* this is happening because the first few kilobyters of a Truecrypt file are always the same regardless of the contents (holding the encryption headers), and SuperDuper checks to see if a file is modified by comparing the first few kilobytes of the 2 files. Since the headers do not change, SuperDuper is assuming the files have not changed.

My guess is that you have an option set in TrueCrypt to not update the "container's" dates when the contents are modified. Without a change to either the dates, sizes, metadata etc, the files won't be copied.

Oh I feel silly now.
I just unchecked the option, I'll see if that helps.
Thanks.

OK, it seems to be backing them up now, but the MD5 hashes still don't match. Can you think of any reason that may be?

Are they open or closed on the source? We're just copying the files with standard calls, Jethryn...

Sorry, just a silly mistake by me. I have mounted the image before opening it which changed the access time.

Everything is working fine.

Good, glad to hear it. Certainly would have been a surprise to hear otherwise! :)