Why is the “Hyper-V Replica Broker” required?

Hyper-V Replica requires the Failover Clustering role Hyper-V Replica Broker to be configured if either the primary or replica Hyper-V server is part of a cluster. This post builds on top of the guide and explains *why* the broker is required and captures its high level behavior.

The following example will be used through the rest of the article:

  • Cluster-P – Failover Cluster      in city 1
  • P1, P2, P3      (.contoso.com) – names of the cluster nodes on a cluster Cluster-P
  • P-Broker-CAP.contoso.com – the client access      point of the broker on Cluster-P
  • VirtualMachine_Workload – the name of the      virtual machine running on Cluster-P
  • Cluster-R – Failover Cluster      in city 2
  • R1, R2      (.contoso.com) – names of the cluster nodes on the Cluster-R
  • R-Broker-CAP.contoso.com – the client access      point of the broker on Cluster-R

Unified View

  • On Cluster-R;      P-Broker-CAP.contoso.com is added to the list of authorized      servers rather than adding P1, P2, P3 (.contoso.com) individually.
  • When enabling      replication for any virtual machine on the primary server, the client      access point of the broker on the replica server is used (and not the      replica server name)
  • When a      replicating virtual machine migrates within the Cluster-P,      the destination server is automatically authorized to send replication      traffic
  • When new nodes are added      to the Cluster-P, there is no change required on replication      settings (specifically the authorization table) on Cluster-R

Initial Node placement

  • When replication      is enabled for the primary virtual machine, the primary server contacts R-Broker-CAP
  • The request is      authenticated and authorized. R-Broker-CAP then picks a      random node fromits cluster Cluster-R after      validating whether the host node is available and if the Virtual machine      Management Service is running. It returns the node name (eg:      R2.contoso.com) to the primary server
  • The primary      server now starts replicating to this node (R2.contoso.com)

Making the replica virtual machine, HA

As part of creating the replica virtual machine, the Hyper-V Replica Broker is also responsible for making the virtual machine highly available. If the node crashes, the Failover Cluster Service would move replica the Virtual machine, thereby protecting the replica Virtual machine and the replication process from host crashes on the Cluster-R.

Redirect traffic in case replica virtual machine migrates

  • If the replica      virtual machine migrates from one node (eg: R1.contoso.com) to another (eg:      R2.contoso.com), the primary server falls back to the broker R-Broker-CAP      with the question “where is the replica for the virtual machine VirtualMachine_Workload
  • The broker      locates the virtual machine in the cluster and returns the node name      (R2.contoso.com) to the primary server.
  • The primary      server sends its subsequent requests to R2.contoso.com – the replication      is re-established with no manual intervention.

Provide centralized management of the replication settings

  • For a cluster on the      replica site, the replication settings are configured via the Replication      Settings which is available on clicking the Broker role in the Failover      cluster console.
  • The Broker role      writes the replication configuration to the cluster database and triggers      a notification.
  • Virtual machine      Management Service on each node picks up the configurations and each node      is now working with the latest copy of the replication settings.

Configure the Broker using PS cmdlet

·         Issue the following cmdlets to configure the broker:

$BrokerName = “P-Broker-CAP”

Add-ClusterServerRole -Name $BrokerName

Add-ClusterResource -Name “Virtual Machine Replication Broker” -Type “Virtual Machine Replication Broker” -Group $BrokerName

Add-ClusterResourceDependency “Virtual Machine Replication Broker” $BrokerName

Start-ClusterGroup $BrokerName

Written by Marcos Nogueira

Marcos Nogueira

With more than 18 years experience in Datacenter Architectures, Marcos Nogueira is currently working as a Principal Cloud Solution Architect. He is an expert in Private and Hybrid Cloud, with a focus on Microsoft Azure, Virtualization and System Center. He has worked in several industries, including Aerospace, Transportation, Energy, Manufacturing, Financial Services, Government, Health Care, Telecoms, IT Services, and Gas & Oil in different countries and continents.

Marcos was a Canadian MVP in System Center Cloud & Datacenter Managenment and he has +14 years as Microsoft Certified, with more than 100+ certifications (MCT, MCSE, and MCITP, among others). Marcos is also certified in VMware, CompTIA and ITIL v3. He assisted Microsoft in the development of workshops and special events on Private & Hybrid Cloud, Azure, System Center, Windows Server, Hyper-V and as a speaker at several Microsoft TechEd/Ignite and communities events around the world.

Leave a Reply

Your email address will not be published. Required fields are marked *