Reprotect Fails with an error "Operation times out: 7200 seconds VR synchronization failed for VRM group <Unavailable>. Operation timed out: 7200 seconds".
Article ID: 368233
Updated On:
Products
Issue/Introduction
After a failover or failback, running re-protect on a recovery plan that uses vSphere Replication for VM replication may result in a timeout error.
Re-protect operations on these recovery plans fail with the error: "Operation times out: 7200 seconds. VR synchronization failed for VRM group <Unavailable>. Operation timed out: 7200 seconds."
In the ESXi Host vmkernel logs you see timeout error messages:
/var/log/vmkernel.log
vmkernel.log
2025-06-28T08:03:49.683Z cpu23:7487659)WARNING: Hbr: 893: Failed to receive from 10.x.x.x (groupID=GID-xxxxxxxxxxxxxxxxxxxxx): Timeout
2025-06-28T08:04:11.746Z cpu23:7487659)Hbr: 2540: Wire compression supported by server 10.x.x.x : FastLZ
2025-06-28T08:04:12.085Z cpu23:7487659)Hbr: 6591: Got requirements from server = 0x0
Environment
This kind of behavior is observed on the environments where vSphere Replication is being used for replication of VMs.
Cause
When you run re-protect, Site Recovery Manager updates vSphere Replication to change the replication direction for the VM and updates this information for the protection group and the recovery plan. If the replication takes more to complete than the default value (2 hours), the re-protect process in Site Recovery Manager will get timeout. The default timeout value is 2 hours this value can be adjusted if you encounter timeout errors when vSphere Replication synchronizes virtual machines on the recovery site.
Resolution
Increase the vrReplication.synchronizationTimeout and vrReplication.reverseReplicationTimeout timeout values in Advanced Settings.
- In the vSphere Client, click Site Recovery > Open Site Recovery.
- On the Site Recovery home tab, select a site pair, and click View Details.
- In the left pane, click Configure > Advanced Settings > vSphere Replication.
- Select a site, and click Edit to modify the vSphere Replication settings.
Once the above parameters are changed, re-run the re-protect task which should be successful.
For more details, please refer the below document :
Feedback
