This section applies to upgrading Rapid Recovery Core , Rapid Recovery Agent, and the Local Mount Utility. For documentation on upgrading other Rapid Recovery components, see the following:
If you do not see release 6.3 editions of the books referenced above, use the release 6.2 versions.
|
NOTE: As of release 6.3, Rapid Recovery no longer supports Kaseya Virtual System Administrator. There is no new version of the Rapid Recovery Third-Party Integration Guide. |
If upgrading from Rapid Recovery release 6.2 or later, you can use the Automatic Update feature to upgrade to this release, if it is enabled in your Core. Use of this feature requires you to consent to Quest using a limited amount of your personal data. For more details, see the topic "How Rapid Recovery uses personal information" in the Rapid Recovery 6.3 User Guide.
Due to parameters included as part of GDPR compliance in Rapid Recovery release 6.2 and later, customers using Rapid Recovery versions prior to 6.2 will not be able to use the Automatic Update feature to upgrade. You must manually upgrade the software one time instead. Once you have upgraded to Rapid Recovery release 6.2 or later and consented to the use of personal data, you can resume using the Automatic Upgrade feature.
The following table provides a visual guide of the compatibility between supported versions of Rapid Recovery Core and Rapid Recovery Agent.
Version | 6.1.3 Core | 6.2.1. Core | 6.3.0 Core |
---|---|---|---|
6.1.3 Agent | Fully compatible | Fully compatible | Fully compatible |
6.2.1 Agent | Not compatible | Fully compatible | Fully compatible |
6.3.0 Agent | Not compatible | Not compatible | Fully compatible |
Previous editions of this topic depicted compatible versions of Rapid Recovery Core and Rapid Recovery Agent, regardless of whether the release versions shown were currently supported.
The following hybrid chart shows supportability (using the color coding explained in the legend) as well as compatibility between Core and Agent versions since release 5.4.3.
|
NOTE: Future editions of this topic will only include the simplified supportability information shown in the preceding chart. |
Version | 5.4.3 Core1 | 6.0.2 Core | 6.1.33 Core | 6.2.1 Core | 6.3.0x Core |
---|---|---|---|---|---|
5.4.3 Agent1, 2 | Compatible | Compatible3 | Compatible3 | Compatible3 | Compatible3 |
6.0.2 Agent1, 2 | Not applicable | Compatible | Compatible3 | Compatible3 | Compatible3 |
6.1.34 Agent | Not applicable | Not applicable | Compatible | Compatible 3 | Compatible3 |
6.2.1 Agent | Not applicable | Not applicable | Not applicable | Compatible | Compatible3 |
6.3.0x Agent | Not applicable | Not applicable | Not applicable | Not applicable | Compatible3 |
Color Legend: | Full Support | Limited Support | Discontinued | Never Supported |
1 While not currently supported, AppAssure 5.4.3 and Rapid Recovery 6.0.2 are shown in this chart to convey interoperability. See note 4.
2 Protected machines with EFI partitions must be upgraded to Rapid Recovery release 6.0.x or later to successfully restore data, perform bare metal restore, or perform virtual export. To receive assistance from Quest Data Protection Support, Quest recommends upgrading to a supported release (generally, the latest release), as detailed in note 4.
3 Users can protect machines using older versions of Rapid Recovery Agent in a newer Core. Logically, newer features provided in more recent versions of Rapid Recovery Agent are not available for machines protected with older Agent versions installed.
4 As shown in this chart, Rapid Recovery supports the current version (6.3.0x), and the latest maintenance release of the last two major/minor versions (6.2.1 and 6.1.3, respectively). When a new maintenance release becomes generally available, it becomes fully supported. The prior version goes into limited support. For detailed information, see the "Product Life Cycle and Policies" section of the Rapid Recovery Support website at https://support.quest.com/rapid-recovery/.
Only the latest maintenance releases for the last two major/minor versions (N-1 and N-2 releases shown in table 11) are supported. For example, in release 6.3.0x, these versions include only releases 6.2.1 and 6.1.3. With the general availability of this release, other versions (such as releases 6.2.0, 6.1.2, 6.1.1, and so on) are now outside of the support policy. While Quest expects these versions to function, they may not have been tested for interoperability with the current version. If you have a current maintenance agreement, Quest Data Protection Support can attempt to answer your questions. However, if you call for support for an unsupported version, expect to be asked to upgrade.
Other factors affect interoperability. For example, the Rapid Snap for Virtual feature was first introduced in Rapid Recovery 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. Release 6.2 introduced agentless application support for protected machines running Exchange Server and SQL Server. Logically, users of Core version 5.4.3 cannot agentlessly protect any VMs. Users of Core version 6.0 cannot protect VMs on Hyper-V without installing the Agent software. And Cores earlier than release 6.2 have limited agentless support for Exchange and SQL Server, as detailed in the user guide topic "Understanding Rapid Snap for Virtual agentless protection" or "Understanding agentless protection" for each relevant release.
For more information about the differences between service levels supported for Rapid Recovery versus support levels generally for Quest products, see "Differentiation between standard Quest and Rapid Recovery service levels" in Rapid Recovery 6.3 Release Notes.
When upgrading from AppAssure to Rapid Recovery on your machines, or upgrading from one version of Rapid Recovery to a more recent version, it is important to be mindful of the following best practices:
If upgrading to Rapid Recovery Core release 6.3, you can continue to protect machines with older versions of Agent. If you have a current maintenance contract and are experiencing difficulties, contact Quest Data Protection Support for assistance with any release version covered under full or limited support.
To see Rapid Recovery software releases under full, limited, or discontinued support, and to understand those terms, refer to the product life cycle information on the Support website. Navigate to https://support.quest.com/rapid-recovery/, select the appropriate release in the product filter, and then click the "Product Life Cycle and Policies" tab.
To use any new features or enhancements in the latest Agent software, you must upgrade your protected machines to that version. Before upgrading, always make sure the operating system on the protected machine is supported. In general, Quest supports the latest generally available versions of Windows and many recent distributions of Linux. For specific information on supported operating systems, see the Rapid Recovery 6.3 System Requirements Guide.
|
NOTE: Quest recommends retaining the binary installer file for any currently installed Rapid Recovery software product. You can use this file in the future to reinstall, repair, or remove the software. |
|
NOTE: If you declined to share PII with Quest, you must obtain and register a non-phone home key before using your Core. For more information about managing your PII, the GDPR, the functions you cannot perform if you do not accept the use of personal data, and how to obtain a non-phone-home license, see the topic "Managing privacy" in the Rapid Recovery 6.3 User Guide. For more information about registering a phone-home or non-phone-home license with your Core, see Updating or changing a license. |
|
Caution: If automatic update notification is enabled, you may see a message in the Core Console of a source Core indicating that a newer version of the Core software is available. If the message also indicates that a replicated (target) Core has an earlier version, Quest recommends pausing replication on both Cores, manually upgrading first the target Core and then the source Core, and then resuming replication. If you see that message but opt to select Update Now on the source Core first, the next attempt to replicate will fail until you also upgrade the target Core. |
Before upgrading any Core server, please read the topic Preparing the Core server to upgrade.
© ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center