Retrospect Cannot find database files
We had a nightmare scenario 2 weeks ago where a server went down with 2 corrupt RAID drives. The Retrospect 7.6.123 SBS backup drive also got corrupted (thanks solar flare!)
We sent the drive off for recovery and got it back. Now, we cannot open the catalog file as it says it is heavily damaged. We try to recreate the backup set (either from disk or backup file) and it doesn't see them or says that it is not backup files. We tried it the following ways:
Directly connecting to the drive
Copying the files to another USB drive and trying to connect to it.
Sharing the drive and trying it from another computer both as a share and as advanced->UNC
Using another computer with Retrospect 7.7 and trying to open it that way.
Is there ANY way to get to these .rdb files?
We sent the drive off for recovery and got it back. Now, we cannot open the catalog file as it says it is heavily damaged. We try to recreate the backup set (either from disk or backup file) and it doesn't see them or says that it is not backup files. We tried it the following ways:
Directly connecting to the drive
Copying the files to another USB drive and trying to connect to it.
Sharing the drive and trying it from another computer both as a share and as advanced->UNC
Using another computer with Retrospect 7.7 and trying to open it that way.
Is there ANY way to get to these .rdb files?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for kirk_lesser's comment #a38347983
for the following reason:
We were stuck with the way we had to do things for this client.
Accepted answer: 0 points for kirk_lesser's comment #a38347983
for the following reason:
We were stuck with the way we had to do things for this client.
Points should be rewarded. There was no off-the-shelf way to recover, so I told them they had to go to a recovery lab. This is what the the author ended up doing.
ASKER