-
Title
Replication fails with "Call to service" - Remote replication core timeout -
Description
Replication fails due the the timeout threshold being reached.
Call to service method https://FQDN:8006/apprecovery/api/core/replicationcomms/slave/agents/replicationJob/sync POST failed: Service method call timed out
OR
Error: replay.core.contracts.replication.unabletoconnecttoremoteserverexception unable connect remote server
-
Cause
The timeout threshold for the replication was reached. This timeout references 'no response' between the cores, it does not refer to the longevity of the job running (for which there is no timeout for).
-
Resolution
Windows Registry Disclaimer:
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
There is a threshold timeout for the jobs, stating how long the job will wait without response from the target side. This can be modified through the registry. To adjust this setting, modify the following (this will interrupt service for your jobs):- Suspend the replication jobs between the 2 affected cores, and then stop the core service on both the Cores.
- Open up regedit (this will be done on both cores) and backup the current registry of HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Replication\ReplicationService
- Modify the following keys to reflect what is listed below:
- VolumeImageSessionTimeout - from 15 mins, change to 01:00:00 Do not change the time to 60 minutes.
- RemoteReplicationSyncJobTimeout - change to 00:30:00
- RemoteReplicationSyncJobPoolingTime - change to 00:00:10
- Max. parallel streams - change to 1
- Start the core service on both cores and resume replication.