showing posts tagged with 'rapidrecovery'
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 RemoteReplicat  ...
by lunarg on April 26th 2017, at 10:35
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  ...
by lunarg on June 21st 2016, at 15:47
For some reason, if an upgrade of an AppAssure/Dell Rapid Recovery Agent is not succesfully completed or cancelled, a subsequent upgrade may fail with the following error message:

Destination path is not empty. Please choose another one.

If an upgrade was cancelled or has failed for some reason, the following upgrade attempt will try to perform a complete installation. Because not all files and/or folders have been removed, the installer will not continue and will display the error message.

To resolve the problem, manually remove the files and folders, but leave any registry keys intact to ensure a proper upgrade without losing any settings.

If it is running, stop the Agent or Core  ...
showing posts tagged with 'rapidrecovery'