rsinsheimer

Just updated from 7.6 to 7.7, hoping this issue was fixed, but no. I have >700 GB of photographs in uncompressed form (TIFs and PSDs) that I back up with Retrospect. These are highly compressible file formats -- if you .zip one of these they'll drop to 1/4 the size -- or less. For whatever reason, when I turn on compression in Retrospect the saved size of the data set goes up about 30%. Does anyone have any idea why that might be, and if there's a work-around? While backup space these days is relatively cheap, I'd rather not have to add more drives (I'm backing up onto a 1TB external USB drive, if that makes any difference) as the data set gets bigger. -- Roger

According to the software, thorough verification is on. I re-sync'd the volume, and did get rid of one error relative to before, here's today's report: - 2/2/2009 6:13:02 AM: Copying Photos on media on Nas-01-72-c2 2/2/2009 6:20:09 AM: Snapshot stored, 4,247 KB 2/2/2009 6:20:11 AM: Comparing Photos on media on Nas-01-72-c2 File "\\NAS-01-72-C2\media\Photos\Shollenberger Nov 05\Working\Printing\Sunrise at Shollenberger.psd": didn't compare An error occurred during the verification step. The MD5 digest for the file "\\NAS-01-72-C2\media\Photos\Shollenberger Nov 05\Working\Printing\Sunrise at Shollenberger.psd" did not match, error -1129 (MD5 digest mismatch) An error occurred during the verification step. The MD5 digest for the file "\\NAS-01-72-C2\media\Photos\Shollenberger Nov 05\Working\Printing\Sunrise at Shollenberger.psd" did not match, error -1129 (MD5 digest mismatch) An error occurred during the verification step. The MD5 digest for the file "\\NAS-01-72-C2\media\Photos\Shollenberger Nov 05\Working\Printing\Sunrise at Shollenberger.psd" did not match, error -1129 (MD5 digest mismatch) 2/2/2009 6:20:27 AM: 4 execution errors Completed: 8 files, 450.9 MB Performance: 1202.3 MB/minute (932.8 copy, 1803.5 compare) Duration: 00:07:25 (00:06:39 idle/loading/preparing) Is it normal behavior for Retrospect to try three times to get the MD5 digest to match? That seems like a good thing, but apparently this is a "real" error, whatever that means in this context. Would it make sense to copy the problem file to another location, delete it in the current location, then put it back? Since I have no understanding of what this error means, I have no clue how to resolve the problem. :rollie:

Bump. Any suggestions anyone?

Here's this morning's report: - 1/19/2009 6:01:52 AM: Copying Photos on media on Nas-01-72-c2 1/19/2009 6:07:48 AM: Snapshot stored, 4,213 KB 1/19/2009 6:07:51 AM: Comparing Photos on media on Nas-01-72-c2 File "\\NAS-01-72-C2\media\Photos\Petaluma\Turning Basin 1_18_09\YU0V0334.CR2": didn't compare File "\\NAS-01-72-C2\media\Photos\Shollenberger Nov 05\Working\Printing\Sunrise at Shollenberger.psd": didn't compare An error occurred during the verification step. The MD5 digest for the file "\\NAS-01-72-C2\media\Photos\Shollenberger Nov 05\Working\Printing\Sunrise at Shollenberger.psd" did not match, error -1129 (MD5 digest mismatch) An error occurred during the verification step. The MD5 digest for the file "\\NAS-01-72-C2\media\Photos\Shollenberger Nov 05\Working\Printing\Sunrise at Shollenberger.psd" did not match, error -1129 (MD5 digest mismatch) File "\\NAS-01-72-C2\media\Photos\Southwest 2000\Roll #01\Working #15 (Turning leaves and red rocks, soutern Utah).tif": didn't compare An error occurred during the verification step. The MD5 digest for the file "\\NAS-01-72-C2\media\Photos\Southwest 2000\Roll #01\Working #15 (Turning leaves and red rocks, soutern Utah).tif" did not match, error -1129 (MD5 digest mismatch) An error occurred during the verification step. The MD5 digest for the file "\\NAS-01-72-C2\media\Photos\Southwest 2000\Roll #01\Working #15 (Turning leaves and red rocks, soutern Utah).tif" did not match, error -1129 (MD5 digest mismatch) File "\\NAS-01-72-C2\media\Photos\Southwest 2000\Roll #02\Working #3A.tif": didn't compare 1/19/2009 6:09:44 AM: 8 execution errors Completed: 109 files, 2.2 GB Performance: 1058.9 MB/minute (965.4 copy, 1172.3 compare) Duration: 00:07:51 (00:03:42 idle/loading/preparing) I haven't touched any of those files in the last day. I am unclear why the same file would show up with an error twice -- does this mean the Retrospect tried a second time? -- Roger

7.6.123 . Today's backup had 87 MD5 errors on the server, 7 on the OS drive.

Not really sure what to do about this error. It's showing up not only on my server that I'm backing up, but also on my RAID 1 OS drive. I'm running Vista Home Premium, if that's signficant. On the OS drive I'm getting 2 or 3 MD5 errors, on the server 6 or 7. This wouldn't be such a huge deal, except that some of the files that are showing this error are almost 1 GB in size, so having Retrospect re-back them up over and over again eats up space bigtime on the backup drive. The Vista OS computer is new -- on my XP computer which I recently replaced, I never had these errors.