Replicate or back up VMs not working

Hakim Fahadi 40 Reputation points
2026-11-17T09:30:01.56+00:00

Trying to replicate VM host for backup, but no way near success. Any help here?

Windows for business | Windows 365 Enterprise
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-17T09:32:09.53+00:00

    Run Test-VMReplicationConnection from the primary Hyper-V host first; its result will distinguish a host-to-host connectivity or authentication failure from a VM-specific replication problem.

    1. Test the replica connection

    Open PowerShell as Administrator on the Hyper-V host containing the source VM.

    For domain-joined hosts using Kerberos:

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

    For certificate authentication:

    Test-VMReplicationConnection `
      -ReplicaServerName "replica.contoso.com" `
      -ReplicaServerPort 443 `
      -AuthenticationType Certificate `
      -CertificateThumbprint "CERTIFICATE_THUMBPRINT"
    

    Use the port and authentication method configured on the receiving host. A successful test returns:

    The connection to the specified Replica server with the specified parameters was successful.
    

    These are Microsoft’s documented tests for a standalone replica host.^1^

    If this test fails, check the matching branch below before changing the VM.

    • Kerberos: Verify both hosts can resolve each other by FQDN, the configured HTTP port is reachable, domain trust is valid, and the Replica server permits replication from this primary server.
    • Certificate: Verify the certificate is not expired, has Client and Server Authentication EKUs plus a private key, chains to a trusted root, and its CN or SAN matches the replica host FQDN.^2^
    • Clustered destination: Use the Hyper-V Replica Broker FQDN, not an individual cluster-node name. Also verify that the Replica Broker role is online and its SPN is registered correctly.^3^

    2. Capture the actual VM replication state

    On the primary host, run:

    Get-VMReplication -VMName "YourVM" |
      Format-List VMName,State,Health,Mode,PrimaryServer,ReplicaServer,
                  ReplicaPort,AuthenticationType,LastReplicationTime
    
    Measure-VMReplication -VMName "YourVM" |
      Format-List *
    

    Alternatively, in Hyper-V Manager, right-click the VM and select Replication → View Replication Health. A Critical state means replication has stalled or failed and requires investigation; Warning generally means replication is working but lagging.^4^

    3. Find the exact failure

    On the primary host, open:

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

    Reproduce the failure, then record:

    • Event ID
    • Error code, such as 0x80070057 or 0x00002EFE
    • Full event message
    • Whether failure occurs while enabling replication, during initial replication, or after initial replication completed

    Hyper-V Replica commonly reports events such as 32022, 32086, 32000, and 33680; the code and message determine the appropriate correction.^3^

    4. If connectivity succeeds but the VM still fails

    Check these prerequisites on the destination host:

    1. The receiving host is enabled as a Replica server.
    2. Its authorization entry permits the primary host or applicable trust group.
    3. The destination storage path exists, is accessible, and has enough capacity for the VM configuration, all selected VHD/VHDX files, and any additional recovery points.
    4. The account performing setup belongs to Hyper-V Administrators or is a local administrator on both hosts.
    5. Security software is not blocking replication traffic or access to replication files.
    6. If either host was recently updated, check for version/configuration incompatibility and pending updates.

    Microsoft identifies network/authentication, Replica configuration, storage, permissions, security software, and damaged HRL files as distinct failure areas.^3^

    Do not delete replica VMs or HRL files until the event ID and error code identify corruption or a required rebuild; doing so discards the existing replica relationship and recovery history.

    Post the output from Test-VMReplicationConnection, Get-VMReplication, and the newest Hyper-V-VMMS/Admin error to narrow this to a specific correction.


    References

    1. Enable Hyper-V Replica on a single host
    2. Replicate a virtual machine with Hyper-V Replica
    3. Hyper-V Replica troubleshooting guide
    4. Replicate a virtual machine with Hyper-V Replica
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.