Share via

Hyper-V Troubleshooting: Resume Replication Fails with critical status message in a cluster

  • Article

Event Details:

Hyper-V suspended replication for virtual machine <VMName> due to a non-recoverable failure. (Virtual Machine ID <VMId>). Resume replication after correcting the failure.

Event ID:32552

Description: Hyper-V could not replicate changes for virtual machine <VMName> because the Replica server refused the connection. This may be because there is a pending replication operation in the Replica server for the same virtual machine which is taking longer than expected or has an existing connection. (Virtual machine ID <VM ID>)

Event ID: 32022

Description: Hyper-V could not replicate changes for virtual machine <VMName>': The operation timed out (0x00002EE2). (Virtual Machine ID <VM Id>)

Possible Causes:

1. Storage Space is not sufficient on the Replica Side.

2. A power failure on the replica side and Replica Server restarted. This might cause iSCSI session to get disconnected and when it resumed after a restart, there was a lot of replica data which has to replicate over a limited bandwidth causing replication to fail and leaving Replication health status as Critical.

Resolution:

1. Check the disk space on the replica cluster site. Increase free CSV space and try resuming replication.

2.  Pause Replication on other VMs and resume replication on VM by VM basis to make sure that enough bandwidth is available over the network for all the pending replication data to get transferred to recovery server post re-start of recovery server.