Release Notes

On upgrading the Core from AppAssure 5.4.3 to Rapid

Recovery 6.0, the Core Console does not launch

automatically

Description After upgrading the Core from AppAssure 5.4.3 to Rapid Recovery 6.0, you are

prompted to restart the system. On restarting the system the startAA.vbs script

does not open the Core Console but displays a Windows Script Host error.

Workaround/

Solution

After upgrading to Rapid Recovery 6.0, manually start the Core Console by clicking

the icon on the desktop.

Error displayed when remounting volumes

Description When recovering a DVM repository the following error is displayed: Failed read

consistency lock on IsSpare_AC or

MediaPresent_DiskDriveToStorageExtent_AC Association Cache. The

error occurs when a repository was provisioned on several controllers and one of

the mount points was removed.

NOTE: Ensure you use the PERC H330 controller to provision storage.

Workaround/

Solution

1. Assign drive letters to volumes with storage locations of the repository.

2. Manually restore Core settings or Open Existing Repository through the

Repositories pane specifying valid paths for repositories.

Rapid Recovery 6.0 displays an error when ESX(i) host is

offline

Description After exporting ESX(i) virtual standby, if the state of ESX(i) host is offline, the error:

Unable to connect to the remote server now is displayed.

Workaround If an ESXi server backed Virtual Standbys exist, ensure all hosting ESXi servers are up

and operational.