Replicate hyper-v

Validate that the destination storage path is accessible, healthy, and has enough free space for every replicated VHD before recreating the Hyper-V Replica relationship.

1. Check the destination storage

On the destination Hyper-V host, open PowerShell as Administrator and run:

Get-Volume |
  Format-Table DriveLetter, FileSystem, HealthStatus, OperationalStatus,
              Size, SizeRemaining -AutoSize

Get-PhysicalDisk |
  Format-Table FriendlyName, OperationalStatus, HealthStatus -AutoSize

Get-VirtualDisk |
  Format-Table FriendlyName, OperationalStatus, HealthStatus -AutoSize

The intended destination volume should:

• Be online and accessible from the destination host.
• Report a healthy operational state.
• Have space for the VM configuration, all selected VHD/VHDX files, and any additional recovery points.
• If clustered, be accessible by every node through a Cluster Shared Volume (CSV). Microsoft specifically identifies inaccessible paths, insufficient capacity, incompatible storage, and storage permissions as causes of Hyper-V Replica failures.^1^

For a cluster, also run:

Get-ClusterSharedVolume | Format-List *
Get-PhysicalDisk |
  Format-Table FriendlyName, CanPool, OperationalStatus, HealthStatus
Get-VirtualDisk |
  Format-Table FriendlyName, HealthStatus

If a disk reports unhealthy, is missing, or logs Event IDs such as 11, 129, 153, 5120, or 5142, address the storage path, HBA/MPIO, driver, firmware, or physical disk problem before attempting replication again.^2^

2. Configure the receiving host correctly

For two standalone Windows Server Hyper-V hosts, configure the destination:

1. Open Hyper-V Manager.
2. Select the destination host.
3. Select Hyper-V Settings → Replication Configuration.
4. Select Enable this computer as a Replica server.
5. Choose:
   • Kerberos (HTTP) when the hosts belong to the same or trusted AD domains.
   • Certificate-based authentication (HTTPS) for workgroup or untrusted-domain hosts.
6. Under Authorization and storage, authorize the source host and select the healthy destination storage path.
7. Enable the corresponding inbound firewall rule:
   • Hyper-V Replica HTTP Listener (TCP-In) for Kerberos.
   • Hyper-V Replica HTTPS Listener (TCP-In) for certificates.

The defaults are port 80 for Kerberos/HTTP and 443 for certificate-based HTTPS.^3^

Check the destination configuration:

Import-Module Hyper-V
Get-VMReplicationServer

The expected state is Online.

If the destination is a failover cluster, configure a Hyper-V Replica Broker instead of using an individual node name. Its storage path must be accessible by every cluster node, such as a CSV, and the broker must be Online.^4^

3. Test transport before enabling the VM

Run this on the source host, substituting the destination FQDN:

Test-VMReplicationConnection `
  -ReplicaServerName 'replica.contoso.com' `
  -ReplicaServerPort 80 `
  -AuthenticationType Kerberos

For certificate authentication, use port 443, Certificate authentication, and the appropriate certificate thumbprint. If this test fails, the problem is connectivity, firewall, authentication, DNS, or certificates—not the VHD destination path.^3^

4. Enable and inspect replication

In Hyper-V Manager on the source host:

1. Right-click the VM and select Enable Replication.
2. Enter the destination host FQDN—or the Replica Broker name for a cluster.
3. Select only the VHDs that need replication.
4. Choose the replication frequency and recovery-point policy.
5. Select Send initial copy over the network, or use external media when the VM is too large for the available link.
6. Finish the wizard and inspect Replication Health.

A Critical state means replication has stalled or failed. Check storage capacity/performance, connectivity, authentication, certificates, and event logs; then resume or resynchronize only after correcting the reported issue.^5^

Capture the exact failure from:

Event Viewer → Applications and Services Logs → Microsoft → Windows → Hyper-V-VMMS → Admin

Also run:

Get-VMReplication -VMName 'YourVM' | Format-List *
Measure-VMReplication -VMName 'YourVM'

The exact event ID, hexadecimal error code, Windows Server versions, standalone-versus-cluster configuration, and destination storage type are required to identify whether “storage” means insufficient capacity, an inaccessible path, permissions, disk health, or replication-log corruption.

References

1. Hyper-V Replica troubleshooting guide
2. Troubleshoot storage issues in Hyper-V and Windows Server failover clusters
3. Enable Hyper-V Replica on a single host
4. Enable Hyper-V Replica on a failover cluster
5. Replicate a virtual machine with Hyper-V Replica