Bringing up Active Directory and Servers in DR site?

Looking for thoughts and best practice for replicating and dealing with restoring an environment after disaster strikes.  We have a DR facility with a high bandwidth pipe.  Replicating AD to this site would not be difficult, but what happens when your primary site evaporates into thin air and you need to bring up the same server infrastructure at DR?  We have the ability to Snap mirror (replicate) data in near realtime via SAN and we are heavily virtualized.  What I'm struggling with is the naming and IP addressing of the identical servers at DR.  I'd be interested to hear how others are tackling this issue?  Assuming that in the event of Primary site failure, the DR site must quickly assume all critical server roles, names and IP addresses.

Thanks!    
dkrautAsked:
Who is Participating?
 
ee_autoConnect With a Mentor Commented:
Question PAQ'd and stored in the solution database.
0
 
KenMcFCommented:
Just install another DC at your DR site with DNS and make it a GC. Do not use imageing or snapshots. Make sure you setup your DR site as a seperate AD site with the proper subnets.
Some companies configure there DR sites as lag sites and only replicate during certian hours or days of the week.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you've got NetApp Filers at both sites and you are heavily virtualised this is easy.

At the DR site, Break the Snap Mirror to the LUNs containing your Snapshots of the LUNs which contain your servers present these LUNs to your ESX servers at your DR site (ESX will see them as snap LUNs).

Rescan the hbas and vmfs, the LUNs should appear, browse the datastores add the VMs to the inventory.

Power On VMs.

Now, this assume's one thing, and we've spoken to our Networking Team, and they have carried over ALL or production VLANs to the DR site, ready for the day, when we have to move there.

0
 
alreadyinuseCommented:
If you are wanting an identical setup with names, ip addresses, dhcp etc then why don't you isolate the environment until needed. Put a firewall in the frontend and deny communications until needed. Provide seperate external access if needed using a VPN connection into the isolation DR site for testing etc.
0
 
dkrautAuthor Commented:
So setting up a new site with DC's at the DR facility seems like a logical approach to handling AD.  What about Stretch/Geo clustering for critical app servers?  Anyone have any experience with this?  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.