Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 8743

Designing Remote Site Failover (Hyper V Replication & Failover)

$
0
0

Hi All,

We are looking to run a pure Windows 2012 R2 environment for our main office (New York) and want to design as best an instantaneous failover solution to a remote site (Chicago) given we have various and numerous outage problems.

MAIN OFFICE (NEW YORK)

SonicWall NSA220 Router

Dell Server 1 (running Hyper V 2012 R2)

  1. DC Server VM (DC, DNS, DHCP, File Share, etc)
  2. DirectAccess Member Server VM

Dell Server 2 (running Hyper V 2012 R2)

  1. Exchange Member Server VM

Dell Server 3 (running Hyper V 2012 R2)

  1. Database Member Server VM1
  2. Database Member Server VM2

50 Workstations

REMOTE OFFICE (CHICAGO)

Sonicwall NSA220 Router (connect to MAIN OFFICE via VPN)

10 Workstations

Everything I've been readying about Hyper V 2012 R2's awesome Replication & Failover solution leads me to believe we can simply setup the same amount of servers to the Remote Site, connect the two sites via Sonicwall VPN, and then copy the VM's to them using Replication (first local copy, then replication over WAN VPN), and then...when a failure occurs, we simply spin up the VMs at the remote site for near instantaneous failover (along with changes to DNS, MX records, etc.)

Is what we are considering a solid, cost effective solution?  Or should we be setting this up some other way?



Viewing all articles
Browse latest Browse all 8743

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>