How to do a AD recovery with the backed up system state for w2k3?

This is running a w2K3 server as a single DC. My management is worry if the server (especially server hardware) is down, we do not have any backup and how can we recover the system so as business as usual. We only have a monthly backup on system state. If this DC is down, can we restore this system state on a different server, and all the users can logon to the domain as per usual?

Or any other suggestion as long users can logon to domain.

Thanks in advance.
LVL 1
MichaelBalackAsked:
Who is Participating?
 
VirastaRConnect With a Mentor UC Tech Consultant Commented:
Hi,

Check whether this step by step answers your question.
Restoring Windows 2003 Active Directory in a Disaster Recovery Situation.

How to Recover from an Active Directory Failure
http://www.packtpub.com/article/how-to-recover-from-an-active-directory-failure

Hope that helps :)
0
 
DaveCommented:
Whilst restoring AD from a Windows/2003 backup is pretty simple, providing the machine name and OS versions are the same, and finding a spare machine with Server 2003 installed might be challenging these days, as the Microsoft instructions here :-

http://technet.microsoft.com/en-us/library/cc758435(v=WS.10).aspx

However if its a month old, then it may not be much use to you. So all the passwords will be a month old, all the groups membership will be a month old... One of the biggest issues you may have is that each machine that's a domain member has a password that it keeps updated at least every 30 days, so these will all be different on the machines and you will have to rejoin all the machines to the domain.

You can change the period by policy:-

http://technet.microsoft.com/en-us/library/jj852252.aspx

but that opens things up to attack.....

Best practice would be to add the DC role to another "server". Then if one fails most apps will just fail over to the second.
0
 
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Have more than one DC and if hardware is an issue then ensure you one DC as a VM and ensure it is a Global Catalog server.  You should always have more than one GC server.
0
 
rick81Commented:
if you're worried about a physical DC you should have recent backups, a spare server (to run as additional DC) either physical or virtual.  Also having onsite hardware warranty/support from manufacturer can usually be a life safer if you ever run into trouble with the hardware.  another option is to use imaging software that will allow you to restore the DC to different hardware.  Acronis or Shadow Protect offer this.
0
 
DaveCommented:
Cloning is great unless you have a BIOS Locked OEM image of windows, in which case it may not run in a VM.
0
 
MichaelBalackAuthor Commented:
Hi everyone,

Thanks for the suggestions. I really appreciate.

Hi VirastaR,

Your articles look promising. Let's me read through the whole article and update you later.
0
 
MichaelBalackAuthor Commented:
It works perfectly
0
All Courses

From novice to tech pro — start learning today.