lunadesign Posted July 14, 2014 Report Share Posted July 14, 2014 I have a friend with an older system that's still using Retrospect Professional 7.6.123. It appears he accidentally corrupted at least one of the RDB files in his local disk backup set (only has 1 member) by forcefully shutting down Retrospect a few days ago when it seemed to be hung.The nightly local backups continued to work on subsequent nights but when he tried to do his weekly snapshot transfer, it failed with Retrospect re-asking for the backup set media for the local backup (the source in the snapshot transfer).I ran "Verify Media" on the local set and near the end of the session, it started re-asking for the backup media (just like above). When I clicked "Choices" and then "Browse", it became clear that it was looking for a certain RDB file. The file is still on the disk but when I select it, Retrospect says "This file is corrupted or does not belong to this Backup Set". The file's timestamp is pretty close to when the forceful shutdown happened so I'm not surprised this file is corrupted.However, I don't see any option to skip this file (and thus abandoning any data within it) so I'm not sure what to do. It's also possible that at least one other RDB file written around the same time is also corrupted but I don't know how to get past this file to check the rest.Should I delete the corrupt RDB file and recatalog? Will recatalog be smart enough to skip any other bad RDB files? Or should I delete the backup sessions from that day in the hopes that it prunes out the bad RDB files? In any of these cases, will Retrospect be smart enough to re-backup the files that were in the corrupt RDB file (assuming they didn't subsequently change and get backed up on a later date)?Thanks in advance! Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 14, 2014 Report Share Posted July 14, 2014 You should move the corrupt RDB file to another folder, in case you might need it. Then do a recatalog. Yes, Retrospect is smart enough the re-backup the missing files from the source computer. Quote Link to comment Share on other sites More sharing options...
lunadesign Posted July 14, 2014 Author Report Share Posted July 14, 2014 Thanks! And what if there are other corrupt RDB files? Will the recatalog operation get stuck or will it be smart enough to skip any other bad RDB files? And will Retrospect re-backup any of the files that were lost in the bad RDB file? Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted July 14, 2014 Report Share Posted July 14, 2014 If there are any other corrupt RDB files, Retrospect will log an error. You can then move that file and restart the recatalog. Yes, Retrospect will re-backup any of the files that were lost in the bad RDB file. 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.