cfieldgate Posted March 15, 2014 Report Share Posted March 15, 2014 Hi, I am in the process of updating the hardware of my backup storage server and as a consequence the backups stored there will be lost. In preparation for this I ran a Transfer Backup Set operation (Retrospect v8.5) to a new Backup set stored elsewhere. I had one execution error relating to one file of this ~3TB data set (RAW format photographs): + Executing Backup Set Transfer at 26/02/2014 22:09 To Backup Set Backup - Archive... - 26/02/2014 22:09:32: Transferring from Krusty - Archive 26/02/2014 22:13:08: Execution completed successfully Completed: 1 files, 12.0 MB Performance: 3.3 MB/minute Duration: 00:03:35 (00:00:01 idle/loading/preparing) - 26/02/2014 22:13:08: Verifying Backup - Archive Generated MD5 digest for file "\\KRUSTY\Archive\Image Archive\2007\Dorset\2007-11-27\Card 2\_Y1U1169.CR2" does not match stored MD5 digest. 26/02/2014 22:13:09: 1 execution errors Remaining: 1 files, 12.1 MB Completed: 0 files, zero KB Performance: 0.0 MB/minute Duration: 00:00:01 I then ran a backup from the source data to the new Backup Set and the missing file was backed up. + Normal backup using zBackup - Archive at 27/02/2014 05:30 To Backup Set Backup - Archive... - 27/02/2014 05:30:39: Copying Archive on krusty 27/02/2014 05:46:42: Snapshot stored, 68.6 MB 27/02/2014 05:46:49: Comparing Archive on krusty 27/02/2014 05:47:00: Execution completed successfully Completed: 1 files, 12.0 MB Performance: 84.7 MB/minute (120.0 copy, 72.0 compare) Duration: 00:16:20 (00:16:03 idle/loading/preparing) As I am curious, and not because it really matters (the original Backup Set will be lost - hence the Transfer) I then ran a Verify operation on the original Backup Set and the error was again reported. + Executing Krusty - vArchive at 14/03/2014 06:31 - 14/03/2014 06:31:27: Verifying Krusty - Archive Generated MD5 digest for file "\\KRUSTY\Archive\Image Archive\2007\Dorset\2007-11-27\Card 2\_Y1U1169.CR2" does not match stored MD5 digest. 15/03/2014 01:51:55: 1 execution errors Remaining: 1 files, 1.1 GB Completed: 428617 files, 3,444.0 GB Performance: 3123.0 MB/minute Duration: 19:20:28 (00:31:14 idle/loading/preparing) 1 files were not verified Total duration: 19:20:30 (00:31:14 idle/loading/preparing) 15/03/2014 01:51:56: Script "Krusty - vArchive" completed with 2 errors Interestingly, the file size (apparently) reported is much larger (1.1GB vs. 12MB). I don't know why. However, when I ran a subsequent backup to this (original) Backup Set the missing file was not backed up (the subsequent backups to both Backup Sets show the same files were backed up and not the missing file - also checked by Browsing the relevant Sessions). Why is this? Since Retrospect now knows there is a read error for one file why does the next backup not correct for this? Do I need to Groom the original Backup Set to force the backup of the missing file? 1 Quote Link to comment Share on other sites More sharing options...
cfieldgate Posted March 25, 2014 Author Report Share Posted March 25, 2014 Is there anyone out there? Mayoff? Quote Link to comment Share on other sites More sharing options...
Scillonian Posted March 25, 2014 Report Share Posted March 25, 2014 Have you tried a full catalog rebuild? This may help to prove if the error lies in the catalog file or one or more of the .RDB files is damaged. (With a backup set of ~3TB and depending on the transfer speed of your NAS this could take a long time — the ~1.2TB backup set on my NAS takes ~6 hours to rebuild.) I expect grooming would fail a some point because of the error. Try a catalog rebuild before trying to groom. With a damaged catalog file Retrospect can do some strange things which explain the backup inconsistencies. Quote Link to comment Share on other sites More sharing options...
cfieldgate Posted March 26, 2014 Author Report Share Posted March 26, 2014 Have you tried a full catalog rebuild? This may help to prove if the error lies in the catalog file or one or more of the .RDB files is damaged. (With a backup set of ~3TB and depending on the transfer speed of your NAS this could take a long time — the ~1.2TB backup set on my NAS takes ~6 hours to rebuild.) I expect grooming would fail a some point because of the error. Try a catalog rebuild before trying to groom. With a damaged catalog file Retrospect can do some strange things which explain the backup inconsistencies. Scillonian, Thanks - a good suggestion which I will try - although the Verify too long enough! 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.