Category: Hyper-V Replica Broker


Troubleshooting Hyper-V Replica

Introduction to Troubleshooting Hyper-V Replica This section explains how to troubleshoot Hyper-V Replica.  Use this guide when: You have problems with connectivity between Primary and Replica servers You have problems enabling a virtual machine for replication You have problems with virtual machine replication whether it is Initial Replication (IR) or Delta Replication (DR) You have problems executing management actions associated with virtual machines on a Primary or Replica server You...


General Methodology for Troubleshooting Hyper-V Replica

Hyper-V Replica connectivity issues between Primary and Replica servers Symptom:  Hyper-V Replica functionality is disrupted and the Hyper-V VMMS\Admin log reports general network connectivity errors between the Primary and Replica server Verify the Replica server is booted and running. Check network connectivity and name resolution functionality between the Primary and Replica server by executing ping and nslookup tests.  If ping test fails, resolve network connectivity issues.  If name resolution fails,...


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...