Operation timed out: 14580 seconds
2025-01-06T11:39:02.359+05:30 verbose vmware-dr[01237] [SRM@6876 sub=HbrRecoveryEngine opID=b66d8a0a-9e07-43f0-ae63-4dd421d15a3c-reprotect:b53a:e8ea:2f9b:6d14-onlineSync:2f27] [52f24] Sync: Using sync time out of 7200 seconds.
2025-01-06T15:39:02.428+05:30 verbose vmware-dr[01238] [SRM@6876 sub=RemoteTask.dr.hbrProvider.HmsProxy.remoteSync48 opID=b66d8a0a-9e07-43f0-ae63-4dd421d15a3c-reprotect:b53a:e8ea:2f9b:6d14-onlineSync:2f27 tid=dr.hbrProvider.HmsProxy.remoteSync48.HmsRemoteSync] The remote task 'vim.Task:19f9e716-4a4d-4f30-afd4-9fb50254a3d2:dr.hbrProvider.HmsProxy.remoteSync48' timeout passed. _updated=true
VMware Site Recovery Manager 8.x
VMware Live Site Recovery 9.x
The default timeout value was insufficient for the synchronization process to complete, leading to a timeout error after 14580 seconds
This may be caused due to:
vrReplication.synchronizationTimeout
is a configurable parameter in vSphere Replication, that defines the maximum allowed time (in seconds) for a replication synchronization operation to completevrReplication.synchronizationTimeout
value is set to default 7200 seconds.vrReplication.synchronizationTimeout
= 14400 seconds (4 hours).remoteManager.taskProgressDefault
Timeout is set to 180 seconds by default.vrReplication.synchronizationTimeout
to 10800 seconds (3 hours) instead of the default 7200 seconds (2 hours).vrReplication.synchronizationTimeout
is changed from 7200 to 10800, total timeout is then adjusted to 2 x vrReplication.synchronizationTimeout
= 21600 To increase the vrReplication.synchronizationTimeout
value on both the sites go to the Advanced Settings section.