by lunarg on September 21st 2017, at 09:54

Quest Rapid Recovery provides the ability to replicate restore points to off-site location. More than often, connectivity to these locations has limited bandwidth and is sometimes even unstable. Unfortunately, Rapid Recovery doesn't do well with unstable connectivity: more than often, replication jobs abort because of high latency. Luckily, you can tweak the timeout parameters through the registry:

  • HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreSettings\ClientTimeoutSettings
    Increase the values of ReadWriteTimeout and ConnectionTimeout to 1 hour.
  • HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Replication\ReplicationService
    Increase the values of VolumeImageSessionTimeout and RemoteReplicationSyncJobTimeout to 1 hour.

This should improve replication stability somewhat. Additionally, avoid setting the concurrent outgoing replications jobs to high. Sometimes, setting it to 1 is better, allowing the replication to work sequentially (done in Settings > Jobs).