Restoring windows 2003 sbs from a successful backup fails

[Gavin_Hooper_2]

We have been trying to do a test restore of a 2003 SBS server for the last 2 weeks and what ever we do we get a failure.
The furthest we have got is a full restore which completes succesfully but on reboot it blue screens with a stop message.

We have followed Document ID: 243037 http://support.veritas.com/docs/243037
excatly and it fails to reboot at II step 30.

The original backup was a success so the restore should worrk no problems.

We have version 10D with SP1 there appears to be no more updates available. We have installed windows 2003 sbs with sp1 with the exact drive config as the original.

[Aleks_Maksimovi]

Hi Gavin

You will need to take the next step of finding out what the BLUE screen stop code error is and what it means. A couple of reasons could be a problem with the BOOT.INI or a problem with a specific driver. But this depends of the STOP code error.

Regards,

[Vincent_Rabbat]

If its a domain controller, then you can't do it like this. First you need another domain controller in your domain and then reinstall server2003sbs then do a non authorative restore with the system state

refer to :

http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/activedirectory/maintain/opsguide/part1/adogd03.mspx

If its the only domain controller, it can't be done. Always have a 2nd domain controller in your domain (even use a crap machine for it).

[Gavin_Hooper_2]

The stop error is stop 0x0000007B but no other info is available.

I don't believe it's true about needing a second DC as some how I have got this server to restore in the past.

[Ken_Putnam]

Are you attempting to restore to the same hardware or different hardware?

If it is different, you probably have either a driver problem, or the Disk Configuration is not the same, including whether or not a utility partition exists

[Gavin_Hooper_2]

The hardware is exactly the same, both HP ML 370s. The only difference is this one has 1 less nic in it and doesn't have mirrored or raided drives but the size of volumes are the same

[priya_khire]

Hello Gavin,

Was the original disk configuration dynamic? Are you now restoring to a basic disk? Refer to the following technote that might help resolve the problem:

"STOP: 0x0000007B INACCESSIBLE_BOOT_DEVICE" is received during reboot when performing Intelligent Disaster Recovery
http://support.veritas.com/docs/248092

Revert if the issue still persists.

Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.

Regards.

[Gavin_Hooper_2]

No, the original was basic and so is this one.

[priya_khire]

Hello,

Install the latest device drivers for 10d, in case you have 10d and then verify the results:

http://support.veritas.com/docs/282974

Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.

Regards.

[Gavin_Hooper_2]

Sorry my mistake it is version 10 we are using. Can't find any driver updates for this.

[Ashutosh_Tamhan]

Hello Gavin, has the hardware changed ever since you have taken the full backup of the server to be restored?
Also check : http://support.veritas.com/docs/198094
http://support.veritas.com/docs/237174



Regards,
Ashutosh

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Gavin_Hooper_2]

As stated in my previous reply

"The hardware is exactly the same, both HP ML 370s. The only difference is this one has 1 less nic in it and doesn't have mirrored or raided drives but the size of volumes are the same "

[Gavin_Hooper_2]

Also this is not an IDR restore

[Deepali_Badave]

Hello,

Please refer the following technote:

http://support.veritas.com/docs/249077

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Gavin_Hooper_2]

How would this help when i have clearly stated in previous posts that i am using a basic disk
Quote "No, the original was basic and so is this one"

It seem as if there is no considered opinion on what is causing this as you keep suggesting the same thing. A thorough reading of previous posts implicates that this will not fix the issue.

A lot of time has been spent on this issue and I am very disillusioned with the email support so far.

We are a Veritas/Symantec 'Preferred Partner'

Please provide information on how to escalate this issue as it is a new purchase that is not fit for the task it is intended until this issue is resolved.

[shweta_rege]

Hello,


The error faced by you most often appears because the SCSI controller is in need of a third party driver that was not included in the Intelligent Disaster Recovery (IDR) disks because the option Use currently installed drivers was not selected during disk creation, or the drivers were too large to fit into the IDR disks. These drivers may not have been included on the Windows installation media.


This issue occurs if windows is having problem loading the disk controller driver. ie. RAID, IDE, SCSI driver or there is any modification in boot.ini .We suggest you to use Windows 2000 Service Pack integrated CD to create IDR bootable CD. Start the IDR process from the scratch once again and observe the result.

We would suggest you please refer to the following technote

Title :- When performing Intelligent Disaster Recovery, the message
"Inaccessible_Boot_Device" is displayed during reboot.

http://seer.support.veritas.com/docs/237174.htm


Recovering a system that uses a RAID array

http://seer.support.veritas.com/docs/190616.htm



NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered
and would be moved to answered questions pool.

*************************************************
************************************************