win2k3 reboot problem

[Ian-c_1]

I am running 2 ML350's one as a SQL server and the other as a disaster recovery machine, both of these machines are linked over a network to a backup server using retrospect 7.0

I tried doing a full restore of the DR box (op sys and data) when I rebooted the machine it would not work it just kept rebooting

the backups look fine but I cannot get a restore to work, any ideas?

[Ivan Ferreira]

The question is, would work even if you restore on the origiinal system? I know that maybe you cannot test that, but ensure that your backup software can save open files. Ensure that both server have the same and exact hardware configuration, slot by slot.

Before taking the image, uncheck the option in startup and recovery to automatically reboot the system. Maybe at least you will get an error msg.

[Robert S. Carr]

Ian:

Well, I say the obvious but it looks like the recovery isn't exactly 'optimal'. At least you ran a test so you know what to expect in case of an actual disaster.

To get the DR machine back in action, you'll need to run the Recovery Console from your installer disk. The procedure is covered here:

http://support.microsoft.com/?kbid=326215

There is one potential issue you need to take into account before running the recovery console. If you upgraded your Win2k3 server with SP1, you'll need to upgrade the installer disk. This is called Slipstreaming. To slipstream a Win2k3 install disk with SP1, see:

http://www.petri.co.il/windows_2003_sp1_slipstreaming.htm

This is to prevent the recovery console from potentially over-writing older pre-SP1 files onto an SP1 installation.

Here's a great set of links covering disaster recovery:

http://www.petri.co.il/disaster_recovery.htm

Ian, a question. Are you using the Disaster Recovery Add-on?

Let everyone know how things are coming.

Rob

[Ian-c_1]

well I have tried a few different scenarios for the restore

all the work was done on the DR box using backups that had worked without errors

the retrospect has open file, disaster recovery and SQL database add ons installed

the win2k3 is not service packed at all (this was something else that was to be done after a successful restore)

managed to catch the error message on one of the reboots - Bug Check 0x7B: Inacessible boot device

have tried using symantic ghost 6.5 to do an image backup and restore but the same thing happens

tried building a Disaster recovery CD using retrospect but I get the same results

the only way I could get the system to come back up to a workable state with minimal data loss ( one of the SQL instances did nor work) was to use the windows Automatic System Recovery option, but this took about 6 hours to check all the drives in the mirror set

I can get the system running if I do a clean install using the HP SmartStart CD but this is not a great solution as then I will have to manually reload all the application software and reconfigure the SQL etc.

I keep thinking im doing something wrong somewhere and its going to be an easy fix but I can't find it

[Robert S. Carr]

Ian:

I found this on the EMC website for Retrospect:

Disaster Recovery

Some third-party drivers not installed: During disaster recovery of a local or client Windows computer, Retrospect automatically installs most third-party drivers required to communicate with the backup device, hard disk, and over the network. However, some drivers cannot be installed automatically. In this case, you will have to install the drivers during the temporary operating system setup (as in the case of some RAID drivers) or exit the Disaster Recovery Wizard to use the Windows Hardware Wizard or Hardware Manager (as in the case of some Network Interface Card drivers).

See http://kb.dantz.com/display/2n/index.asp?c=12&cpc=5GSK8V331KGNkyd4x263e7QPl325RA1mX&cid=2&cat=&catURL=&r=0.1602442


Are you using a RAID with the ML350?

Rob

[Robert S. Carr]

Another tip from EMC on Windows XP installations experiencing a similar problem to you. On reboot the machine won't start:

see

http://kb.dantz.com/display/2n/index.asp?c=12&cpc=5GSK8V331KGNkyd4x263e7QPl325RA1mX&cid=2&cat=&catURL=&r=0.1602442

if this link does not connect properly, visit
http://kb.dantz.com/

look for

Windows could not start because of a computer disk hardware configuration problem after a restore

Their instructions are to

1) Boot from the setup disk

2) Press R in the recovery console

3) Select the Windows installation and enter the administrator password at the prompt

4) Type

bootcfg /add

at the prompt

5) Respond Y to add the restored installation to the boot list.

6) At Enter Load Identifier, type Windows 2003 Server.

7) At Enter Operating System Load Options:, press Enter.

8) Exit the Recovery Console and select the first item on the boot menu.

9) After you log on, edit C:\Boot.ini to remove the improper entry.

Hope this works. I haven't used Retrospect 7 but my experience with past versions has been quite good.

Good luck.

Rob

[Ian-c_1]

Thanks for all the help Rob

yes I am using a raid on the ML350

I tried the bootcfg /add as you suggested and this did not work either

I have tried repairing the boot sector and the MBR I have also tried replacing the startup files from the cd and again it does not work

I still have to try installing the drivers for the raid during the temporary OS setup, I will let you know how I get on

Thanks again

Ian