Configuring Hyper-V Replica Broker for a Failover Cluster
If you have either the primary, replica or extended replica server as a member of a Failover Cluster environment, you will need to configure the Hyper-V Replica Broker role. This role is necessary to enable a cluster to be part of a Hyper-V Replica so that it can support seamless replication. In this scenario, you can have a standalone server and a cluster working as primary or replica server, or a cluster for each.
When configuring a Hyper-V Replica for a virtual machine, a different virtual name called Client Access Point (CAP) must be used. The CAP is created during the Hyper-V Replica Broker configuration.
In this recipe, you will see how to configure Hyper-V Replica Broker to use your cluster servers in the Hyper-V Replica scenario.
Getting ready
You will need a Failover Cluster environment already configured with a cluster created as well. For more information on how to install and configure it, have a look at the Installing and...