Chat now with support
Chat mit Support

Rapid Recovery 6.7 - Release Notes


The following is a list of enhancements implemented in Rapid Recovery6.7.

Table 1: General enhancements

Enhancement Issue ID
Support for Ubuntu 21.04 and 22.04 RR-110734, RR-111057
Ability to connect the existing Rapid Recovery Azure original repository from the Rapid Recovery Core Console RR-110916
Support for Windows 11 RR-110934
Ability to schedule backups to occur every given number of days RR-110951
Support for AlmaLinux 8 and Rocky Linux 8 RR-110958
Support for Debian 11 RR-110969
Support for Windows Server 2022 for Rapid Recovery Core and Rapid Recovery Agent RR-110978
Support for VMware Workstation 16 RR-111017
Support for NVMe Linux disks RR-111065
Added the ability to disconnect remote mounts using PowerShell RR-111074
Added the ability to select the Subnet of Virtual Network in the Azure Export Wizard RR-111077
Support for RHEL 8.6 RR-111111

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

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

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

  • Hypervisor:
    • 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 Description Issue ID
Corrected an issue where mount folders in C:\ProgramData\AppRecovery\MountPoints reached capacity and did not clean up. 111102
Corrected an issue where the AppRecoveryAPI sample Get-Event did not work. 111101
Corrected an issue where the job for retrieving data from Amazon Glacier failed with the error "The remove server returned an error: (400) Bad Request." 111079
Corrected an issue where a BMR that included a FAT 16 partition failed with the error "Error performing disk changes." 111043
Corrected an issue where, in specific scenarios, all recovery points were deleted instead of selected. 111008
Corrected an issue where cluster protection failed with the error "Object reference not set to an instance of an object." 110997
Corrected an issue where, if an ESXi virtual machine had more than 16 disks, export failed with the error "No SCSI devices available!" 110965
Corrected an issue where the user could not add a Backblaze cloud account due to incompatible validation requirements. 110961
Corrected an issue where certificates were continuously generate for a Linux agent when the machine name included a specific symbol. 110957
Corrected an issue where consuming a seed drive located in a cloud account failed with the error "Initialization of new instance of type 'Replay.Core.Implementation.Backup.Jobs.RestoreJob' has failed. ---> System.ArgumentNullException: Value cannot be null." 110929
Corrected an issue where, if the repository had the Average Bytes per Record set to 65536, the Core crashed during transfer operations. 110927
Created a patch for an issue where, on a specific environment, archive check failed with "Integrity check results: checksum errors, dedupe hash mismatches '0' have been detected." If you experience this issue, contact Quest Support. 110899
Corrected an issue where export using SAN transport mode failed. 110839
Corrected an issue where, if a volume was very large (in this case, more than 5 TB), BMR failed with a timeout error or became unresponsive. 110684

Known issues

This topic contains known issues in the following categories:


Table 3: Core and Windows known issues

Issue ID Known Issue Description Workaround Functional Area
111113 SLES 12 SP5 fails to boot after BMR    
111095 Export and BMR from Ubuntu 20.04 to VMware fails to boot.    
109771 After canceling an ESXi export task when all volumes are in the post-processing phase, an error message appears.   Virtual export
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."   Core Console UI
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.    


Trying to perform an "Open Exchange Database" job from a recovery point fails with error "Multiple concurrent writable mounts of a single volume are not supported."

Use the Local Mount Utility, or manually mount the recovery point and open the database.

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. Contact Quest Support for a patch to resolve this issue. 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 unresponsive
107784 When protecting a cluster, there is no ability to add cluster nodes to Virtual Standby No workaround at this time. Virtual export
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. Contact Quest Support for a patch to resolve this issue. 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. Contact Quest Support for a patch to resolve this issue. Appliance, Core Console UI
106545 When upgrading a Core (in languages other than English) that protects machines with Agent version earlier 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
105830 Rollup job does not merge replicated recovery points according to the retention policy if seed drive for older recovery points was not consumed. Consume the seed drive on the target core. 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
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
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
97451 Volume letters are not assigned after BMR for GPT partitions of ESXi Agentless VM. Assign drive letters manually. BMR, ESXi agentless
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

Go to the top of the Known issues topic.


Table 4: Linux known issues

Issue ID Known Issue Description Workaround Functional Area
111206 Linux volume metadata displays incorrectly.    
110865 If I/O data is generated for a volume on a Linux machine, the Linux machine may not respond during a snapshot.   Linux, protected volumes
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


Table 5: 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 Tthere 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


Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen