Chat now with support
Chat with Support

Rapid Recovery 6.2 - Release Notes

Rapid Recovery 6.2 Release Notes New features Enhancements Deprecated in this release Resolved issues Known issues System requirements reference Licensing Rapid Recovery software and appliances Getting started with Rapid Recovery Globalization About us

Deprecated in this release

This section includes a list of features, items, or related components that are deprecated in Rapid Recovery release 6.2.

Central Management Console deprecated

Rapid Recovery release 6.2 includes the production rollout of the Data Protection Portal. This feature, particularly useful for managed service providers, lets you manage multiple Cores; access a dashboard where you can monitor tasks and events, view repository status, and check system health; generate reports; and perform a growing list of other functions from a single web-based user interface. This new web-based portal is currently accessible to Rapid Recovery users with a current maintenance agreement. Its ability to manage multiple Rapid Recovery Cores from a central location replaces the functionality of the now-deprecated Central Management Console.

If you manage two or more Cores in release 6.2, Quest recommends that you migrate to the Data Protection Portal. Only the new portal is supported for management of release 6.2 Cores.

As of release 6.2, the Central Management Console is now in limited support only. Topics related to the Central Management Console have been removed from technical documentation. If you are no longer using this component, as a best practice, Quest recommends uninstalling the Central Management Console.

In Rapid Recovery Core release 6.2, the Data Protection Portal Core setting lets you enable or disable connection with the portal.

Integration between the Rapid Recovery Core Console and the Data Protection Portal is enabled by default. To view the current connection setting, disable, or enable the connection for any Core, navigate to Settings in the Core Console and view or change the Data Protection Portal configuration.

If using a Core version older than release 6.2, you must download a plug-in that lets your Core connect to the portal. When you log in to the Data Protection Portal from any Core server, you can download and install the appropriate plug-in for your Core version. The plug-in lets you manage multiple Cores, and is backward compatible with currently supported versions of Rapid Recovery Core.

For more information about the Data Protection Portal, see in-product help for the Data Protection Portal.

Synchronous replication no longer supported

Earlier versions of this product (prior to AppAssure 5.4.1) supported only synchronous replication, in which there was a single retention policy between source and target Cores. Asynchronous replication mode—the capability to support disparate retention policies—was introduced in release 5.4.3, and has been the standard for every release since. The old mode was deprecated.

As of Rapid Recovery release 6.2, support for the old synchronous replication mode is discontinued. When upgrading earlier releases, the Core installer checks a registry key to verify if a DVM repository integrity check is required. If so, you are notified that you must perform an integrity check. This check is only required if your DVM repository was created prior to release 5.4.1, if you used replication at that time, and if the integrity check was not previously performed.

For more information, see the Rapid Recovery User Guide topic "About checking the integrity of DVM Repositories." For details on manually performing the integrity check, see the procedure for "Performing an integrity check on a legacy DVM repository."

Operating system support changes

Rapid Recovery release 6.2 includes upgrades of the .NET framework from version 4.5.2 to version 4.6.2. Additionally, support has been added in release 6.2 for Secure Hash Algorithm 2 (SHA2). This certificate security protocol is stronger and generates a longer hash, and is used for Rapid Recovery drivers. Because of these incremental improvements, and because of required libraries and binary limitations, older Windows versions that do not fully support these requirements are no longer supported as of Rapid Recovery release 6.2.

The changes in OS support are documented below. For a full list of operating systems and the Rapid Recovery components supported for each, refer to the Rapid Recovery System Requirements Guide topic "Rapid Recovery release 6.2 operating system installation and compatibility matrix."

If you currently protect machines with an operating system that is no longer supported, you have two options:

1.
You can upgrade the OS on the machines you want to protect to a supported OS, then upgrade Rapid Recovery Agent to release 6.2 and continue to protect the machine on your release 6.2 Core.
2.
You can protect the machine on a release 6.2 Core using an older but supported version of Rapid Recovery Agent (such as 6.1.3). Of course, in such cases, new release 6.2 features are not available for that protected machine and are not supported.

The following Windows operating system support changes apply to Rapid Recovery release 6.2:

Windows XP. As in release 6.1.3, Core and Agent are not supported for machines running this OS. Rapid Recovery now no longer supports agentless protection or URC restore for machines with this OS.
Windows Vista. As in release 6.1.3, Core and Agent are not supported for machines running this OS. Rapid Recovery now no longer supports agentless protection or URC restore for machines with this OS. This OS is not supported.
Windows Vista SP2. As in release 6.1.3, Core is not supported for machines running this OS. Rapid Recovery now no longer supports protection for machines with this OS using Agent or agentless. LMU, Mailbox Restore, and DocRetriever for SharePoint are no longer supported on this OS.
Windows 7. As in release 6.1.3, Core and Agent are not supported for machines running this OS. Support for this operating system is discontinued. Rapid Recovery no longer supports agentless protection, URC restore or URC driver injection for machines with this OS.
Windows 7 SP1. Core and Agent are no longer supported for machines running this OS with Service Pack 1. LMU, Mailbox Restore, and DocRetriever for SharePoint are no longer supported on this OS. Limited support is provided only for agentless protection, URC restore, and VM export to Azure, which works only for 64-bit installations.
Windows 8. Core and Agent are no longer supported for this OS. Limited support is provided only for agentless protection, URC restore, and VM export to Azure (which works only for 64-bit installations).
Windows 8.1. Core is supported for this OS . Agent and agentless protection support continues. VM export to Azure works only for 64-bit installations.
Windows 10. Core is supported for this OS . Agent and agentless protection support continues. The previous incompatibility with virtual exported to VirtualBox (in which SCSI controller drivers were missing for Windows 10) has been corrected. VM export to Azure works only for 64-bit installations.
Windows Server 2003. As in release 6.1.3, Core and Agent are not supported for machines running this OS. Support for agentless protection for VMs with this operating system is limited, as is URC restore. No other aspects of this OS are supported.
Windows Server 2008. As in release 6.1.3, Core and Agent are not supported for machines running this OS. Support for agentless protection for VMs with this operating system is limited, as is URC restore. VM export to Azure works only for 64-bit installations.
Windows Server 2008 SP2. Core and Agent are no longer supported for machines running this OS. Support for agentless protection for VMs with this operating system is now limited, as is URC restore. VM export to Azure works only for 64-bit installations.
Windows Server 2008 R2. As in release 6.1.3, Core and Agent are not supported for machines running this OS. Support for agentless protection for VMs with this operating system is now limited, as is URC restore. URC driver injection is no longer supported. VM export to Azure works only for 64-bit installations.
Windows Server 2008 R2 SP1. Core is supported for this OS, provided you follow guidance in Microsoft KB 3033929. Silent installation of Core is not supported. Agent and agentless protection are supported on this OS. VM export to Azure works only for 64-bit installations.
Windows Server 2012. Core, Agent, and agentless protection are supported on this OS . VM export to Azure works only for 64-bit installations.
Windows Server 2012 R2. Core, Agent, and agentless protection are supported on this OS. VM export to Azure works only for 64-bit installations.
Windows Server 2016. Core, Agent, and agentless protection are supported on this OS. VM export to Azure works only for 64-bit installations.

The following Linux operating system support changes apply to Rapid Recovery release 6.2:

Ubuntu Linux 12.04 LTS, 12.10, 13.04, 13.10, 14.10, 15.04, 15.10. These OS distributions have reached end of life, and are therefore no longer tested. Agent, Agentless, and Live DVD support for these OS is therefore limited.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating