Restoring system state Win2K server DC

[dufresnem]

I have a Win2K Server as my main DC which is approximately 5 yrs old. I want to replace the server entirely.

To minimize the impact, the current DC is still online and running. I have built a brand new server and will install Win2K Server with AD onto this new box.

Is there any documentation on how to restore the system state from backup tape onto the new server with little impact?

 

[DaveGoTech]

I think you are almost there. The exact procedure would depend upon your backup software. The restore would have to be accomplished after hours of course. Just disconnect the network cables during the restore.

 

[dufresnem]

What I was going to do on the new server was this;

1- Install Win2K Server as a DC with the same hostname and IP. (Obviously, this won't be connected to the LAN)

2- Patch the server with latest service packs.
3- Install ArcServe Client Agent backup software
4- Reboot into Directory Restore mode and perform a nonauthoratative restore of the complete system/boot partition including the system state.
5 Reboot server and login. My domain profiles should still be intact.

 

[DaveGoTech]

Yes, you are doing it right. I recently replaced a Netware server with a new box and followed a similar procedure. The only thing I missed were a few references to the old H/W drivers for the network card, which, when restored, killed the new server. I had another issue with accounts (particular to Novell) so I decided to start over again. Luckily, since you are not touching the live server, this can safely be done.

 

[dufresnem]

I have just finished installing Windows 2000 server onto my new box(fully patched), with all the backup software installed. I'm ready to restore the system/boot partition from tape.

One last thing before I proceed. Win2KServer is installed and I HAVE NOT CONFIGURED IT AS A DC. AD is not installed.

Can I just reboot into Directory restore mode and restore the system/boot partition from tape, or is it a must to configure the server as a DC with AD instaled prior to restoring from tape?

 

[DaveGoTech]

I would configure the new server as close to what it was before prior to restoring. That way you minimize surprises and possibly save time troubleshooting.

 

[adamc1115]

I did something similar, though I was contending with many applications that I didn't want to reinstall.

I used Symantec Ghost to image the server to a USB disk, then to the new server.

Dropped in the Windows 2000 Server disk, ran a repair, reloaded all updates and service packs, and the server was good to go.

 

[dufresnem]

Sorry I haven't replied sooner. Very very busy!!!

Restored everything and all is well.

Installed everything and configured the new server to almost a mirror of the old.
Installed AD.
Installed DNS
Installed backup software

Created a mini LAN and placed the new server, backup server and workstation on that LAN. Performed a restore to the new server. Tested everything.

Brought down the old, connected new box to my Corporate LAN, brought up the new box...perfect!

 

[rws70]

Question for adamc1115

You said you used Ghost to backup and restore a domain controller. I tried that a while back but it was not successful. I read in a Microsoft article that Ghost would not work. I had to use special backup software like Veritas to do it because it intergrates in a special way. What a shame because ghosting a server's hard drive is so easy.

You sound like you have found a work-around. Restore the Ghost image and then run a repair job from the install cd. My install cd is old and I am running sp4 now so I would probably have to reinstall sp4 too.

How do you handle the authoritative vs non-authoritative aspect of the restore?

Can you concur and/or comment further on this method. Ghost is so easy to use compared to the Veritas method which requires building a new box with the same name, etc. etc. etc.

Cheers
RWS

 

[adamc1115]

Sorry for the late reply. It worked fine, I would slipstream in SP4 using

http://www.nliteos.com/

As you found, it isn't supported by microsoft. If it is your only dc you shouldn't have to worry. If there are multiples I would transfer your fsmo roles and dcpromo it out first.