How to test Hyper-V replication failover
Have a main site and DR site with Windows 2012 replication running across a 10MB WAN link. Would like to test actual failover but not sure what would need to be done to remote VM to make it work.
Assume main- 192.168.0.x range
Assume DR- 192.168.10.x range
If I do planned failover to DR site, I will have an operational server on the wrong subnet. Do I need to readdress remote server to the DR site's local IP range and update DNS? Does MS include some facility or tool to work around this? Just trying to find more info to test real world and simulate a failed VM at main site.
Assume main- 192.168.0.x range
Assume DR- 192.168.10.x range
If I do planned failover to DR site, I will have an operational server on the wrong subnet. Do I need to readdress remote server to the DR site's local IP range and update DNS? Does MS include some facility or tool to work around this? Just trying to find more info to test real world and simulate a failed VM at main site.
Last Comment
ASKER
50 users, 15 servers run 24x7. Only 1 HyperV server per site with local disk storage.
Most users connect using web enabled apps but more concerned about single VM issue than entire site outage. Boss wants me to prove that we could DR a single server failure. We do have a virtual DC at DR site so am less concerned about testing a DC failure and more an app or database server.
Does this give more info?
Most users connect using web enabled apps but more concerned about single VM issue than entire site outage. Boss wants me to prove that we could DR a single server failure. We do have a virtual DC at DR site so am less concerned about testing a DC failure and more an app or database server.
Does this give more info?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
So in your example, would I need to connect to each virtual server,
readdress it for the local subnet,
update DNS so internal resources could connect to it?
My boss will want to test this, too. This doesn't sound like an easy thing to test.
readdress it for the local subnet,
update DNS so internal resources could connect to it?
My boss will want to test this, too. This doesn't sound like an easy thing to test.
That is correct. The VMs at the DS would require some tweaking prior to bringing them online.
And no, it is not "easy" but necessary. :)
And no, it is not "easy" but necessary. :)
ASKER
Gotcha. Thx and I will send points on the morrow. I am on my cell.
ASKER
Thx for sticking with me on questions.
No worries. Glad I could help.
Windows Server 2012
Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.
21K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
1) Does your DR site have live users running on it at present?
2) In the event of complete failure at Main-Site will users be relocated to DR-Site? Or will they be still on Main-Site network?
The reason I ask these questions, if you have a domain controller that needs its IP changing, you will have a major headache updating sites and services, DNS, DHCP. You would then need to point your Main Site's DHCP helper to your backup site on your network device as well as ensure routing etc flowed correctly and DNS lookup would follow.
The easiest solution assuming users will stay at Main Site would be to fire up the VM on a local machine at Main Site (I have run a 2012 domain controller from my Dell Laptop before). The failover that you are proposing will not work easily.
How big a network are we talking about?