Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - Release Notes

Getting started with Rapid Recovery

These topics provide information you can use to begin protecting your data with Rapid Recovery.

Topics include:

Rapid Recovery Core and Agent compatibility

The following table provides a visual guide of the interoperability between Core and Agent software versions. This table lists versions tested for release 6.1.2.

Table 22. Interoperability between Core and Agent versions

AppAssure 5.4.3 Core

Rapid Recovery 6.0.2 Core

Rapid Recovery 6.1.1 Core

Rapid Recovery 6.1.2 Core

AppAssure 5.4.3 Agent1

Fully compatible

Fully compatible

Fully compatible2, 3

Fully compatible2, 3

Rapid Recovery 6.0.2 Agent

Not compatible

Fully compatible

Fully compatible3

Fully compatible3

Rapid Recovery 6.1.1 Agent

Not compatible

Not compatible

Fully compatible

Fully compatible 3

Rapid Recovery 6.1.2 Agent

Not compatible

Not compatible

Not compatible

Fully compatible

1 EFI partitions on protected machines must be upgraded to Rapid Recovery Agent release 6.0.x or later to successfully restore data, perform bare metal restore, or perform virtual export.

2 Release 6.1 release notes erroneously indicated that 5.4.3 Agent in 6.1.0 Core was not supported. This configuration is tested and supported. See Note 1.

3 Users can protect machines using older versions of the Agent software in a newer Core. Logically, newer features provided in more recent versions of Rapid Recovery Agent are not available for machines protected with older versions of Agent installed.

The matrix shows releases that have been fully tested with this release, and represent fully supported releases, plus the most recent prior release (6.1.1). Other software versions in limited support status (such as releases 6.0.1 and 6.1) have not been tested for interoperability, but are also expected to work.

Other factors affect interoperability. For example, the Rapid Snap for Virtual feature was first introduced in Rapid Recovery Core version 6.0, letting you protect VMware ESXi VMs agentlessly. Rapid Recovery release 6.1.0 expanded this support to host-based protection for Hyper-V VMs. Logically, users of Core version 5.4.3 cannot agentlessly protect any VMs. And users of Core version 6.0 cannot protect VMs on Hyper-V without installing the Agent software.

Upgrade and installation instructions

Quest recommends users carefully read and understand the Rapid Recovery Installation and Upgrade Guide before installing or upgrading. Specifically, when upgrading, read all topics in the chapter Upgrading to Rapid Recovery. For new installations, read all topics in the chapter Installing Rapid Recovery.

Additionally, Quest requires users to carefully review the release notes for each release, and the Rapid Recovery system requirements for that release, prior to upgrading. This process helps to identify and preclude potential issues. Since the release notes are updated last of all the product documents for each release, it is your best source for updated system requirements.

If upgrading from AppAssure Core release 5.4.3, or Rapid Recovery Core release 6.0.x or 6.1.x, then run the latest Core installer software on your Core server. If using replication, always upgrade the target Core before the source Core.

To protect machines using the Agent software, if upgrading from AppAssure Core release 5.4.3, or Rapid Recovery Core release 6.0.x or 6.1.x, run the latest Rapid Recovery Agent installer on each machine you want to protect. For more information, see the subtopic Protection.

You can also use the Rapid Snap for Virtual feature to protect virtual machines on supported hypervisor platforms agentlessly. Important restrictions apply. For more information on benefits or restrictions for agentless protection, see the topic Understanding Rapid Snap for Virtual in the release 6.1 edition of the Rapid Recovery User Guide.

Quest Software policy is to support two previous major/minor releases of Rapid Recovery. If you want to upgrade an older version, best practice is to first upgrade to the fully supported release (Rapid Recovery Core release 6.0.2), or the one prior (AppAssure Core release 5.4.3). You can then run the 6.1.2 installer for the appropriate Rapid Recovery software component.

For more information, see the Rapid Recovery Installation and Upgrade Guide.

When upgrading a protected Linux machine from AppAssure Agent to Rapid Recovery Agent version 6.x, you must first uninstall AppAssure Agent. For more information and specific instructions, see the Rapid Recovery Installation and Upgrade Guide.

To download the Rapid Recovery Core software, you must have an account registered on the license portal. Upon successful registration, you can then download the software, carefully review the Rapid Recovery system requirements, and install a Rapid Recovery Core.

Licensing

Trial versions of Rapid Recovery Core may include a temporary license key. A license key is required to perform uninterrupted backups, replication, or data restoration. For more information, see the following resources:

For complete details on licensing, see the Rapid Recovery License Portal User Guide.

Protection

To protect any physical or virtual machine (except VMs on VMware vSphere), you must install the Rapid Recovery Agent software. You can download Rapid Recovery Agent from the license portal to install on each machine you want to protect. You can also deploy Agent to the machines you want to protect from a properly configured Rapid Recovery Core.

If using a VMware vSphere host for your Core and protected machines, in many cases, you have the option to protect your machines without installing Rapid Recovery Agent. If using agentless protection, some limitations apply (especially for SQL Server or Exchange servers). For more information about these limitations, see the topic Understanding agentless protection in the Rapid Recovery User Guide.

Add your machines to protection on the Rapid Recovery Core by using the Protect Machine or Protect Multiple Machines wizard.

NOTE: Before protecting a cluster, you must first create a repository. For more information, see the topic Creating a DVM repository in the in the Rapid Recovery User Guide. Although a repository is also required to protect a machine, you have the option to create a repository during the workflow for protecting a machine.

Additional resources

Additional information is available from the following:

Related Documents