| Howard Kaikow 2005-01-25, 5:46 pm |
|
I had the misfortune to have a hard drive die about two weeks ago, alas, it
had my main OS.
So, I now get to test Retrospect's mettle for a CD-ROM DR recovery.
Over the weekend, I got to the point of rebuilding the catalog.
It took just under 6 hours and 43 minutes!
For reasons not relevant here, the restore did not work and I had to
re-start the DR.
I could find no way to use the already re-built catalog.
Is there a way to point the DR to an extant catalog file?
So, I had Retrospect rebuild the catalog.
Alas, this time there was a BSOD before the rebuild was finished, or while
the system was waiting for me to return to the computer to respond.
So, as we speak, I am running the DR again, and the catalog rebuild is under
way.
After 4 hours and 20 minutes, 38.5 GB has been cataloged. Cannot believe
there's much more to go.
Hopefully, this build will succeed.
If not, my only recourse may be to install a real OS and install Retrospect,
then restore ALL the drives. However, I'm afraid that the system state would
not then get properly restored.
Key question:
If drive X was my main system, i.e, the one under which the backup set was
created, then if I create an OS on drive Y, install retrospect on drive Y,
and then Restore drive X from the backup set, will ALL of drive X's files
get restored, including those of the system state?
|