Re: Compaq to IBM Server

Hi,

Basically the compaq is ML570 (running smart array 5300) and IBM is x-series 255 (serveRAID). It is running as a domain controller, hence, only system states is restored. Tried all method found in the article Bruce posted, but still cannot boot up, keep saying "boot device inaccesible". Please help!

Any idea how to see the boot process? e.g. at which part of the booting that hangs?

Hi Nut Cracker,

Thanks for the info.
I have confirmed that the boot.ini is the same. What I did is the same as your suggestion, buildup x255 from scratch, and restore system state using NTbackup from LTO tape to the x255. After reboot, blue screen. I tried repair using Emergency Repair Disk does not work. Tried repair using inplace upgrade also does not help. I agree with you that setting up another domain controller and let replication do the rest is the best alternative, however, the purpose of this recovery is meant for disaster recovery when only thing available is restore from tape.

Is there any way to step through the boot process to find out if what has gone wrong?
Is there anyway to prevent any of the hardware info in the registry not to be overwritten, during the restore process?

"NuT CrAcKeR" <nutcracker@intenationalhacket.org> wrote in message news:OA%23DxpXQDHA.2316@TK2MSFTNGP12.phx.gbl...
it could possibly be more than just the RAID driver. In the arcpath specified of the boot.ini that you are using in your recovery, make sure that the correct multi()disk()rdisk()partition() entry's are being used. Also, make sure that the entries are correct for your new hardware. There are also likely to be chipset differences which will also cause the recovery to fail. You might want to do a temp install of 2000 on the IBM just to see what the boot.ini has in its arcpath. Then, wipe the system, modify the boot.ini on the recovery install, and make any necessary changes. This is still likely to be problematic in the long run.

I would have to honestly suggest that you buildup the x225 from scratch, and then restore the system state to the machine. If you have another domain controller that is still online, simply setup the IBM as a DC and let replication do its thing. If you can still access the ML570 online, backup AD and the systemstate to a location on the network... build the x225, and restore the state to the new server. be sure to have to ML570 off line when you bring the x225 onto the wire, as it would be best to have the IBM configured exactly as the CPQ was.. name, IP, etc...

If you dont have any other DC's, I am sure you wont ever have another single domain controller environment again... right?

NuTs