Hyper-V Replica Broker Configuration Lab By Yung Chou, Microsoft Platform Evangelist,

Transcription

1 Page 1 of 23 Hyper-V Replica Broker Configuration Lab By Yung Chou, Microsoft Platform Evangelist, Windows Server 2012 Hyper-V Replica is a built-in mechanism for replicating Virtual Machines (VMs). It can replicate selected VMs in real-time or asynchronously from a primary site to a designated replica site across LAN/WAN. Here a replica site hosts a replicated VM while an associated primary site is where the source VM runs. And either a replica site or a primary site can be a Windows Server 2012 Hyper-V host or a Windows Server 2012 Failover Cluster. Hyper-V Replica is an attractive Business Continuity and Disaster Recovery (BCDR) solution since not only conceptually easy to understand, but technically straightforward to implement, as demonstrated by the following schematic and the lab introduced later in this article. Further, with many newly added capabilities and flexibilities in Windows Server 2012 such as Storage Space, continuously available file share, Hyper-V over SMB 3.0, etc. a BCDR is no longer an academic exercise, but with Hyper-V Replica a feasible solution within reach. It is an ideal and affordable BCDR solution for small and medium businesses. Hyper-V Replica is also applicable to a failover cluster. And this lab, details the processes, steps, and operations in implementing Hyper-V Replica Broker in failover cluster settings. For those who are new to Hyper-V Replica, a walk-through of Hyper-V Replica essentials is available at

2 Page 2 of 23 Hyper-V Replica Broker With a failover cluster of Hyper-V hosts in place, one needs to first configure a Hyper-V Replica Broker role using Failover Cluster Manager. Then enable Hyper-V Replica on the Hyper-V Replica Broker. Ordinarily, Hyper-V Replica can be enabled in the Hyper-V Settings of a Hyper-V Host. However in a failover cluster, the Hyper-V Replica configurations are grayed out in an individual Hyper-V host s Hyper-V Settings and to be managed through the Hyper-V Replica Broker role configured with Failover Cluster Manager. The schematic below depicts that the employment of a Windows Server 2012 Hyper-V failover cluster as a Hyper-V Replica Site is through the cluster role, Replica Broker. Instead of operating directly onto a Hyper-V host as in a nonclustered environment, the process of replicating a VM is to now specify a Replica Broker as a replica site. The Replica Broker will then place the VM onto the associated failover cluster storage accordingly. Windows Active Directory domain is not a requirement for Hyper-V Replica which can be implemented between workgroups or domains with a certificate-based authentication without the need to establish a domain trust relationship. Active Directory is nevertheless a requirement if involving a Hyper-v host which is part of a failover cluster, and in such case all Hyper-V hosts of a failover cluster must be in the same Active Directory domain.

3 Page 3 of 23 Step-by-Step, Screen-by-Screen Hands-On Lab With a failover cluster of Windows Server 2012 Hyper-V hosts, we now will enable VM replication in Hyper-V Replica Broker which is a cluster role to be configured with Failover Cluster Manager. This lab assumes a Windows Server 2012 Hyper-V failover cluster is in place, and presents the processes, steps, and operations as the following. A pdf version of this lab guide is available at Configuring Hyper-V Replica Broker Role and Populating Replication Configuration In Failover Cluster Manager, first configure a Hyper-V Replica Broker role. Notice only one Hyper-V Replica Broker per failover cluster.

4 Page 4 of 23 Name the Hyper-V Replica Broker and specify the IP addresses. Review the configuration summary prior to confirmation.

5 Page 5 of 23 Upon completion, a configuration report becomes available/

6 Page 6 of 23 As indicated in the report, the next step is to configure the Replication Settings of the Hyper-V Replica Broker.

7 Page 7 of 23 At this time, the Hyper-V Replica Broker is running and click the Replication Settings from the Actions pane.

8 Page 8 of 23 If using a different port, need to set firewall rule on the port to allow incoming replication traffic. Use a CSV or file share to store Replica files. And here a wild card is placed for Primary Server field to include all servers in itprosrock.com. Windows Firewall rules are to be enabled on both nodes of the cluster.

9 Page 9 of 23 In a command prompt, type wf.msc to bring up Windows Firewall with Advanced Security. Scroll down to highlight and enable both rules. Do this on both nodes of the failover cluster. At this time, the Hyper-V Settings of each Hyper-V Host of the failover cluster will now how Replication Configuration with populated settings. Replication Configuration remains grayed out since it must be managed through Hyper-V Replica Broker in a failover cluster. This failover cluster is now ready for accepting and processing Hyper-V Replica traffic.

10 Page 10 of 23 Replicating VM to Hyper-V Replica Broker To replicate a VM, right-click the source in Hyper-V Manager and enable replication.

11 Page 11 of 23 Next

12 Page 12 of 23 Specify an intended Hyper-V Replica Broker. Since this is in an AD environment, supposedly the machine name should suffice for resolving the name. Here, I enter the FQDN for clarity.

13 Page 13 of 23 If employing a different port, at the Replica site as applicable Windows Firewall rules should include a defined rule to accept incoming replication traffic on the particular port. Compression is available.

14 Page 14 of 23

15 Page 15 of 23 The initial copy of a replication can be sent immediately in real-time or later as scheduled> An initial copy can be delivered over the wire, with external media like a DVD, or a VM on the Replica site. Once an initial copy is put in place, subsequently only deltas are sent.

16 Page 16 of 23 If a VM is with multiple VHDs, replicate the OS disk to ensure the VM will boot upon failing over.

17 Page 17 of 23 Here the VM is sent in real-time over the wire. Upon replicated, the VM is registered in Failover Cluster Manager and shut down.

18 Page 18 of 23 Testing Failover from Hyper-V Replica Broker This simulates a failover within the cluster. This will create a test VM based on the indicated recover point.

19 Page 19 of 23 A test VM is with the suffix, - Test. Start the test VM to ensure a successful simulated failover. Later stop testing failover. The test VM is to be automatically deleted.

20 Page 20 of 23 The test VM is deleted.

21 Page 21 of 23 Executing Planned Failover from Primary Site Here the primary site is DEVELOPMENT. A planned failover is to be carried out on a selected VM due to scheduled datacenter maintenance. To do a planned failover, the source VM must be shut down first. Here once failed over, start the replica VM.

22 Page 22 of 23 All went well and the source VM has been replicated. Indeed the replicated VM in Failover Cluster Manager at the Replica site is automatically started in a planned failover scenario which also automatically reverses the replication. Check the Replication Health to verify the reverse replication.

23 Page 23 of 23 Replication Health of the replica shows 1 replication cycle has completed with HyperV1.itprosrock.com (a cluster node of the failover cluster) as the Primary, i.e. source, server while DEVELOPMENT.itprosrock.com as the replica, i.e. destination, server.