Return
-
Title
Increasing Replication Timeouts -
Description
The replication timeout settings are controlled by the registry and can be extended. -
Resolution
Please follow the steps below on both Source and Target Cores for sustained replication errors:
1) Stop the Cores' service.
2) Increase the next timeouts on the master and target cores to 30 minutes and restart both (Source and Target services):
- HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Replication\ReplicationService\RemoteReplicationSyncJobTimeout
- HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Replication\ReplicationService\VolumeImageSessionTimeout
3) Increase the following Core timeout settings via registry editor:
- HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreSettings\ClientTimeoutSettings\ConnectionTimeout
- from 00:05:00 to 00:15:00
- HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreSettings\ClientTimeoutSettings\ReadWriteTimeout
- from 00:05:00 to 00:15:00
- HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreSettings\ClientTimeoutSettings\ConnectionUITimeout
- from 00:05:00 to 00:15:00
- HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreSettings\ClientTimeoutSettings\ReadWriteUITimeout
- from 00:05:00 to 00:15:00
- HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Replication\ReplicationService
- MaxParallelStreams – 4
- RemoteReplicationSyncJobTimeout – 00:30:00
- VolumeImageSessionTimeout – 01:00:00
4) Start the Cores' service.