We are currently going through some DR tests for our network and I am looking at the possibility of using ASR restore to restore our SBS 2003 server to different hardware if needed (as well as thrid part solutions). I have run into a problem though:
Using a test network, I perform an ASR backup of an SBS 2003 server, remove it from the network and perform a restore on to a different box. This goes fine, and the machine boots up OK. I then perform a full restore of the system partition (using Backup Exec 11d) and reboot.
All still fine. I then boot to DSRM to restore the system state. When I then reboot, I get a stop error 0x0000007B every time. I know this error usually relates to drivers, which I thought might crop up eventually, but I'm not sure what to do about it.
Now the system seemd to be running OK before I performed the system state restore - Sharepoint was up and running, network services were running. I hadn't got as far as restoring the Exchange DB though. I also have a second DC on the network which the SBS server can replicate from.
My question is really - does anyone have any ideas as to what could be causing this stop error? More to the point, could I even get away without restoring the system state? What would be the issues with leaving the system state as it was at the point of the ASR backup? (considering that I have a second DC to replicate AD from).
Is ASR restore a viable solution for restoring an SBS server to different hardware?
Any help would be appreciated. Thanks.