vCenter/ESXi support changes
VMware vCenter version 5.5 reached end of general support by its manufacturer in September 2018. In Rapid Recovery release 6.3, Quest offered limited support of ESXi 5.5 as an export target and for agentless protection using Rapid Snap for Virtual.
In Rapid Recovery release 6.4, ESXi 5.5 is no longer supported as an export target. Limited support for agentless protection continues in this release.
General support by VMware for ESXi 6.0 is expected to end in March 2020. VMware recommends that its customers upgrade to vSphere 6.5 or vSphere 6.7. Rapid Recovery users are advised to migrate to fully supported versions and be aware of the support dates.
Full support by Quest is provided only until a related product reaches end of general support by its manufacturer; thereafter, its support within Rapid Recovery is limited in that release, and its status is deprecated—it will not be supported in future releases.
For a full list of supported versions for vCenter/ESXi and all other products that Rapid Recovery works with in release 6.4, see the Rapid Recovery 6.4 System Requirements Guide.
Hypervisor support changes
Rapid Recovery customers are advised of the following changes for supported hypervisors.
Oracle VM VirtualBox
Rapid Recovery supports Oracle VM VirtualBox as an export target for virtual machines.
Recent VirtualBox support changes
New in release 6.4 is support for VirtualBox version 6.0.
VirtualBox support matrix
The following matrix shows Quest Data Protection Support status for VirtualBox versions:
| VirtualBox Version | End of General Support | Support Status in 6.4 |
|---|---|---|
| 5.1 | July 2020 | Limited support |
| 5.2 | July 2020 | Supported |
| 6.0 | December 2023 | Supported |
See the Oracle Lifetime Support Policy on the Oracle website.
VMware Workstation
Rapid Recovery supports VMware Workstation as an export target for virtual machines.
Recent VMware Workstation support changes
- Support for VMware Workstation version 11 is discontinued.
- Support for VMware Workstation versions 12 and 14 is now limited.
- VMware Workstation version 15 is now supported.
VMware Workstation support matrix
The following matrix shows Quest Data Protection Support status for VMware Workstation versions:
| Workstation Version | End of General Support | Support Status in 6.4 |
|---|---|---|
| 11.x | June 2016 | Limited support |
| 12.x | February 2018 | Limited support |
| 14.x | March 2019 | Supported |
Quest recommends that Rapid Recovery customers using versions of VMware Workstation that are no longer supported or are in limited support upgrade to VMware Workstation 14 (or a later version when supported).
VMware vSphere on ESXi
Rapid Recovery supports VMware vSphere/vCenter on ESXi, both as an export target for virtual machines, and for agentless protection.
Recent ESXi support changes
In September of 2018, vSphere Hypervisor ESXi 5.5 reached end of general support. VMware no longer supports that version of ESXi. Accordingly, only limited support is extended to Quest Data Protection Support customers using ESXi 5.5 in this release.
Additionally, ESXi 6.0 reaches end of general support in March of 2020.
This support applies to ESXi as a target for virtual export, as well as for agentless protection. Support for these versions is deprecated and is expected to be discontinued in an imminent release.
Quest recommends that Rapid Recovery customers using ESXi 5.5 and 6.0 upgrade to vSphere 6.5 or vSphere 6.7.
VMware ESXi support matrix
The following matrix shows Quest Data Protection Support status for VMware vCenter/ESXi versions as a target for virtual export:
| vCenter/ESXi Version | End of General Support | Support for Virtual Export in 6.4 | Support for Agentless Protection in 6.4 |
|---|---|---|---|
| ESXi 5.5 | September 19, 2018 | Not supported | Limited support |
| ESXi 6.0 | March 12, 2020 | Supported | Supported |
| ESXi 6.5 | November 15, 2021 | Supported | Supported |
| ESXi 6.7 | November 15, 2021 | Supported | Supported |
See the VMware Lifecycle Product Matrix on the VMware website.
Microsoft Hyper-V
Rapid Recovery supports Hyper-V both as an export target for virtual machines, and for agentless protection.
Recent Hyper-V support changes
- Windows 8 reached end of support in January 2018. For this release, Quest offers limited support for virtual export to a VM running Windows 8 (64-bit), as well as agentless protection.
- Windows Server 2008 (SP2) and Windows Server 2008 R2 (SP1) were both previously included in the Rapid Recovery 6.2.1 System Requirements Guide as being supported for virtual export. These operating systems are no longer supported in release 6.4 for virtual export or agentless support.
- Windows Server 2012 reached end of support in January 2018. Rapid Recovery offers limited support for agentless protection on Hyper-V servers running this operating system. Virtual export to Hyper-V targets running Server 2012 is supported for this release.
- Windows Server 2012 R2 reached end of support in January 2018. Rapid Recovery offers support for agentless protection on Hyper-V servers running this operating system, as well as virtual export to Hyper-V targets running Server 2012 R2. This support is likely to change in future releases.
- Hyper-V running on Microsoft Windows Server versions 2008 R2 SP1, 2012, 2012 R2, 2016, 2019 (limited).
- Limited support is available for Windows Server 2019 as a VM export target in release 6.4. Full support of this hypervisor is expected in future releases.
|
|
NOTE: Regarding limited support, Quest Data Protection Support accepts support calls for these features by customers with a current maintenance agreement. Support representatives may offer suggestions and work-arounds when available. Quest does not commit to software patches or revisions related to products or operating systems that have reached end of life. Users are advised that any support provided by Quest for EOL software is deprecated and likely to be discontinued soon. |
For information on end-of-life dates, see Hyper-V Server lifecycle on the Microsoft website.
End of support for Linux Agent 6.3 for various distributions
End of support for version 6.3 of Red Hat, CentOS and Oracle Linux
Quest strives to put resources behind the most recent product releases in order to continually improve and enhance the value of our solutions. In some cases, that means we can no longer support older software versions that interact with our products.
Rapid Recovery release 6.4 no longer supports Red Hat Enterprise Linux version 6.3, or its companion distributions, CentOS 6.3 and Oracle Linux 6.3.
Quest recommends that users upgrade to the most recent Linux version compatible with your needs; for example, upgrade to release 6.6 or 7.x. For an updated list of operating systems supported, always refer to the topic "Rapid Recovery Agent software requirements" in the relevant version of the Rapid Recovery System Requirements Guide.
Customers who wish to continue backing up Linux machines using release 6.3 of those Linux distributions can choose to remain on Rapid Recovery Core release 6.3.0, which is the last release to support the specified 6.3 Linux distributions.
Resolved issues
This topic contains resolved issues in the following categories:
- Core and Windows resolved issues
- DL appliance resolved issues
- Documentation resolved issues
- Linux resolved issues
- Local Mount Utility resolved issues
- QorePortal resolved issues
The following is a list of issues addressed in this release.
Table 4: Core and Windows resolved issues
| Issue ID | Resolved Issue Description | Functional Area |
|---|---|---|
|
109436 |
On a specific environment, the Agent software on protected Linux machine crashed due to the inability to obtain MBR disk metadata sectors. |
Linux, MBR disks |
|
109740 |
Could not obtain Oracle metadata if the Oracle DB listener had non-default (customized) name. |
Oracle protection |
|
109615 |
Transfer failed for specific ESXI agentless VM with error: "Length cannot be less than zero. Parameter name: length." |
Agentless protection, ESXi |
|
109600 |
Transfer failed for ESXI agentless VM status: 'NotFound' if VM was hosted on vCenter in datacenter sub-folder. |
Agentless protection, ESXi |
|
109552 |
In specific environment with standard phone-home licensing, the Core could not automatically contact the license portal if connection to QorePortal was disabled. |
License portal |
|
109513 |
Rollup failed with error: "Can not find the recovery point with the id [ID]" after specific steps related to the mountability check job. |
Rollup, Mounts |
|
109442 |
On Recovery Points page for ESXi agentless VM, the "Allocated Space" metadata value in the Recovery Points summary table displayed incorrect values for large volumes. |
Agentless protection, ESXi, Core Console |
|
109418 |
Prior to optimizations in registry serialization, in a specific environment, VM export hung at 95% progress and eventually failed with timeout exception "The operation has timed out." |
VM export, Core Console |
|
109380 |
License type of Agent changed from Virtual to Physical after re-protecting an ESXi VM. |
Licensing, Agentless protection |
|
109231 |
Transfer failed due to exception: 'System.NullReferenceException' if ESXi VM was located in a child vApp. |
Agentless protection, ESXi |
|
109178 |
Damaged recovery points were captured for ESXi Agentless VMs using SAN transport mode. |
Agentless protection, ESXi, transfer mode |
|
109147 |
When machines protected with Rapid Recovery Agent 6.1.3 or earlier with high change rates were upgraded to Agent releases 6.2.0, 6.2.1, or 6.3.0, portions of the change log over 1MB were discarded. This resulted in damaged recovery points, which required capture of a new base image to ensure full restore options. For more information, see Quest Knowledge Base article 301910. Since this defect was corrected in release 6.4, Quest strongly encourages users of Rapid Recovery Agent versions 6.1.3 and older to upgrade directly to release 6.4.x. |
Agent upgrade, recovery points |
|
109140 |
There was no ability to select Hyper-V Generation 2 export for a Windows 2019 UEFI agent. |
Hyper-V, UEFI |
|
109129 |
The Core could not contact the Rapid Recovery License Portal using the "Contact Now" button in Core Settings even when connection to QorePortal was enabled. |
Licensing, Core Settings |
|
109059 |
In a specific environment with a non-typical configuration, mounts failed with Error "TevoMountReplay failed with error -2147024873 (0x80070017 - Data error (cyclic redundancy check))." |
Mounts |
|
109044 |
Damaged recovery points were captured for ESXi agentless VMs if transfer was performed with non-default Outstanding Reads per Stream setting (anything other than 0). |
Agentless, Protected machine settings, Transfer |
|
108879 |
Transfer for ESXi agentless VM fails if name contains Chinese characters |
Transfer, agentless protection, localization |
|
108825 |
For agentlessly protected cluster on ESXi or Hyper-V, there was no ability to associate the cluster to the hypervisor host to decrease license usage. |
Hypervisors, clusters, protection, licensing |
|
108782 |
Transfer failed with error: "Value cannot be null. Parameter name: list" for specific protected windows machine running Rapid Recovery Agent 6.2.1. |
Transfer; Agent |
|
108625 |
VMs agentlessly protected on vCenter Linked agents switch to trial once NPH key with large enough license pool is applied |
Licensing, Agentless protection |
|
108611 |
Incorrect validation message appeared in 'User Name' field when creating Rackspace Cloud Files account. |
Cloud accounts |
|
108385 |
For Cores with protected server clusters, paused protection for clusters (not nodes) resumed without explicit command after Core contacted the License Portal. |
Protection, Pause/Resume, server clusters |
|
108313 |
Upgrade, Deploy and other web-installer depended jobs failed with error code: 3002, "The certificate for MSI issued to Quest Software Inc is invalid." |
Web installer, certificates |
|
108174 |
For a replicated SQL Server cluster running Windows 2008 R2 Systems Configuration Checker (SCC), the error: "public action method 'SqlGrid' was not found on controller Replay.Core.Web.Controllers. ReplicatedClustersController'" appeared when trying to open the Summary page for the target Core. |
Replication, SQL Server cluster, Agent, Windows 2008 R2 |
|
100569 |
EC2 Export job fails with exception: 'Amazon.EC2.AmazonEC2Exception: The key pair '{key_name}' does not exist.' for replicated Agent from another region |
Virtual exports, Amazon E2C |
Go to the top of the Resolved issues topic.
Table 5: DL appliance resolved issues
| Issue ID | Resolved Issue Description | Functional Area |
|---|---|---|
|
100569 |
EC2 Export job fails with exception: 'Amazon.EC2.AmazonEC2Exception: The key pair '{key_name}' does not exist.' for replicated Agent from another region. |
Virtual exports, Amazon E2C |
Go to the top of the Resolved issues topic.
Table 6: Documentation resolved issues
| Issue ID | Resolved Issue Description | Functional Area |
|---|---|---|
|
108288 |
In-product help is now available for agentlessly protected ESXi and Hyper-V virtual machines (not just hypervisors) when viewing Active Block Mapping (ABM) settings at the machine level. |
Agentless protection, ABM, machine-level settings, In-product help |
|
108327 |
An incorrect web help link has been removed from the System Information page for protected virtual machines. |
Agentless protection, In-product help |
|
108934 |
Errors that were corrected in the 6.3 User Guide but had not been updated in the in-product help for that release are now also updated in the in-product help content. See the 6.3 release notes for details. |
In-product help |
|
N/A
|
License and copyright information for the components listed in Rapid Recovery release 6.3.0 Release Notes have been added to third-party components visible within in-product help if they are still appropriate. Additionally, the third-party components section contains substantial updates in release 6.4 to ensure all third-party components are identified as required. |
Third-party components, licensing, copyright |
Go to the top of the Resolved issues topic.
Table 7: Linux resolved issues
| Issue ID | Resolved Issue Description | Functional Area |
|---|---|---|
|
109453 |
Protected Linux machine captured base image instead of empty incremental when no changes occurred on the protected device. |
Base image, backup, Linux |
|
108750 |
BMR of Linux machine failed to start with error code: ERROR_REG_PARTS while mapping device with size greater than 3 TB. |
BMR, Linux Restore, Live DVD |
|
108395 |
There was no ability to protect a Linux machine with more than 2000 disk devices attached. |
Linux protection |
|
108290 |
Linux Live DVD did not recognize disks on a specific environment. |
Linux, Live DVD |
|
97017 |
Exported CentOS7 wasn't bootable on the ESX(i) when it had more than 6 system volumes and root volume with the 'xfs' filesystem. |
Virtual exports, Linux, XFS |
Go to the top of the Resolved issues topic.
Table 8: Local Mount Utility resolved issues
| Issue ID | Resolved Issue Description | Functional Area |
|---|---|---|
|
109087 |
There was no ability to open Exchange database using Mailbox restore from LMU. |
LMU, Exchange protection, Mailbox Restore |
Go to the top of the Resolved issues topic.
Table 9: QorePortal resolved issues
QorePortal features a What's new article that is refreshed with each deployment to list new features, enhancements, and resolved issues. To access the article, from the QorePortal header, click ![[Help Center]](/ko-kr/technical-documents/image/7ed5a61c-94dd-44a3-ae6d-6c21bc30d03e "[QorePortal Help Center]")
Go to the top of the Resolved issues topic.