Cluster role to create on Cluster2: Hyper-V Replica Broker. Replication target name to specify: The name of the Hyper-V Replica Broker.

When Hyper-V Replica is used with a clustered Hyper-V host as either the primary or the replica site, that cluster requires a Hyper-V Replica Broker role, because the broker abstracts away which specific physical node currently owns a given replicated virtual machine, keeping replication working correctly even as VMs live-migrate or fail over between nodes within the cluster. Before enabling replication, an administrator must create this Hyper-V Replica Broker role on Cluster2 and configure its replication settings, including the authentication method, the storage location for replica virtual machine files, and which primary servers are allowed to replicate to it. When subsequently configuring replication for the virtual machines on Cluster1, the destination (replica server) must be specified using the Hyper-V Replica Broker ' s own client access point name -- not the name of an individual physical node in Cluster2 -- because the broker, not any single node, is what tracks current VM ownership as virtual machines move between Cluster2 ' s nodes. Specifying an individual node name instead would break replication and failover as soon as a VM ' s ownership moved to a different node in Cluster2.