WinXP recovery after hard drive failure?

[libove]

I have a WinXP system. The hard drive failed. I replaced it with a newer larger hard drive. I have complete Networker backups (v6.2) of the system, including C:\ (the only drive letter in the system), SYSTEM STATE:, SYSTEM DB:, and SYSTEM FILES:.

What is the right order of steps to take to recover this?

Here's what I think:
1. install XP minimally
2. install Networker client to temporary location
3. run Networker "recover" client and restore all Save Sets for this client system, and also run Networker "recover" client and restore SYSTEM FILES:, SYSTEM STATE:, and SYSTEM DB:.
4. reboot
5. cross fingers ...

Do I have that right?

Here are the specific commands I have in mind for the recoveries:

recover -s servername -iY -S ssid -S ssid -S ssid ...
where the ssids come from 'mminfo -s server -c client', taking all ssids starting with the most recent 'full' and including all 'incr' since then.

recover -s servername -iY <enter>
directory to browse: /
add SYSTEM STATE:
add SYSTEM DB:
add SYSTEM FILES:
recover

Do I have this right?

Thanks!
-Jay

 

[wallace88]

A simplier method is just to reinstall XP, install NetWorker client, start up NetWorker User GUI, then mark everything for that client, and hit start.

NetWorker is smart enough to recover in the correct order. Once the recover is complete, it will ask you to reboot, and you have to reboot to complete the recovery.

 

[libove]

Yeah, I thought about that and tried it. It took more than an hour for nothing to come back after I selected the C:\ drive. It seems that I have some kind of massive inefficiency problem on the Networker server (nsrindexd ran at ~90% CPU for that entire time).

To get a clearer picture of what was happening during that time, I killed the nwrecover off and started a recover, and typed "add C:". It began, slowly, listing out the tens of thousands of files that the whole drive would include. At the rate it was finding and listing files and directories, it would take days or longer.

I cross-checked the index for that client, which took only a minute and returned no errors. The index is only about 18MB.

Is there something I can do to make the indexes / nsrindexd more efficient?

Thanks
-Jay