Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Recover a W2K3 DC on another Hardware (Dissimilar Hardware)

Status
Not open for further replies.

Olivier1512

Technical User
Sep 29, 2005
6
BE
Hello,

In my quest of the impossible, I'm currently trying te recover a DC on another machine. As strange as it is, I was able to recover one of my 2 DC's (who is Blade based Hardware with AMD CPU) on a Evo Desktop.
I was trying to recover the second DC (child domain and who is also Blade based) on the same machine type as my previous DC and it badly crashed a startup. I did a repair and no more BSOD but it freeze at the splash screen (after 2 - 3 seconds). I'm able to restart in safe mode without networking. The other modes doesn't work.
I followed the steps decribed in this article but it doesn't work wel.

Also, would a DC recover will work work with BMR 4.7 and netbackup ?? Anyone experience with this product ??

Any othe ideas or tips

Thx in advance

Olivier
 
Do you have any DC's currently available on your network? On these DC's that you are trying to recover, is there anything special (i.e. Exchange Server)?

If you have another DC still up, you may not need to recover the DC's themselves. You will need to seize the FSMO roles if the DC's that crashed hosted these roles. From there, you can build new DC's from the domain you have via DC Promo.


Goodluck

"Assumption is the mother of all f#%kups!
 
In fact I'm plaaning a disater recovery.

That's why I have the backup of my root domain and my child domain.

I'm just trying to recover my forest on another hardware. If it doesn't work I will have to find similar hardware
 
Windows 2003 has a very cool option to be able to install a DC from backup media. It is good if you are in a remote site that would have a link too slow to replicate accross.

You may like to use it in this instance. If you loose the DC with the FSMO roles, you will need to seize them.

I have used this method on VMWare before, it is very cool

Goodluck





"Assumption is the mother of all f#%kups!
 
Sounds like you have a ghosted nic. I don't remember the article but I have seen this in the past when restoring to dissimilar hardware. You will need to remove the refernce for the old NIC from the registry.
 
Ok,

I did the test on a similar hardware (HP DL 380 G3) and you know what ??? BSOD 07B...

Then I did a repair like said in the MS article. And you know what, it works !!!!!!!!

Only think is that you must have a nic driver cd in your pocket.

Another solution is to change the ntoskrnl.exe if you restore on a Single CPU.

I will try the DC install from media and see if I can do a DRP with this method because the MS one is really long.

Anyway, thanks for the help.. If you still have other tips and trick, let me know

Oli
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top