Chat now with support
Chat with Support

Rapid Recovery 6.3 - Release Notes

Known issues

This topic contains known issues in the following categories:


The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

Table 5: Core and Windows known issues

Issue ID Known Issue Description Workaround Functional Area

27309 93141

ESXi virtual export with automatic disk mapping using default configuration for the VM configuration location fails with unclear error. The Failure Reason is "Task 'ReconfigVM_Task' failed: Invalid configuration for device '0'."

Reduce the number of concurrent exports.

Virtual exports, ESXi


When upgrading a Core (in languages other than English) that protects machines with Agent version earler than, the Compatibility page of the Rapid Recovery Core Installer wizard incorrectly shows Agent version 7 in the message instead of Agent 6.2 or Agent 6.3 (based on the installer being used).

None available. Disregard the version number. Protected machines with supported operating systems will be upgraded to Rapid Recovery Agent version 6.3.

Installer, localization


Rollup job does not merge replicated recovery points according to the retention policy if seed drive for older recovery points was not consumed.

None available.

Rollup jobs, replication, seed drive


Trustedinstaller process called during every metadata request from Agent, consuming about 100MB of additional RAM.

Contact Quest Data Protection Support for a patch to address this issue. 



In a specific environment, when a shadow copy has a specific path, agentless backup fails with "Invalid URI: The hostname could not be parsed" error.

Contact Quest Data Protection Support for a patch to address this issue. 



After upgrade from release 5.4.3 to release 6.1 and later, all task events convert to service events, and are no longer visible on the Tasks page.

None available.



If the Quest NetVault Backup with BMR plugin is installed on the same server as the Rapid Recovery Core, then ESXi exports fail.

Copy the following DLLs from Coreservice\vddk\bin to the Coreservice folder, and then restart the Core service:

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

Virtual exports


A deploy to Azure fails if the cloud service name is specified in FQDN format.

Specify only the hostname (without periods) in the Cloud service name text box. For example, instead of specifying, enter companycloudhost.



Drive letters are not assigned on an exported machine that is identical to the original machine.

Assign drive letters manually, or contact Support for a script to run on the exported machine that solves the issue. 

Virtual exports


Add menu for switching between pages with recovery points on the top of the Recovery Points page.

None available. This item is an enhancement request.

Recovery Points, GUI


EC2 Export job fails with exception: 'Amazon.EC2.AmazonEC2Exception: The key pair '{key_name}' does not exist.' for replicated Agent from another region.

Before performing virtual export, import agent machine's key manually to the region in which the target Core machine is deployed. The key should have the same name as origin.

Virtual exports, Amazon E2C


Volume letters are not assigned after BMR for GPT partitions of ESXi Agentless VM.

Assign drive letters manually.

BMR, ESXi agentless


Exported CentOS7 isn't bootable on ESXi when it has more than 6 system volumes and root volume with the 'xfs' filesystem.

Perform VM export of 6 volumes; use restore for remaining volumes.

Virtual exports, Linux, XFS


Table 6: Documentation known issues

Issue ID Known Issue Description Workaround Functional Area


The following corrections were made to the Rapid Recovery 6.3 User Guide but not in the in-product help:

One of the introductory paragraphs in the topic "Protecting multiple machines on a VMware vCenter/ESXi virtual host" is duplicated in the in-product help.

A hypertext link in the topic "Protecting vCenter/ESXi virtual machines using agentless protection" is broken in the in-product help. Some minor formatting errors also appear.

Some formatting errors appear in the topic "Protecting vCenter/ESXi virtual machines using agentless protection" in the in-product help.

A hypertext link in the topic "Factors when choosing agent-based or agentless protection"  is broken in the in-product help. 

A clarification regarding Active Block Mapping was added to the User Guide after in-product help was published. For the ABM setting "Exclude subdirectories," the text "Lets you exclude specific folders and files" was replaced with the following text:

"Lets you exclude specific  files by specifying '<file name>' or '<folder>\<subfolder>\<file name>'.

Only the files will be excluded. The folders or subfolders that contained excluded files are included in the mount point, with no contents."

This change appears in three topics:

  • Protecting vCenter/ESXi virtual machines using agentless protection
  • Protecting Hyper-V virtual machines using host-based protection
  • Changing ABM settings

Malformed or missing hypertext links appear in step 13 of the topic "Protecting multiple machines manually" in the in-product help.

In the topic "Generating a Core report on demand," the note under step 6 should begin "In all cases."

Additionally, various formatting updates were applied to topics when necessary.

These errors have been fixed in the Rapid Recovery 6.3 User Guide and the correction will appear in the next release of in-product help.

In-product help


For agentlessly protected machines only, web help contains a link on the protected virtual machine's System Information page that shows an incorrect topic, "Viewing system information for the Core."

Please disregard this help topic. This link is expected to be removed in a future version of Rapid Recovery.

Agentless protection, In-product help
108288 In release 6.3, a link to in-product help for the new Active Block Mapping feature is present only for protected hypervisor hosts, and is not yet available for agentlessly protected virtual machines. The in-product help topic "Changing ABM settings" and its parent topic, "Understanding Active Block Mapping," are available to users when they open in-product help independently, and in the Rapid Recovery 6.3 User Guide. Agentless protection, ABM, machine-level settings, In-product help


Table 7: Linux known issues

Issue ID Known Issue Description
Functional Area


Linux Live DVD does not recognize disks on a specific environment.

Contact Quest Data Protection Supportfor a patch to address this issue.

Linux, Live DVD


There is no ability to protect a Linux machine with more than 2000 disk devices attached.

Contact Quest Data Protection Support for a patch to address this issue.


31277, 96616

Red Hat virtual machines that are hosted in ESXi are not bootable when exported to VirtualBox. This occurs only with agentless protect and either large hard drives or LVM volumes.

None available.

ESXi, agentless protection, Linux


Table 8: Obsolete known issues

The issues listed in this table are previously known issues that are obsolete. Unless otherwise indicated, these issues relate to features that are no longer supported. Thus, these issues will not be fixed, nor tracked further in Release Notes.

Issue ID Known Issue Description
Functional Area
105997 Customer requested a decrease in the number of events created during agentless backup on vCenter. This is an enhancement request, not a defect, and therefore will no longer be tracked in Release Notes. To request enhancements or new features, access the Quest Ideation Portal at Events monitoring, notifications
104825 There is no ability to create Tiering repository using the Add-on for Kaseya. Tiering recovery points is no longer supported, and the Add-On for Kaseya is discontinued. This issue will no longer be tracked. Tiering, Kaseya Add-On
104812 It is impossible to set GDPR if the user tries to install Core using the Add-on for Kaseya. After installing using the 6.2 Kaseya Add-On, set GDPR (set the "Agree to use of personal data" setting) using General Settings in the Core Console. GDPR compliance was added after the last version of the Kaseya Add-On was provided. This issue will no longer be tracked. Core settings, privacy setings, GDPR, Kaseya VSA
103412 Dashboard Transfer Job widget doesn't track jobs which are expired in the queue. If experiencing this issue, review the status using other aspects of the Core Console UI, or using PowerShell scripts. This is not actually a defect, but reflects behavior as designed by the application. This item will no longer be tracked. Core Console, dashboard widget

100061, 35031

In Rapid Recovery 6.0 and later, some non-English languages (namely French, Japanese, and Korean) use incorrect translations of the word "state" on the Backup page in the "Items Backed Up" section. The correct translation relates to the current condition.

This issue will no longer be tracked.

DL appliance, Backups page, localization


Relocate recovery points to Virtual DR fails with error 'Job fails with RDS service exception. Error code: 'ConnectionResetByPeer.'

Tiering recovery points is no longer supported.



Add-on for Kaseya displays only 10 Kaseya Agents within different tabs.

The last release for the Add-on for Kaseya was 6.2. This product is discontinued. This issue will no longer be tracked.

Kaseya Add-On

Go to the top of this topic.

Where to find Rapid Recovery system requirements

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

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.

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 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

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 6.3 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, andQuest 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 6.3 Installation and Upgrade Guide.
  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:
    1. Sign up for an account. In a web browser, access the license portal registration URL,
      The Sign Up page appears.
    2. 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.
    3. Verify your account information. Check your email and verify your account information by clicking Verify email address.
      The Add License Numbers page appears.
    4. 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:
    1. Use existing credentials. Log into the Rapid Recovery License Portal.
    2. 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.
    3. 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

Getting started with Rapid Recovery

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

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating