Disaster Recover of 2003 AD Dc to different hardware

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In order to create an appropriate DR policy I am attempting to restore the
system state of a domain controller to a different server. The original
server is a HP proliant DL360G4 and the test recovery server is a DL380G4, I
am using different hardware for 2 reasons, I don't have another DL360 and
also in the event of a disaster we may not be able to get identical hardware.

I am using the MS backup tool to simplify things to begin with although I
intend to using Legato Networker as soon as I have the process with MS.

On the first reboot after recovery I very quickly get a DLL failure, from
reading I assume this is a HAL issue. I have read the document
http://support.microsoft.com/default.aspx?scid=kb;en-us;263532&Product=win2000
and have got to the point of trying to get into recovery console to disable
acpi, but as soon as I select the OS in recovery console, the server reboots.
I have also attempted a repair of the exisiting OS and after restarting, the
server gets into a reboot loop as well, if I try to start it in safe mode it
stops on an acpi file.

Any suggestions out there ?

Thanks
Colin
 
I know there are people out there that have done this successfully, I have
never tried this scenario. I know one of the new DR pushes is to use a
virtual server for the DC, thereby eliminating the HAL issue.

Look at VM Ware and Microsoft Virtual Server if you are interested in this
approach.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi,
Have you tried scenario 3 that is mentioned in the KB article?
(repair of the OS?)

Cheers,
jorge
14-Nov-2005 17:46:11
message
In order to create an appropriate DR policy I am attempting to restore the
system state of a domain controller to a different server. The original
server is a HP proliant DL360G4 and the test recovery server is a DL380G4, I
am using different hardware for 2 reasons, I don't have another DL360 and
also in the event of a disaster we may not be able to get identical hardware.

I am using the MS backup tool to simplify things to begin with although I
intend to using Legato Networker as soon as I have the process with MS.

On the first reboot after recovery I very quickly get a DLL failure, from
reading I assume this is a HAL issue. I have read the document
http://support.microsoft.com/default.aspx?scid=kb;en-us; 263532&Product=win2000
and have got to the point of trying to get into recovery console to disable
acpi, but as soon as I select the OS in recovery console, the server reboots.
I have also attempted a repair of the exisiting OS and after restarting, the
server gets into a reboot loop as well, if I try to start it in safe mode it
stops on an acpi file.

Any suggestions out there ?

Thanks
Colin
Click to expand...
Cheers,
# Jorge de Almeida Pinto #
 
In order to create an appropriate DR policy I am attempting to
restore the
system state of a domain controller to a different server. The
original
server is a HP proliant DL360G4 and the test recovery server
is a DL380G4, I
am using different hardware for 2 reasons, I don't have
another DL360 and
also in the event of a disaster we may not be able to get
identical hardware.

I am using the MS backup tool to simplify things to begin with
although I
intend to using Legato Networker as soon as I have the process
with MS.

On the first reboot after recovery I very quickly get a DLL
failure, from
reading I assume this is a HAL issue. I have read the document

http://support.microsoft.com/default.aspx?scid=kb;en-us;263532&Product=win2000

and have got to the point of trying to get into recovery
console to disable
acpi, but as soon as I select the OS in recovery console, the
server reboots.
I have also attempted a repair of the exisiting OS and after
restarting, the
server gets into a reboot loop as well, if I try to start it
in safe mode it
stops on an acpi file.

Any suggestions out there ?

Thanks
Coli
Click to expand...

have you tried to do a repair of the OS as mentioned in the article?
 
Back
Top