readwrite Posted October 28, 2008 Report Share Posted October 28, 2008 Hi, I'm getting the following errors when running a snapshot transfer from a disk backup set to tape. Its alwayes at the same point in the set and the hex numbers are the same reported for the last two nights Bad Backup Set header found (0x030000fd at 730,170,833) Bad Backup Set header found (0x05000005 at 730,170,878) Bad Backup Set header found (0x030000fd at 730,170,892) Bad Backup Set header found (0x0106002b at 730,170,908) Bad Backup Set header found (0x0100002b at 730,170,924) Bad Backup Set header found (0x070000fd at 730,170,947) Bad Backup Set header found (0x030000fd at 730,170,977) Bad Backup Set header found (0x2f030000 at 730,171,122) Bad Backup Set header found (0x8b050800 at 730,171,140) Bad Backup Set header found (0x6e202d20 at 730,171,545) Bad Backup Set header found (0x9ff3fdba at 730,171,634) Bad Backup Set header found (0xd6baeedf at 730,171,653) Bad Backup Set header found (0xbabfd7fd at 730,171,679) Bad Backup Set header found (0xdd3af7fb at 730,171,701) Bad Backup Set header found (0xffffffff at 730,172,072) Bad Backup Set header found (0x10001200 at 730,172,084) Bad Backup Set header found (0x8006ff93 at 730,172,102) Bad Backup Set header found (0x0914120a at 730,172,680) Bad Backup Set header found (0xb1ff00d0 at 730,172,761) Bad Backup Set header found (0xfcb77a32 at 730,172,842) Bad Backup Set header found (0x4817213a at 730,174,225) Bad Backup Set header found (0x0350744d at 730,174,243) How do I fix this ? Do I need to recycle the disk set or can I get away with running some kind of fix job ? Thanks Richard. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted October 28, 2008 Report Share Posted October 28, 2008 It sounds like bad data on your backup. Do you see the errors during a tools>Verify? Do you use verification during the backup? The errors are pointing to specific spots inside the backup being unreadable. The files located at those positions are not being transfered correctly because they probably didn't get backed up correctly. Quote Link to comment Share on other sites More sharing options...
readwrite Posted October 28, 2008 Author Report Share Posted October 28, 2008 Hi, thanks for the reply. I'm running a verify job now, we don't usually run a verify in our backup job. We have another backup set on the same disk. When the transfer snapshot job ran this morning for this backup set the error 'Backup Set format inconsistency (9 at 3)' was logged. The only other change I did recently was to change the percentage of disk space allocated to these two sets. Originally they where set 50:50, changed to 55:45. Could this have caused the problem ? Regards Richard. Quote Link to comment Share on other sites More sharing options...
readwrite Posted October 28, 2008 Author Report Share Posted October 28, 2008 Ok, verify job showed 23 files failing to verify, remaining 30 files 538.5mb completed 407.8GB. So it looks like the backup set is corrupt. I've decided to recyle both sets. Could this problem have been caused by altering the backupset size ? There was free space in both backup sets when I changed the setting. Regards Richard. Quote Link to comment Share on other sites More sharing options...
readwrite Posted October 29, 2008 Author Report Share Posted October 29, 2008 All resolved by recycling the two disk back sets. I think the errors where probably caused after resizing the backup sets. Bug in Retrospect ? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted October 29, 2008 Report Share Posted October 29, 2008 I don't know what "resizing the backup set" means. No bug in Retrospect causes those errors. If verification was on during the original backup, Retrospect would have notified you that the backup failed. Quote Link to comment Share on other sites More sharing options...
readwrite Posted October 29, 2008 Author Report Share Posted October 29, 2008 Select properties for the backup set, then select members, and then properties for the member. I then adjusted the size of the member there, one set I reduced to 45% of disk volume size, the other set I increased to 55% of the disk volume size. Both sets reported free space before doing this. Not sure if it was the cause, however its the only change that was made before we started getting the errors. Will monitor to see if the problem comes back. Regards Richard. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted October 29, 2008 Report Share Posted October 29, 2008 Changing the space allowed for a member can not cause this error. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted October 29, 2008 Report Share Posted October 29, 2008 Changing the space allowed for a member can not cause this error. Assuming that the filesystem integrity is OK. 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.