• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 343
  • Last Modified:

Best practices for setting up a test DR environment.

Hi all,

I am in the process of performing DR tests on our Exchange Server 2003 tape backups.  I am starting with a bare-metal restore.  I had all the servers set up and prepped to begin when the DC I had built, DCPROMO'd on our network, replicated, brought offline and then up again on the test network had a HD failure and died.  Now I can't even put it back and demote it. (I'll use ntdsutil later)

The Exchange server and Backup Exec servers are set up and waiting to go.  I'm rebuilding the new test DC now and will DCPROMO it on Monday to replicate.  I winged it last time, I thought it might be wise to check with some more knowledgeable folks about what the best game plan would be.  Here's what I need:

1. The Exchange Server (Server 2003 - member server) must belong to the same domain as it was before it theoretically died, as well as have the same name.
2. The Backup Exec server is Server 2000. (Member server)
3. All Service packs at same level as their real-time counterparts.
4. Now... the DC.  I DCPROMO, disconnect, seize roles and bring up on test network, correct?  Best practices?

When I 'm done testing, I put back on the production LAN and demote.  As simple as that?
  • 2
1 Solution
The question was about best practice for DR - I believe I have answered that with the link I provided.

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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