Don Lee Posted March 13, 2013 Report Share Posted March 13, 2013 I ran an experiment (what and why is not important here) where I copied a backup set, and got an error. + Executing copy_set at 3/13/13 (Activity Thread 2) To Backup Set atrash... - 3/13/13 12:01:40 AM: Transferring from v9_daily_mercy_last 3/13/13 12:42:27 AM: Execution completed successfully Completed: 503 files, 59.2 GB Performance: 1,559.8 MB/minute Duration: 00:40:46 (00:01:52 idle/loading/preparing) - 3/13/13 12:42:27 AM: Verifying atrash !Generated MD5 digest for file "/Volumes/backup/d.root.130212.gz" does not match stored MD5 digest. 3/13/13 12:58:45 AM: 1 execution errors Remaining: 1 files, 0 B Completed: 502 files, 59.2 GB Performance: 3,887.5 MB/minute Duration: 00:16:18 (00:00:42 idle/loading/preparing) I then ran a verify on the source set, and the verify came through clean. I then turned on "verify entire media set" on a verify script, and it came through clean. I then ran the copy again, to see if the MD5 error was a transient of some kind. Nope. What does "verify" do, if not check things like the MD5 digests? What does "verify entire media set" do? I'm not sure, but I think there is a bug in here somewhere. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.