Jump to content

Repair Catalog: Backup Set Data File Name Is Invalid (Aka Is Pulling A Few Files Out Of A Damaged Rdb File Possible)?

Recommended Posts

Initial Scenario:

An external disk used for retrospect backups was formatted (and was not used after formatting so there was little overwrite). A recovery tool found 300 or so ?intact? RDB files and saved them to an additional unused external drive. I'm not expecting to recover all the backed up data but finding even a bit would be extremely helpful.


What I'm doing:

  2. Tools: Repair Catalog: Recreate from disks:
  3. Choose "All Disks" (then browse to folder containing the .RDB files and hit OK)
  4. Retrospect's next prompt is "Select a Backup Set to recatalog" (the correct catalog name already highlighted/selected). OK.
  5. Are there any more disks in this backup set? No.
  6. Continue with the recatalog with missing files? Continue....



I then get the following alert (error):
The backup set data file name is invalid, cannot recatalog the set using these files.
(and there are no further steps to take)


...I've seen some discussions about this error message and I'm assuming some RDB files are corrupt...


Is there a way to check which RDB files are still intact? I could manually put each RDB file on a disk by itself, try to repair the catalog and cross my fingers but given I've got over 300 RDB files, this woud be pretty time consuming (and no guarantee of success)


...alternately, is there a way to recover some intact data from a problematic RDB file (again, even recovering a few files would be extremely helpful).


Finally, while it would be bad news, if some of you experts confirm that I'm just out of luck, that would be helpful in that I'll stop wasting my time fiddling around with this....


Thanks in advance!


Edited by Eric Campbell
Link to comment
Share on other sites

Retrospect creates and erases RDB files all the time, depending on your settings, like grooming and/or recycle. So unless your drive was previously DoD-wiped and only written those RDB files sequentially without any erasing/recycling etc. chances are you'll end up with far more 'restored' (and corrupt) RDB files when doing an unerase. Furthermore the naming of them will probably be incorrect.


Unformatting can be done by experts, but in reality it's very often not possible to recreate the exact state of the disk as it was when it was formatted. It can be a nice security breach though, as some/a lot information can be extracted, but unfortunately often not in the way you want in this case.


You can either give up and learn from this mistake (actually you have not been using Retrospect as a means of backup, but more likely as a (single point of failure) archiver), or try to fiddle with it and (quite likely) spent a lot of time without results.


Considering you only have a bunch of randomly named and (some) maybe corrupt RDB-files I think you'll probably waste your time.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...