[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Cannot restart dc after authoritative restore

Hi All
I am planning to upgrade to w2k3 but before I do am staging my whole
environment first on an isolated network to see what I will be up to.
I did a system state backup of my production root dc and did an
authoritative restore with that backup on my staging dc. The restore
completes successfully but unable to restart the staging dc after the
restore.
Any ideas
0
Caddo65590
Asked:
Caddo65590
1 Solution
 
jbaker151Commented:
Hi Caddo,
Was the staging dc configured as a DC on your production DC prior to the restore?
I don't know if this will help you or not, but I've built an isolated offline domain for testing purposes as well. What I did was bring 2 new domain controllers up in our production domain, wait until everything has replicated, then shut them down. After the shutdown I plugged in a secondary hard drive on each of the new DC's and did a disk-to-disk ghost. I then unplugged the new secondary hard drives and brought the DC's back up into production and ran dcpromo to cleanly demote them from their DC roles.
To build the offline test domain, just unplug the original primary hard drives, and plug in the new secondary as the primary and bring them up on your isolated network. Because these machines won't see the other DC's anymore, you have to seize all of the FSMO roles to them as if you were recovering from a DC disaster or something.
This has worked like a charm for me. I've rebuilt it many times with this method so my offline domain resembles my production domain as closely as possible.
I hope this helps.
JB
0
 
Caddo65590Author Commented:
I guess you are right bit I didnt want to go through all that process.
According to all the articles I read from the microsoft site, a system state backup from the production system could be used to do an authoritative restore on the test domain but I guess in my case the hardware could be the issue.
After several unsuccessfull attempts I took one of my production dc's to the test domain as the only dc.
Run dcpromo on one server as an additional dc. After replication had completed, I removed the production dc from the test domain and seize all FSMO roles to the additional dc. This worked for me but why do we have to go through all that instead of a simple authoritative restore.
Thanks anyway
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

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