Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1219
  • Last Modified:

How to Restore Win2k3 Domain Controller to different hardware for Disaster Recovery scenario

My client is struggling with the process to restore a Windows 2003 R2 Domain Controller to new hardware - for disaster recovery scenario.

This domain controller is also an Exchange 2003 server.

So, it's like a small business server restore.

Symantec 12d (from tape) and Symantec LiveState Recovery server (images) are being used for the restore

The problem is that after the restore:
1.  Cannot add objects to the Active Directory - but can change properties on existing objects
2.  Exchange 2003 System Attendent and Information Store does not start automatically.

Please advise if you have recovery steps or have resolutions for these issues.

Thanks very much,
Allison Sutherland


0
AHSutherland
Asked:
AHSutherland
1 Solution
 
Jian An LimSolutions ArchitectCommented:
is this only 1 DC environment?

if not, you might need to do a non-authoritaive restore
http://seer.entsupport.symantec.com/docs/236661.htm

you also should read up the symantec process

http://seer.entsupport.symantec.com/docs/243037.htm

If using BESR, please check http://seer.entsupport.symantec.com/docs/310642.htm


because your issue was not properly mention, i am guessing your AD was not restored properly.

also review the backup procedure, you need the system state when doing BESR.


Cheers,
0
 
AHSutherlandAuthor Commented:
First case is:
1 DC with all FSMOs restored to test environment - not intended to place back into domain... purpose of restore is to test Win2K3 Std to Enterprise Upgrade

2nd case is:
1 DC with all FSMOs restored to test environment - add next DC to test replication

Am doing research on Symantec.

0
 
SurajCommented:
Exchange Information and system attendant would not be starting since you exchange server which is a domain controller should have the SACL rights. While starting MSExchangeSA service you would be getting 2114 MSExchangeSA event ID. Run setup /domainprep.

Another thing is you should check if the exchange box is also a Global Catalog servers.

If in case you could mention some events from the directory services and ntfrs events we may suggest you some more steps?

More over you can provide us how many domain controllers do you have in your environment and exchange servers so that it would be more clear to set the action plan.

Thanks,
x-sam
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now