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 RemoteReplicat  ...

After updating Rapid Recovery to 6.1, you will notice the reporting Powershell scripts (such as Reports.ps1) no longer work.

When running such a script, the following error is generated:

Exception calling "LoadFrom" with "1" argument(s): "Could not load file or assembly 'file:///C:\ProgramFiles\AppRecovery\Core\CoreService\coreadmin\bin\Reporting.Implementation.dll' or one of its dependencies. The systemcannot find the file specified."

This is caused by several auxilliary script files not being updated as part of the general 6.1 release of Rapid Recovery, causing the reporting scripts (such as Reports.ps1) not to work properly.

To resolve, you can either dow  ...