W2k3-Entprise R2Sp2 Domain Controller Failure DNS Recovery Using Netbackup 6.5

kelly_lee · 05-04-2008, 04:33 AM

I am recovering from a raid failure of my system. It's a Windows Server 2003 R2 system with SP2 applied and providing DNS , DHCP, Active Directory. Services. There is a second domain controller in the system which did provide us a safety net.

I have restored the system using netbackup 6.5 using the following procedure. 1. Install same OS and patches/service packs. 2. set same node name and ip address as the original server. 3. Restore the c: partition and the system state. (I did this at the same time)

The system came back all files. The configuration is still not back. My active directory DNS did not come back. DHCP configuration is gone I had to rejoin the Domain ( I expected it to join after the recovery of the system state information)

I must have missed something here. Looking for Ideals and or help. Netbackup was suppose to do more. (I know I should have made the BMS restore disk but it did not happen)

This should be a text book problem but needs to be resolved quickly and help would great (No other SA's here to reference)

kelly

gr8fl1 · 05-15-2008, 09:53 AM

Have you tried a non-authoritative restore?

kelly_lee · 05-16-2008, 01:19 AM

My Backups were in good shape but I had not done a Netbackup Bear Metal Restore CD.

Because of time problems I ended up rebuilding the OS and added the patches then did a data restore from netbackup. I had to grab the fismo roles from the failed dc and let the second dc take over. I had linux users who could not login until this happened. I chose a new name for the rebuilt dc and rejoined the domain. My users with roaming profiles I did a global replace of the profile share and they all logged in with no problems. There may have been cleaner ways to do all this but We needed the system up.

If you have not done it yet you may want to spend the time to create the BMR recovery disk. This is my next project. Any one with a procedure to create a BMR disk would save me reading the 500 page netback book. If they want you to use it then why over document it?

Thanks for your post.
Kelly :)

05-04-2008, 04:33 AM	#1 (permalink)
kelly_lee Registered User Join Date: May 2008 Location: texas Posts: 3 OS: windows server 2003 r2 sp2	W2k3-Entprise R2Sp2 Domain Controller Failure DNS Recovery Using Netbackup 6.5 I am recovering from a raid failure of my system. It's a Windows Server 2003 R2 system with SP2 applied and providing DNS , DHCP, Active Directory. Services. There is a second domain controller in the system which did provide us a safety net. I have restored the system using netbackup 6.5 using the following procedure. 1. Install same OS and patches/service packs. 2. set same node name and ip address as the original server. 3. Restore the c: partition and the system state. (I did this at the same time) The system came back all files. The configuration is still not back. My active directory DNS did not come back. DHCP configuration is gone I had to rejoin the Domain ( I expected it to join after the recovery of the system state information) I must have missed something here. Looking for Ideals and or help. Netbackup was suppose to do more. (I know I should have made the BMS restore disk but it did not happen) This should be a text book problem but needs to be resolved quickly and help would great (No other SA's here to reference) kelly

05-15-2008, 09:53 AM	#2 (permalink)
gr8fl1 Registered User Join Date: May 2008 Posts: 6 OS: XP SP2	Re: W2k3-Entprise R2Sp2 Domain Controller Failure DNS Recovery Using Netbackup 6.5 Have you tried a non-authoritative restore?

05-16-2008, 01:19 AM	#3 (permalink)
kelly_lee Registered User Join Date: May 2008 Location: texas Posts: 3 OS: windows server 2003 r2 sp2	Re: W2k3-Entprise R2Sp2 Domain Controller Failure DNS Recovery Using Netbackup 6.5 My Backups were in good shape but I had not done a Netbackup Bear Metal Restore CD. Because of time problems I ended up rebuilding the OS and added the patches then did a data restore from netbackup. I had to grab the fismo roles from the failed dc and let the second dc take over. I had linux users who could not login until this happened. I chose a new name for the rebuilt dc and rejoined the domain. My users with roaming profiles I did a global replace of the profile share and they all logged in with no problems. There may have been cleaner ways to do all this but We needed the system up. If you have not done it yet you may want to spend the time to create the BMR recovery disk. This is my next project. Any one with a procedure to create a BMR disk would save me reading the 500 page netback book. If they want you to use it then why over document it? Thanks for your post. Kelly :)