Chat now with support
Chat with Support

Rapid Recovery 6.6 - Release Notes

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:

  • 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 Server 2012 and 2012 R2 (for export)
    • 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.6:

  • 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 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 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 ID Resolved Issue Description Functional Area
109897 Documentation changes made in the 6.4 User Guide did not appear in the 6.4 in-product help. The changes appear in subsequent releases. In-product help

Table 4: Linux resolved issues

Issue ID Resolved Issue Description Functional Area
110075 Linux server unexpectedly rebooted after resizing a specific volume and running a backup of that volume. Linux protection

Table 5: Local Mount Utility resolved issues

Issue ID Resolved Issue Description Functional Area
110364 There was no ability to open Exchange databases for ESXi agentless VMs due to error database does not exist. Agentless

Known issues

This topic contains known issues in the following categories:

 

Table 6: 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
110899 On a specific environment, archive check failed with "Integrity check results: checksum errors, dedupe hash mismatches '0' have been detected."   Archiving
110887 In the Archive Wizard, the Folder Name field for cloud location is empty by default.    
110864 While attempting to restore a large volumne, BMR fails with timeout error or is unresponsive indefinitely.   BMR
110583 In one specific case, metadata recovery points appears appear inconsistent.    
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." No workaround at this time. 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.    

108972

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

Go to the top of the Known issues topic.

 

Table 7: Linux known issues

Issue ID Known Issue Description Workaround Functional Area
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 8: 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

 

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.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating