Quest® Rapid Recovery 6.

Release Notes
April 2021
These release notes provide information about the Rapid Recovery release, build 6.6.
Topics include:

About this release

Quest Support policy
Enhancements
Deprecated features
Resolved issues
Known issues
Where to find Rapid Recovery system requirements
Product licensing
Getting started with Rapid Recovery
Globalization
About us

About this release

Rapid Recovery software delivers fast backups with verified recovery for your VMs and physical servers, on-
premises or remote. Rapid Recovery is software built for IT professionals who need a powerful, affordable, and
easy-to-use backup, replication, and recovery solution that provides protection for servers and business-critical
applications like Microsoft SQL Server, Oracle Database, Microsoft Exchange, and Microsoft SharePoint. Using
Rapid Recovery, you can continuously back up and protect all your critical data and applications from a single
web-based management console.
Rapid Recovery 6.6 is a minor release, with enhanced features and functionality. See New features and
Enhancements for details.
NOTE: For more information about how major, minor, and maintenance releases are differentiated, see
Rapid Recovery release designations.

Rapid Recovery 6.6

Release Notes 1
Some features, previously integrated software tools, or platforms are no longer supported. For more information
on these items, see Deprecated features.
As a minor release, defect fixes and known issues listed in this document are not cumulative.
For information relevant for any other release, please see the edition of release notes specific to that release on
the Quest technical documentation website.
NOTE: In this release of Rapid Recovery, Quest removed the Beta label from the Azure repository
feature. Quest discourages using an Azure repository for storing original recovery points and
recommends using it only for storing replicated recovery points. For more information, see "Replication
with Rapid Recovery" in the Rapid Recovery 6.6 User Guide.

NOTE: Currently, the Rapid Recovery Core Console lets you connect to an Azure repository only from
the source Core that replicates to it, and does not support the Connect to Existing feature. For more
information, see https://support.quest.com/kb/332647.

Quest Support policy

Full support: For customers with a current maintenance contract, Quest Data Protection Support provides call-in
or email support for the current major and minor release, when patched to the latest maintenance release. That
release is known as N. Quest also fully supports N - 1. For Rapid Recovery, Quest also provides limited support
for N - 2. For more information, see "Rapid Recovery support levels" in the Rapid Recovery Release Notes.
Limited support: Quest Data Protection Support may attempt to answer questions on other versions of our
products, provided resources are available. However, if you are using an unsupported or discontinued version,
no new patches or code fixes will be created for those versions. In such cases, we encourage you to upgrade to
a currently supported version of the product.
Product support life cycle: Quest describes its product life cycle (PLC) support policy on its Support website
(visit https://support.quest.com/rapid-recovery/, click Product Life Cycle & Policies, and then expand the topic
Product Support Life Cycle Policy). To understand full support, limited support, and discontinued support,
consult the detailed policy on the website referenced above.

Enhancements
The following is a list of enhancements implemented in Rapid Recovery6.6.
Table 1: General enhancements

Enhancement Issue ID

Improved the behavior of the repository when it runs out of space. RR-67129
Allowed ReFS protection under compatible versions of Windows 2019. RR-108441
Added support for Generation 2 virtual exports and standbys for Microsoft Azure Cloud. RR-110078
Added the ability to identify a machine as running Nutanix AHV and label it as a virtual RR-110546
machine.
Removed Beta label from Azure storage feature. RR-110562
Added support for WinPE 2004 when building a BootCD. RR-110572
Added support for Ubuntu 20.10. RR-110652

Rapid Recovery 6.6

Release Notes 2
 Enhancement Issue ID

Added support for CentOS 7.9. RR-110653

Deprecated features
The following is a list of operating systems and applications that have limited support due to end-of-life status as
of Rapid Recovery 6.6:

l Operating systems:
l CentOS Linux 6.4-6.10
l Oracle Linux 6.4-6.10
l Red Hat Enterprise Linux (RHEL) 6.4-6.10
l SUSE Linux Enterprise Server 11 SP4 and 12 SP3
l Ubuntu Linux 16.04 LTS
l Hypervisors:
l Hyper-V on Windows Server 2012 and 2012 R2 (for export)
l Hyper-V on Windows 10 x64 (for Agentless protection)
l Oracle Virtual Box 5.2
l Platforms:
l Oracle RDBMS 18c and 12c
l SharePoint Server 2016
l Exchange Server 2010 x64

The following applications are no longer support by Rapid Recovery as of release 6.6:

l Hypervisor:
l VMware Workstation 14.x

Resolved issues
The following table includes a list of issues addressed in this release.
Table 2: Issues resolved in this release

Issue
ID Resolved Issue Description

110686 Rapid Recovery mono failed on the stage of checking system files on CentOS 6 operating systems
with a specific configuration.
110676 A Hyper-V server would crash with a BSOD 0x50 while transferring an agentless guest VM with a

Rapid Recovery 6.6

Release Notes 3
 Issue
ID Resolved Issue Description

volume size about 17TB.

110648 There was no validation for incorrect values or over-the-limit values for Azure repository settings
and Azure repository creation wizard.
110646 BMR from Azure cloud for a regular storage account could not be performed due to the error
"Loading failed: There is no connection with cloud accounts" in the restore wizard.
110595 Recovery points did not display on the Recovery Points tab for increased LVM volumes after
specific steps.
110568 Agentless transfer failed for VMs located on a datastore with "+" in the name.
110567 There was no ability to use a custom email address for notifications.
110523 Exchange log truncation was not working for ESXi agentless VMs if one database is dismounted

110503 Live Restore did not occur simultaneously for all volumes and could not access the files during the
restore.
110479 Newly created virtual machines did not automatically show up in the Core GUI Virtual Machines list
of ESXi host.
110473 Exchange log truncation was not working for HyperV agentless VMs
109828 When Core services restarted, a "Virtual environment component 'Hypervisor Storage' changed
status to 'Warning" alert was displayed.
108764 When performing a virtual export or a virtual standby and you chose 'Specific' network adapters, the
virtual standby was created with an additional e1000 NIC on top of the one you specified.

Table 3: Documentation resolved issues

Issue Functional
ID Resolved Issue Description Area

109897 Documentation changes made in the 6.4 User Guide did not appear in the 6.4 in- In-product
product help. The changes appear in subsequent releases. help

Table 4: Linux resolved issues

Issue Functional
ID Resolved Issue Description Area

110075 Linux server unexpectedly rebooted after resizing a specific volume and running a Linux
backup of that volume. protection

Table 5: Local Mount Utility resolved issues

Issue Functional
ID Resolved Issue Description Area

110364 There was no ability to open Exchange databases for ESXi agentless VMs due to Agentless
error database does not exist.

Rapid Recovery 6.6

Release Notes 4
Known issues
This topic contains known issues in the following categories:

l Core and Windows known issues

l Documentation known issues
l Linux known issues
l Local Mount Utility issues

Table 6: Core and Windows known issues

Issue
ID Known Issue Description Workaround Functional Area

27309 ESXi virtual export with automatic disk Reduce the number Virtual exports,
93141 mapping using default configuration for of concurrent exports. ESXi
the VM configuration location fails with
unclear error. The Failure Reason is
"Task 'ReconfigVM_Task' failed: Invalid
configuration for device '0'."
110899 On a specific environment, archive check Archiving
failed with "Integrity check
results: checksum errors, dedupe hash
mismatches '0' have been detected."
110887 In the Archive Wizard, the Folder Name
field for cloud location is empty by
default.
110864 While attempting to restore a large BMR
volumne, BMR fails with timeout error or
is unresponsive indefinitely.
110583 In one specific case, metadata recovery
points appears appear inconsistent.
109771 After canceling an ESXi export task Virtual export
when all volumes are in the post-
processing phase, an error message
appears.
109575 On a specific environment, Core No workaround at Core Console UI
Console UI does not load, with the error this time.
"Attempted to read or write protected
memory. This is often an indication that
other memory is corrupt."
109236 Transfer job for VM with SharedVHDX on
SOFS appears to fail with errors
"Session with the id has not been found:
fileTransmitSessionId" and "The process
cannot access the file because it is being
used by another process: " but recovery
points actually are created.

Rapid Recovery 6.6

Release Notes 5
Issue
ID Known Issue Description Workaround Functional Area

108972 Trying to perform an "Open Exchange Use the Local Mount

Database" job from a recovery point fails Utility, or manually
with error "Multiple concurrent writable mount the recovery
mounts of a single volume are not point and open the
supported." database.

107978 When deploying the Rapid Recovery No workaround at Agent installation

Agent from the Core server, the Microsoft this time.
Store Install Service disappears from the
list of services visible on the protected
machine.
107947 On a specific environment, virtual export Contact Quest Virtual export
fails to start, with error: 'Cannot connect Support for a patch to
to a remote machine '{0}' ' sometimes on resolve this issue.
unstable environment.
107855 On a specific Dell PowerEdge Windows Perform BCD queries Agent
server environment, protected machine one at a time, unresponsive
hangs briefly (up to 1 minute) every hour sequentially, to avoid
when the Rapid Recovery Agent service this issue. For
starts, seemingly due to a 20-30 BCD diagnostic steps, see
query. Quest Knowledge
Base article 259558.

107784 When protecting a cluster, there is no No workaround at Virtual export

ability to add cluster nodes to Virtual this time.
Standby
107755 When creating an archive using the Close the wizard Archiving, usability
Archive Wizard, if you return from the without saving the
Options wizard page back to the archive, and run
Machines page, there is no ability to edit through the wizard
the date range. again.
107346 When restoring or performing virtual For workaround, Virtual export,
export of a volume with 512-bytes per please see Quest notifications
sector to a volume with 4096-bytes per Knowledge Base
sector, a warning message does not article 144232.
appear.
107304 On a specific appliance environment, the Contact Quest Appliance, Core
error message "GetResponse Timed Support for a patch to Console UI
Out" appears when trying to open the resolve this issue.
Appliance page.

107182 Encryption key does not apply to cluster Select encryption key Encryption
nodes during cluster protection. for nodes manually in
Settings.
106938 On a specific appliance environment, the Contact Quest Appliance, Core
"Storage Hardware" information is not Support for a patch to Console UI
available on the Appliance Health page. resolve this issue.
106545 When upgrading a Core (in languages None available. Installer,
other than English) that protects Disregard the version localization

Rapid Recovery 6.6

Release Notes 6
 Issue
ID Known Issue Description Workaround Functional Area

machines with Agent version earlier than number. Protected

5.4.3.106, the Compatibility page of the machines with
Rapid Recovery Core Installer wizard supported operating
incorrectly shows Agent version 7 in the systems will be
message instead of Agent 6.2 or Agent upgraded to Rapid
6.3 (based on the installer being used). Recovery Agent
version 6.3.
105830 Rollup job does not merge replicated Consume the seed Rollup jobs,
recovery points according to the drive on the target replication, seed
retention policy if seed drive for older core. drive
recovery points was not consumed.
105445 Trustedinstaller process called during Contact for a patch to Metadata
every metadata request from Agent, address this issue.
consuming about 100MB of additional
RAM.
103477 If the Quest NetVault Backup with BMR Copy the following Virtual exports
plugin is installed on the same server as DLLs from
the Rapid Recovery Core, then ESXi Coreservice\vddk\bin
exports fail. to the Coreservice
folder, and then
restart the Core
service:

l glib-2.0
l gobject-2.0
l gvmomi
l iconv
l intl
l libcurl
l libxml2
l vixDiskLibVim

102390 Drive letters are not assigned on an Assign drive letters Virtual exports
exported machine that is identical to the manually, or contact
original machine. Support for a script to
run on the exported
machine that solves
the issue.
97451 Volume letters are not assigned after Assign drive letters BMR, ESXi
BMR for GPT partitions of ESXi manually. agentless
Agentless VM.

Go to the top of the Known issues topic.

Rapid Recovery 6.6

Release Notes 7
Table 7: Linux known issues

Issue Functional
ID Known Issue Description Workaround Area

110865 If I/O data is generated for a volume Linux,

on a Linux machine, the Linux protected
machine may not respond during a volumes
snapshot.
107984 When installing Rapid Recovery No workaround at this time. The text Linux,
Agent on a Linux machine, minor "Configured manualy. May be reconfigured…" Agent
misspellings appear on the is expected to be changed to "Configured installation
command line for firewall settings. manually. This may be reconfigured...".

Table 8: Local Mount Utility known issues

Issue Functional
ID Known Issue Description Workaround Area

108540 Toast pop-up notifications No workaround at this time. Notification

appear outside of the Local
Mount Utility application
window/frame.
107756 Tthere is no ability to set You can set the Core Connection Timeout using the LMU,
Core Connection Timeout Windows registry using key CoreConnectionTimeout. Connection
using the LMU UI. For more information, see Quest Knowledge Base timeout
article 210006.

Where to find Rapid Recovery system

requirements
For every software release, Quest reviews and updates the system requirements for Rapid Recovery software
and related components. This information is exclusively available in the release-specific Rapid Recovery
System Requirements Guide. Use that document as your single authoritative source for system requirements for
each release.
You can find system requirements and all other documentation at the technical documentation website at
https://support.quest.com/rapid-recovery/technical-documents/.
NOTE: The default view of the technical documentation website shows documentation for the most
recent generally available version of the Rapid Recovery software. Using the filters at the top of the page,
you can view documentation for a different software release, or filter the view by document type.

Rapid Recovery 6.6

Release Notes 8
Product licensing
Before you use and manage any version of Rapid Recovery, AppAssure, or DL series backup appliance, you
must first obtain a software license. To purchase a license for the first time, contact the Quest Data Protection
Sales team by completing the web form at https://www.quest.com/register/95291/. A sales representative will
contact you and arrange for the license purchase.
If you need to renew or purchase additional licenses, please contact the Quest Support Renewals team by
completing the web form at https://support.quest.com/contact-us/renewals.
After each license purchase, you must activate the license on the Rapid Recovery License Portal. From this
portal, you can then download your Rapid Recovery license files.
When you initially install Rapid Recovery Core, you are prompted to upload these license files the first time you
open the Rapid Recovery Core Console.
Some users start with a trial license, which has limited capabilities. Once a trial period expires, the Rapid
Recovery Core stops taking snapshots. For uninterrupted backups, upgrade to a long-term subscription or
perpetual license before the trial period expires. If you purchase a license after backups are interrupted,
performing this procedure resumes your backup schedule.
When using a software license in standard phone-home mode, the Rapid Recovery Core Console frequently
contacts the Rapid Recovery License Portal server to remain current with any changes made in the license
portal. This communication is attempted once every hour. If the Core cannot reach the license portal after a
grace period, the Core stops taking snapshots for non-trial licenses. The grace period (10 days by default) is
configurable (from 1 to 15 days) in the license group settings on the license portal.
If a Core does not contact the license portal for 20 days after the grace period, it is removed from the license
pool automatically. If the Core subsequently connects to the license portal, the Core is automatically restored on
the license portal.
Use of phone-home licenses requires Rapid Recovery users to accept a limited use of personal information, as
described in the privacy policy shown when you install Core software. For more information, see the topic
"General Data Protection Regulation compliance" in the Rapid Recovery User Guide.
NOTE: When registering or logging into the license portal, use the email address that is on file with your
Quest Sales representative. If upgrading from a trial version, use the email address associated with the
trial version. If you need to use a different email address, contact your Sales representative for
assistance.
Complete the following steps to license your Rapid Recovery software.

1. Open your registration email. When you first purchase a license from Quest, you receive an email from
the Quest licensing system. The email includes your license entitlements, expiration date (if relevant),
registered email address, and Quest license number. The license number is typically 9 digits, in format
123-456-789. Other formats are supported, as described in the topic "Understanding Rapid Recovery
licenses" in the Rapid Recovery Installation and Upgrade Guide.

Rapid Recovery 6.6

Release Notes 9
 2. New users: Register for the Rapid Recovery License Portal. If you have not previously created an
account on the Rapid Recovery License Portal, then do the following:
a. Sign up for an account. In a web browser, access the license portal registration URL,
https://rapidrecovery.licenseportal.com/User/Register.
The Sign Up page appears.
b. Complete the form. Enter the information requested, review and accept the privacy policy and
terms of use, and click Sign Up.
The Confirm Email page appears.
c. Verify your account information. Check your email and verify your account information by
clicking Verify email address.
The Add License Numbers page appears.
d. Proceed to step 4.
3. Existing users: Log into the Rapid Recovery License Portal. If you previously registered a license
portal account to use with AppAssure or Rapid Recovery, then do the following:
a. Use existing credentials. Log into the Rapid Recovery License Portal.
b. Open the License Numbers dialog box. On the Licensing page, underneath your license pool
information, click the License Numbers link.
The License Numbers dialog box appears.
c. Proceed to step 4.
4. Enter your license numbers. For each Quest license number included in your welcome email, click in
the License Number text box and enter or paste your license number. Then click + Add License
Numbers. When satisfied, click Close.
The License Number dialog box closes.
5. Review updated license information. Review license type and license pool information displayed on
the Licensing page.

Getting started with Rapid Recovery

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

Rapid Recovery Core and Agent compatibility

Upgrade and installation instructions
More resources
Obtaining Rapid Recovery software

Rapid Recovery Core and Agent compatibility

The following table provides a visual guide of the compatibility between supported versions of Rapid Recovery
Core and Rapid Recovery Agent.

Rapid Recovery 6.6

Release Notes 10
Table 9: Compatibility between supported Core and Agent versions

Version 6.4 Core 6.5 Core 6.6 Core

6.4 Agent Fully compatible Fully compatible Fully compatible

6.5 Agent Not compatible Fully compatible Fully compatible

6.6 Agent Not compatible Not compatible Fully compatible

Upgrade and installation instructions

Quest recommends users carefully read and understand the Rapid Recovery Installation and Upgrade Guide
before installing or upgrading. See the section "Installing Rapid Recovery" for a step-by-step general installation
approach. The approach includes requirements for a software license and for an account on the Rapid
Recovery License Portal; adherence to the system requirements; installing a Core; creating a repository; and
protecting machines with the Agent software or agentlessly. It also suggests use of the QorePortal.
All existing users should read the section "Upgrading to Rapid Recovery." This content describes upgrading
factors, provides an overview of upgrading, and includes procedures upgrading Core, and upgrading Agent on
Windows and Linux machines.
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. System requirements are found exclusively in the Rapid Recovery System
Requirements Guide.
When planning an implementation of Rapid Recovery, for guidance with sizing your hardware, software,
memory, storage, and network requirements, see Quest Knowledge Base article 185962, Sizing Rapid
Recovery Deployments."
If upgrading from a currently supported major and minor version of Rapid Recovery Core (6.1x or 6.2x), then run
the latest Core installer software on your Core server. If upgrading from a version of AppAssure or Rapid
Recovery Core that is not currently supported, use a two-step upgrade process. First, upgrade using a
supported Core installer such as 6.2.1; then run the latest Core installer software.
If using replication, always upgrade the target Core before the source Core.
To protect machines running supported operating systems with the latest Rapid Recovery Agent features,
upgrade or install Rapid Recovery Agent on each.
CAUTION: Ensure that you check system requirements for compatibility before upgrading. For
protected machines with operating systems that are no longer supported, you can continue to run
older supported versions of Agent. In some cases, you can protect those machines agentlessly.
You can use the same installer executable program (standard, or web installer) to perform a clean installation or
to upgrade an existing version of Rapid Recovery Core, Rapid Recovery Agent, or the Local Mount Utility. If
upgrading from versions earlier than release 5.4.3, you must first upgrade to 5.4.3 and then run a more recent
installer on the same machine. 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 topic "Installing or
upgrading Rapid Recovery Agent on a Linux machine" in the Rapid Recovery Installation and Upgrade Guide.
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 Rapid Recovery User Guide.
For information on downloading Rapid Recovery software, see Obtaining Rapid Recovery software.

Rapid Recovery 6.6

Release Notes 11
License requirements
New Core users must purchase a long-term subscription or perpetual license to use Rapid Recovery.
Some Rapid Recovery Core users start with a trial license, which uses a temporary license key for the duration
of the trial. After the trial period expires, you can continue to restore from existing backups, but cannot perform
new backups or replication until you purchase a long-term subscription or perpetual license. You must then
activate the license on the Rapid Recovery License Portal, download Rapid Recovery license files, and
associate them with your Core.
For more information about licensing, see the following resources:

l For information about activating your new license and obtaining Rapid Recovery license files for your
Core, see Product licensing in these release notes.
l For information about managing licenses from the Rapid Recovery Core, including uploading license
files to associate them with the Core, see the topic "Managing Rapid Recovery licenses" in the Rapid
Recovery Installation and Upgrade Guide.
l For information about managing license subscriptions and license groups on the license portal, see the
latest edition of the Rapid Recovery License Portal User Guide.

More resources
Additional information is available from the following:

l Technical documentation
l Videos and tutorials
l Knowledge base
l Technical support forum
l Training and certification
l Rapid Recovery License Portal
l Quest Data Protection Portal

l In-product help is available from the Rapid Recovery Core Console by clicking .

Obtaining Rapid Recovery software

You can obtain Rapid Recovery software using the following methods:

l Download from the QorePortal. If you have an active maintenance agreement, you can log into the
QorePortal at https://qoreportal.quest.com. From the top menu, click Settings, and from the left
navigation menu, select Downloads. Here you will have access to installers for various Rapid Recovery
components, including Core, Agent, LMU, DR, and more.
l Download from the License Portal. If you have already registered Rapid Recovery in the Rapid
Recovery License Portal, you can log into that portal at https://licenseportal.com. From the left navigation
menu, click Downloads, and download the appropriate software.

Rapid Recovery 6.6

Release Notes 12
 l Download trial software from the Support website. To download trial software, navigate to the Rapid
Recovery Rapid Recovery website at https://support.quest.com/rapid-recovery and from the left
navigation menu, click Software Downloads. Here you can access trial versions of Rapid Recovery
Core, Agent (for Windows or Linux), tools and utilities, and more. Trial versions function for 14 days, after
which time you must purchase and register a subscription or perpetual license to continue using Rapid
Recovery. To purchase a license, fill out the web form at https://support.quest.com/contact-us/licensing
and select Obtain a license for my product.

You can also obtain the Rapid Recovery Agent software from within the Rapid Recovery Core Console using
the following methods:

l Protecting machines with the wizard. If the Rapid Recovery Core is installed, you can deploy the Agent
software to the machine you want to protect from the Protect Machine Wizard or the Protect Multiple
Machines Wizard. Using these wizards, you can also choose to add machines to protection using an
older installed version of Agent. For more information about these wizards, see the topics "Protecting a
Machine" and "About protecting multiple machines" in the Rapid Recovery User Guide.
l Use the Deploy Agent Software feature. If the Rapid Recovery Core is installed, you can deploy the
Agent software from the Core to one or multiple machines. This is useful for upgrading Agent to one or
more machines simultaneously. From the Protect drop-down menu on the Rapid Recovery Core
Console, select Deploy Agent Software and complete details in the resulting wizard. For more
information about using this feature, see the topic "Deploying Agent to multiple machines simultaneously
from the Core Console" in the Rapid Recovery User Guide.
l Download Agent or LMU from the Rapid Recovery Core Console. From a network-accessible
Windows machine you want to protect, you can log into the Rapid Recovery Core Console and
download the Agent software. From the icon bar, click More and then select Downloads. From the
Downloads page, you can download the web installer to install Agent or the Local Mount Utility on
Windows machines.

Globalization
This section contains information about installing and operating this product in non-English configurations, such
as those needed by customers outside of North America. This section does not replace the materials about
supported platforms and configurations found in the Rapid Recovery System Requirements Guide.
This release is Unicode-enabled and supports any character set. In this release, all product components should
be configured to use the same or compatible character encodings and should be installed to use the same
locale and regional options. This release is targeted to support operations in the following regions: North
America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports
bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).
Multi-language support is available for this product. The user interface for this release is localized to
the following languages: Chinese (Simplified), French, German, Japanese, Korean, (Brazilian)
Portuguese, Spanish.
This release has the following known capabilities or limitations:

l QorePortal is in English only.

l Reports are in English only.

Rapid Recovery 6.6

Release Notes 13
 l All currently supported versions of Rapid Recovery Core require the . Microsoft .NET Framework version
4.6.2. Earlier releases of Rapid Recovery used different versions of the .NET Framework. There is no
downgrade option available. If you upgrade versions of Rapid Recovery to a release using a more
recent version of the .NET Framework, and then subsequently decide to return to a prior version, you
must perform a new installation of the appropriate Core and Agent software.
l Logs and KB articles for Rapid Recovery are in English only.
l Technical product documentation for this release is in English only.

About us
Quest provides software solutions for the rapidly-changing world of enterprise IT. We help simplify the
challenges caused by data explosion, cloud expansion, hybrid datacenters, security threats, and regulatory
requirements. We are a global provider to 130,000 companies across 100 countries, including 95% of the
Fortune 500 and 90% of the Global 1000. Since 1987, we have built a portfolio of solutions that now includes
database management, data protection, identity and access management, Microsoft platform management, and
unified endpoint management. With Quest, organizations spend less time on IT administration and more time on
business innovation. For more information, visit www.quest.com.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have
trial versions. You can access the Quest Support Portal at https://support.quest.com.
The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours
a day, 365 days a year. The Support Portal enables you to:

l Submit and manage a Service Request

l View Knowledge Base articles
l Sign up for product notifications
l Download software and technical documentation
l View how-to-videos
l Engage in community discussions
l Chat with support engineers online
l View services to assist you with your product

Rapid Recovery 6.6

Release Notes 14
© 2021 Quest Software Inc. ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a
software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the
applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written
permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel
or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products.
EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS
PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR
STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL
QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL
DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR
LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST
SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or
warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to
specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the
information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept
4 Polaris Way
Aliso Viejo, CA 92656

Refer to our Web site (https://www.quest.com) for regional and international office information.

Patents
Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most current
information about applicable patents for this product, please visit our website at https://www.quest.com/legal.

Trademarks
Quest and the Quest logo are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit
https://www.quest.com/legal/trademark-information.aspx. All other trademarks and registered trademarks are property of their
respective owners.
Legend
CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions
are not followed.

NOTE: An information icon indicates supporting information.

Rapid Recovery Release Notes

Updated - April 2021
Version - 6.6

Rapid Recovery 6.6

Release Notes 15