Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Rapid Recovery 6.3 - Release Notes

Limited support for live migration

Live migration is a Hyper-V feature of Windows Server which lets users move running VMs from one Hyper-V host to another with no visible downtime. This provides flexibility to hypervisor administrators in managing VMs.

This feature is included in Windows Server OS from Windows Server 2008 R2 and later versions. Windows Server 2016 is the first OS to support this feature without failover clustering.

Live migration is a Hyper-V feature of Windows Server which lets users move running VMs from one Hyper-V host to another. Rapid Recovery supports Hyper-V live migration when moving VMs between nodes in a cluster. Live migration between separate hosts (a Hyper-V 2016 feature) is not supported with Rapid Recovery.

If using Rapid Snap for Virtual agentless protection, a supported version of Rapid Recovery Agent must be installed on the Hyper-V host. If using agent-based protection, Rapid Recovery Agent must be installed on each node in a protected Hyper-V cluster, but is not required on the host.

Improvements in mounts for Core and LMU

Rapid Recovery Core captures snapshots from volumes on machines protected in the Core, and saves them in the designated repository as recovery points. From the Rapid Recovery Core Console (or using the Local Mount Utility), you can browse recovery points, and choose to mount one in the Core.

You can browse through the data in a mounted recovery point (also referred to as simply a "mount"). For example, you can recover individual files, or use the mount as a source for a restore action (such as restoring whole volumes). When viewing a mount, you can restore in place (to the original machine location, or to bare metal.

Historically, Rapid Recovery assigned a physical address (such as C:\mounts\backup1vol2) for each mount, from which you can access the data.

As of Rapid Recovery 6.3, when mounting a recovery point (whether from the Rapid Recovery Core Console or using the LMU), you can choose to assign an as-yet unreserved drive letter (such as f:\) to the mount instead of a physical address.

This new functionality is also supported by PowerShell and Command Line commands. An example of the usefulness of this feature is when mounting using the command line, since there is no longer a need to verify in advance which volumes are available.

NOTE: For more information on these commands, see the latest edition of the Rapid Recovery Commands and Scripting Reference Guide.

 

Deprecated features

The following is a list of features that are no longer supported starting with Rapid Recovery 6.3.

Rapid Recovery support for Exchange Server 2007 is deprecated

In April of 2017, Microsoft Exchange Server 2007 reached end of life. Microsoft no longer supports that version of Exchange Server.

Accordingly, Rapid Recovery support of Exchange Server 2007 is deprecated.

  • Exchange Server 2007 is not supported by Rapid Recovery release 6.3.
  • Customers with a current maintenance agreement using supported prior versions of Rapid Recovery (as of General Availability for release 6.3, these include releases 6.1.3 and 6.2.1) are entitled to limited support for Exchange Server. If customers encounter issues, Quest Data Protection Support   will apply their best effort to provide known work-arounds or fixes. However, no coding effort will be applied to issues discovered in Exchange Server 2007 in relation to our software.

Quest recommends migrating to newer, supported versions of Exchange if you want to continue protecting your data using Rapid Recovery.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation