Replication conflicts with agentlessly protected virtual machines on SMB shares Content differences between context-sensitive help and technical documentation

Rapid Recovery release designations Quest Support policy Rapid Recovery service levelsy New features

Virtual Machine-only licensing Support for Oracle 18c RDBMS VM configuration backup and restore on Hyper-V Support for backup and restore of Linux LVM cache volumes BMR for disk-level agentless backups on Linux Support for many disk-level volumes for Linux BMR

Enhancements

VMware Workstation 15 now supported Oracle VirtualBox 6.0 now supported VM configuration backup and restore improvements on ESXi Protection of shared VHDX disks for standalone Hyper-V Debian 10 Linux now supported

Deprecated features

Upcoming end of support for Rapid Recovery version 6.1.3 Rapid Recovery support for Microsoft Windows Server 2008 R2 SP1 is deprecated VMware Workstation support changes vCenter/ESXi support changes Hypervisor support changes End of support for Linux Agent 6.3 for various distributions

Resolved issues Known issues Where to find Rapid Recovery system requirements Product licensing Getting started with Rapid Recovery

Rapid Recovery Core and Agent compatibility Upgrade and installation instructions More resources Obtaining Rapid Recovery software

Globalization

Known issues

Rapid Recovery 6.4 Release Notes > Known issues

This topic contains known issues in the following categories:

Core and Windows known issues
Documentation known issues
Linux known issues
Local Mount Utility issues

Table 10: 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
109790	This issue applies only to agentlessly protected VMs successfully using a non-phone-home (NPH) front-end capacity license. If the VM is removed from protection and re-protected using the same license, the license status appears as "Trial" instead of "Active."	Completely delete the registry (licenseinfo) hive and apply the NPH key again.	Licensing, agentless protection
109682	When attempting to archive to an existing Azure Government cloud account, error 'Initialization of new instance of type...' appears and archive is unsuccessful.	No workaround at this time.	Archive, cloud, Azure Government
109575	On a specific environment, Core Console UI does not load, with the error "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."	No workaround at this time.	Core Console UI
109188	When setting the protection schedule for an interval of 24:00 (24 hours exactly) and saving as a template, the Core does not apply this template properly. No transfers occur when based on a saved template using this interval. This affects Core releases 6.3.0 and 6.4.0.	Until this defect is addressed, do not use an interval of 24:00. For example, you can use 23:59.	Protection schedules
108299	Replicated data is incorrectly calculated as protected data when a non-phone-home capacity license is applied on the target Core. "Used by this Core" statistic on the target Core should read "0" or unlimited, since replication data transfer is not counted towards limitations for licensing.	1. Increase license pool size (purchasing additional licenses if necessary). 2. Use another type of license (for example, a standard phone home capacity license).	Replication, licensing
107978	When deploying the Rapid Recovery Agent from the Core server, the Microsoft Store Install Service disappears from the list of services visible on the protected machine.	No workaround at this time.	Agent installation
107947	On a specific environment, virtual export fails to start, with error: 'Cannot connect to a remote machine '{0}' ' sometimes on unstable environment.	No workaround at this time.	Virtual export
107855	On a specific Dell PowerEdge Windows server environment, protected machine hangs briefly (up to 1 minute) every hour when the Rapid Recovery Agent service starts, seemingly due to a 20-30 BCD query.	Perform BCD queries one at a time, sequentially, to avoid this issue. For diagnostic steps, see Quest Knowledge Base article 259558.	Agent hang
107755	When creating an archive using the Archive Wizard, if you return from the Options wizard page back to the Machines page, there is no ability to edit the date range.	Close the wizard without saving the archive, and run through the wizard again.	Archiving, usability
107346	When restoring or performing virtual export of a volume with 512-bytes per sector to a volume with 4096-bytes per sector, a warning message does not appear.	For workaround, please see Quest Knowledge Base article 144232.	Virtual export, notifications
107304	On a specific appliance environment, the error message "GetResponse Timed Out" appears when trying to open the Appliance page.	No workaround at this time.	Appliance, Core Console UI
107182	Encryption key does not apply to cluster nodes during cluster protection.	Select encryption key for nodes manually in Settings.	Encryption
106938	On a specific appliance environment, the "Storage Hardware" information is not available on the Appliance Health page.	No workaround at this time.	Appliance, Core Console UI
106545	When upgrading a Core (in languages other than English) that protects machines with Agent version earlier than 5.4.3.106, 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
105830	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
105445	Trustedinstaller process called during every metadata request from Agent, consuming about 100MB of additional RAM.	Contact for a patch to address this issue.	Metadata
104393	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 for a patch to address this issue.	Agentless
103477	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
102756	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 companycloudhost.cloudapp.net, enter companycloudhost.	Azure
102390	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
101736	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
97451	Volume letters are not assigned after BMR for GPT partitions of ESXi Agentless VM.	Assign drive letters manually.	BMR, ESXi agentless

Go to the top of the Known issues topic.

Table 11: Documentation known issues

Issue ID	Known Issue Description	Workaround	Functional Area
109897	The following corrections were made to the Rapid Recovery 6.4 User Guide but not in the in-product help: References to former topic name "Managing licenses" in the Rapid Recovery 6.4 Installation and Upgrade Guidehave been updated to "Understanding Rapid Recovery licenses." The topics in in-product help that use the older topic name are listed below: Factors when choosing agent-based or agentless protection (first paragraph of subtopic "release 6.4 license consumption concepts") Rapid Recovery Core settings (the table row that reads "Licensing") How Rapid Recovery ses personal information (first sentence, and later in a bulleted list of resources) Obtaining and using non-phone-home licenses (fourth paragraph) In the Core settings chapter of the User Guide, some updates were made to topics related to the DVM deduplication cache that do not appear in the 6.4 version of in-product help. In topic "Understanding deduplication cache and storage locations," formatting changes only appear. Specifically, the alphabetic case has been changed from title case to sentence case in the table showing default storage location settings. When those steps refer to UI elements, they now appear in bold, following UI conventions for click steps. In topic "Configuring DVM deduplication cache settings," in the table under step 5, the same formatting changes were applied to the same settings. Additionally, in the row showing Deduplication cache size, the description has been changed to correctly show the current text box label (also set in boldface), and to include a note. The updated text reads: "If you want to change the deduplication cache size for DVM repositories, then in the Deduplication cache size (GB) text box, enter a new amount in gigabytes. Note: If you decrease the size of the deduplication cache, the existing contents of the cache are flushed, and the cache is recreated." In help, the Restoring data chapter topic "VMware VM configuration backup and restore" indicates that release 6.4 introduces the ability to back up VMware VM configurations. This capability was actually introduced to release 6.3; in release 6.4, you can also back up Hyper-V VM configurations, as described in Rapid Recovery 6.4 Release Notes topic "VM configuration backup and restore on Hyper-V." In the PDF/HTML version of the 6.4.0 User Guide, this topic is updated, and is now called "VM configuration backup and restore for VMware and Hyper-V".	Please refer to the PDF or HTML-based User Guide on the Quest technical documentation website to see the latest content in the topics specified. When reviewing these topics within in-product help, disregard the minor discrepancies, and take heed of the updated information regarding deduplication cache which is flushed and re-created if the deduplication cache size is reduced.	In-product help, technical product documentation
109793	Within in-product help, on the Settings page of the Core Console, if you click the Help icon for the License Details Core setting, a generic error message appears.	To read about licensing in release 6.4, see the Rapid Recovery 6.4 Installation and Upgrade Guide topic "Managing Rapid Recovery licenses." In previous editions of in-product help, this Core setting included a link to information about licensing. That topic no longer appears in the User Guide or in-product help. The Help icon will not appear in future editions of in-product help.	In-product help, Rapid Recovery Core Console, Core Settings, License Details
N/A	The information for the following third-party components has been added or updated in Rapid Recovery Core release 6.4 after in-product help was produced. The following notifications comprise supplemental updates to in-product help for third-party contributions. Their purpose is to provide proper attribution and meet legal and copyright requirements related to the use of the listed components.	Consult these notifications in Release Notes for the latest updates to legal and copyright requirements.	In-product help, Third-party components, copyrights, legal requirements
	Component p7zip 16.0.2 is not included in the list of third-party components available from in-product help for release 6.4.	Component p7zip 16.0.2 uses the Mozilla Public License (MPL) 1.1. A copy of the MPL can be found as a linked license in Rapid Recovery's Third-Party Components link within in-product help.
	Component NBD is a Linux component which, when compiled into the kernel, lets Linux use remote servers as one of its network block devices. This software component is not used by Rapid Recovery Core but may be required by protected Linux agents. Quest is required to indicate where a copy of the source code for this GPL component is located. Component NBD is incorrectly noted within 6.4.0 in-product help as being available on the Linux DVD.	This component is not actually used by Rapid Recovery, but may be used by protected Linux machines. NBD is not available on the Linux DVD. Red Hat Enterprise Linux, CentOS and Oracle Linux installation packages download NBD source code from a publicly-accessible web location. Direct links differ based on distribution used; see the relevant Rapid Recovery Agent installation package. For assistance, please contact Quest Data Protection Support. Component NBD (various versions) uses the GNU General Public License 2.0, which can be found in Rapid Recovery's Third-Party Components link within in-product help. The copyright attributions there are accurate and complete.

Go to the top of the Known issues topic.

Table 12: Linux known issues

Issue ID	Known Issue Description	Workaround	Functional Area
109902	When a newly created block device is added to an already-protected Linux machine, the Linux driver attaches to the block device without it being explicitly added to protection.	Remove new volume from protection if you do not want to protect it in the Core.	Linux, Agent, protected volumes
109691	When a 6.4 Linux machine with multiple volumes mounted is protected in a 6.4 Core, if one or more volumes is not included in the protection schedule, the volume or device remains attached to the Rapid Recovery driver until the data is refreshed for that machine from the Core.	Refresh metadata for the affected machine from the Core Console.	Mounted devices, protection, Core Console
107984	When installing Rapid Recovery Agent on a Linux machine, minor misspellings appear on the command line for firewall settings.	No workaround at this time. The text "Configured manualy. May be reconfigured…" is expected to be changed to "Configured manually. This may be reconfigured...".	Linux, Agent installation

Go to the top of the Known issues topic.

Table 13: Local Mount Utility known issues

Issue ID	Known Issue Description	Workaround	Functional Area
108540	Toast pop-up notifications appear outside of the Local Mount Utility application window/frame.	No workaround at this time.	Notification
107756	In 6.2x, 6.3x versions of the LMU, there is no ability to set Core Connection Timeout using the LMU UI.	You can set the Core Connection Timeout using the Windows registry using key CoreConnectionTimeout. For more information, see Quest Knowledge Base article 210006.	LMU, Connection timeout

Go to the top of the Known issues topic.

Where to find Rapid Recovery system requirements

Rapid Recovery 6.4 Release Notes > 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 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.

Product licensing

Rapid Recovery 6.4 Release Notes > 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 6.4 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.

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 6.4 Installation and Upgrade Guide.
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, https://rapidrecovery.licenseportal.com/User/Register.
  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.
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.
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.
Review updated license information. Review license type and license pool information displayed on the Licensing page.