Chat now with support
Chat with Support

Rapid Recovery 6.2 - Release Notes

Rapid Recovery 6.2 Release Notes New features Enhancements Deprecated in this release Resolved issues Known issues System requirements reference Licensing Rapid Recovery software and appliances Getting started with Rapid Recovery Globalization About us

Resolved issues

Customer-facing issues resolved in this release are listed below.

Table 1. Core and Windows resolved issues

Resolved Issue Description

Issue ID

Functional Area

Sometimes the Core failed to restore the configuration for some services during the remount volumes job that occurred after a factory reset, but the remount volumes job showed as successfully completed.

104043

Core

103813

RRT

In the Spanish UI, agentless virtual machines did not appear on the virtual machines tab in the Spanish interface.

103782

Localization

In the Korean UI, there was no ability to boot from a RASR USB flash drive due to invalid information in the BCD file (0xc0000098).

103775

Localization

The Agent service crashes when trying to collect cluster SQL metadata of a database with the FileAttributes.ReparsePoint attribute.

103740

Agent

The status of a virtual machine exported to ESXi appears as "Disabled" or "Stopped" after editing the export configuration, which is expected.

103704

ESXi

Replication started outside of the scheduled time if the job was added to the queue.

103702

Replication

Restoring ReFS volumes did not work on Windows Server 2016.

103698

Restore

There was no ability to add a cloud account for Azure Government.

103683

Azure

Core performance got worse and used a lot of system resources while mounting a recovery point from an attached Azure archive.

103670

Azure

A connection to the MongoDB reporting database cannot be established due to insufficient free ports, which is expected.

103664

Reports

Restoring a Core configuration with a configuration backup file of a previous Core was not restricted.

103632

Core

A machine with a root on a RAID volume didn't boot after a successful export.

103558

Export

103556

RRT

The limitation for the maximum concurrent exports did not work correctly after specific steps.

103515

Core

The error "Placeholder mismatch with format string [Checking volume images by read {0} on {1} recovery point {2}] and arguments ..." appeared while performing an integrity check on a DVM repository, even though the check was successful.

103492

Repository

Resizing the Dedup Cache failed with the error "cache_io_engine: windows error 87" if the Dedup Cache was located on a disk with a sector size of 4 KB.

103469

Repository

When protecting a vCenter virtual machine, agentless protections fails with the error "An item with the same key has already been added."

103426

Agentless protection

A Core localized in Brazilian Portuguese failed to communicate with the License Portal, because the string was not recognized as a valid DateTime.

103371

Localization

While protecting a machine agentlessly, if the maximum number of permitted snapshots was exceeded, an incorrect error message displayed.

103334

Agentless protection

A transfer failed because there are no retries present on the CleanupSnapshotInternal stage, which is as designed.

103310

Transfers

There was a logic issue with the option "Include only the recovery in the date range..." when this option was used for a scheduled archive.

103283

Archiving

Sometimes the export postprocessing step took a lot of time, because there was incorrect dismount logic in the driver.

102742

Export

Sometimes there was no ability to protect a second cluster that had the same hostname as the first cluster, even though it was from a different domain.

102702

Protection

Incremental and Virtual Standby Hyper-V exports failed if the location or name for the exported virtual machine contained Chinese symbols.

102589

Localization

The warning "VSS full snapshot was taken with excluded VSS writers 'Microsoft Exchange Writer has state'" appeared about a non-existing writer on a protected machine (SQL or Exchange, depending on the instance installed) during log truncation.

102567

Protection

Incremental snapshots were slow for volumes with specific write activity.

102493

Protection

Deferred delete canceled after a rollup job on French operating systems.

102436

Localization

After an upgrade to 6.1.2, repository maintenance failed after restoring the provisioning configuration.

102340

Upgrade

After several days, the AAFileFilter driver caused a blue screen to appear on a Hyper-V cluster running Windows Server 2012 R2 or Windows Server 2016.

102232

Agentless protection, server cluster, driver

A seed drive job automatically canceled due to a NullReferenceException.

101617

Seed drive

On Windows 2016, some drivers were blocked during an installation of the Agent software with the "Secure boot" option enabled.

101573

Agent installation

The VMwareProxy service crashed due to TCP/IP port exhaustion.

101485

VMware proxy

A remount job did not restore the locale of a Core.

101316

Localization

If a letter was assigned to a Recovery partition, the status of the volume displayed as "Not valid."

101224

On a system test environment, ESXi virtual standby failed with the error "An entry with the same key already exists."

100868

ESXi

The VMM actions were available while the ESXi host was in maintenance mode.

35740

ESXi

There was an incorrect validation for the "Maximimum connection pooling size" and the "Minimum connection pooling size" fields for the MongoDB connection.

35607

Reports

A base image was taken when the NTFS Boot Sector copy changed.

34981

NTFS

Virtual disk provisioning failed with Return Code 4 if the storage pool did not consistently have empty space, which is as designed.

34937

Virtual machines

Unexpected base images were taken of the ESX(i) virtual machines that had snapshots with quiescing enabled.

34916

ESXi

The Virtual Standby tab performance was slow.

34434

Exporting

The warning message "Information about allocated space for some volumes is unavailable..." appeared on the Summary tab for a protected virtual machine (VM) if that VM was located on an NFS datastore.

33551

Virtual machines

All running archive jobs failed with the error "There is not enough space on the disk" if more than one archive job was in progress at the moment when the target network storage ran out of space.

31827

Archiving

Rollback or export using SAN transport mode failed because one of the parameters had an invalid error in ESXi.

29508

Agentless

Table 2. DL appliance resolved issues

Resolved Issue Description

Issue ID

Functional Area

On a DL1000, sometimes launching FTBU would hang on the splash screen after a required reboot of the server during a configuration using the first wizard.

105114

FTBU

Some ESXi export jobs failed with the error "VddkApiException: You do not have access rights to this file."

105029

ESXi

If one of the physical disks on a DL1300 or DL1000 was offline, the FTBU would hang after the first wizard on the "Applying Settings ..." window.

103699

FTBU

On a DL1300 or DL4300 with FI#3.2.55, the ApplianceProvisioningConfiguration.xml file was present on the RECOVERY partition after configuring FTBU.

103389

FTBU

Sometimes the message "Internal Server Error" appeared on the Backup tab.

102379

RASR

Jobs failed with the error "System.OutofMemoryException" on DL appliances after running for a period of time, which is as designed.

101246

Jobs

If a letter was assigned to a Recovery partition, the status of the volume displayed as "Not valid."

101224

Provisioning

Windows Backup could not be created because the necessary volume items for a backup could not be determined if the volume letters were changed.

100985

Windows Backup

If Windows Backup was forced on a server with old Winbackups of a 75 GB volume with no free space on the internal controller, the main appliance status was red and could not be resolved.

100887

Windows Backup

A restore of the provisioning configuration job failed with the uninformative error "Cannot mount volume to the folder 'I:\' because it contains files or folders," if the virtual disk has a letter that was already used before the remount.

35805

Provisioning

The behavior of the logic used to determine the provisioning size was incorrect.

35770

Provisioning

The GUI was not disabled immediately after confirming the remount process.

35579

Provisioning

The Start VM and Start Network Adapters buttons were not disabled when an ESXi or Hyper-V export of a machine was launched.

30989

Exporting

Table 3. DocRetriever resolved issues

Resolved Issue Description

Issue ID

Functional Area

DocRetriever failed to retrieve SharePoint hierarchy if a web application's port contained an extra space character.

105749

Restore

An incorrect username was displayed in the "Modified by" and "Modified" columns after restore of a file uploaded by another user. The file now shows the original username after restore.

105101

Restore

DocRetriever failed to open a SharePoint 2016 database with several sites that had similar IDs.

103710

SharePoint

DocRetriever did not restore "Content Editor" web parts in SharePoint 2013.

103241

Restore

The DocRetriever Agent did not work (all restore operations failed) on a machine with MOSS 2007 32-bit installed. Corrected for 6.1.2 and 6.1.3. 32-bit versions are no longer supported.

102522

Restore

Table 4. Documentation resolved issues

Known Issue Description

Issue ID

Functional Area

The components ANTLR 3.3.3 and ANTLR 4.0.2 previously appeared in the "Third-party contributions" topic found only within in-product help. These versions were not used in Rapid Recovery 6.1.3 and have been removed. The 6.2 version references ANTLR 3.4 and 4.0.2.

104031

Context-sensitive help

The component MongoDB 2.6 previously appeared in the "Third-party contributions" topic, even though it was not used in Rapid Recovery 6.1.3. For 6.2, the listing is updated to reference MongoDB 2.6.11.

104030

Context-sensitive help

The component Microsoft Windows Azure Storage 7.2.1 did not appear in the 6.1.3 third-party contributions topic. 6.2 uses version 8.2.0, which is included in the list.

102504

Context-sensitive help

The component DataGridViewImageAnimator 1.0 appeared in the 6.1.3 third-party contributions topic, even though it was not used in Rapid Recovery 6.1.3 and is no longer used. It has been removed in the current list.

102503

Context-sensitive help

The component SimpleRestServices 1.3.0.3 did not appear in the list of third-party contributions, whereas an outdated version had appeared. This version is included in the current list.

102502

Context-sensitive help

The component OpenStack.NET 1.4.0.2 did not appear in the list of third-party contributions, whereas an outdated version of the component appeared in its place. This version is included in the current list.

102501

Context-sensitive help

The component NLog 3.2.1 did not appear in the list of third-party contributions, whereas an outdated version of the component appeared in its place. The current list references version 4.4.1.2, which is used in release 6.2.

102500

Context-sensitive help

The component AWS SDK for .NET 3.3.1.2 did not appear in the list of third-party contributions, whereas an outdated version of the component appeared in its place. The current list references this version.

102499

Context-sensitive help

Table 5. Linux resolved issues in release 6.1.3.527

Resolved Issue Description

Issue ID

Functional Area

There was no ability to support LVM-based storage pools.

103488

LVM

Transfers from a Core failed on SLES 11.4 x32 with the following error: "The partition size is incorrect, please shrink the volume."

103300

SLES

There was an ability to select Linux system folders for a rollback restore, even though restoring to a system folder is not supported.

103178

Restore

The Agent service could not be started if it was installed on a machine that did not use the default init system, which is as designed.

35818

Agent

Specific volumes could not be mounted after the export of a Linux machine.

35288

Export

Table 6. Mailbox Restore resolved issues

Resolved Issue Description

Issue ID

Functional Area

MailboxRestore failed to perform restore to original location on specific environment due to wrong flags passed into OpenMsgStore MAPI method.

105755

Restore

Public folder permissions were not restored for empty folders.

105267

Restore

After opening an Exchange 2016 CU5 database in Mailbox restore, the Inbox folder was missing in some mailboxes.

104334

Restore

A security alert dialog did not display during a restore when the Exchange server used a self-signed certificate.

102765

Restore

A non-informative error message appears if the user was not found in GAL during a restore of permissions for a public folder.

102018

Restore

Known issues

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

Table 7. Core and Windows known issues

Known Issue Description

Issue ID

Functional Area

Unexpected base images occur for cloned disks during Hyper-V agentless transfers.

Workaround: None.

106296

Hyper-V

The New License and Privacy Policy parameters are not rewritten during a Core installation if the Core was previously uninstalled without configurations.

Workaround: In the Settings of the Core Console, set the Privacy Policy and License settings.

106243

Configuration

An export to Amazon EC2 fails if the Amazon account has few subnets.

Workaround: None.

106107

Exporting

The custom retention policy for a virtual machine on a Hyper-V cluster is not saved and rollup does not perform.

Workaround: Add the retention policy to the Nightly Jobs in the Core settings.

106088

Retention policy

There is no ability to deploy and protect the machines if an older version of the Agent (release 5.4.3, 6.0.1, or 6.0.2) is installed on the Hyper-V server and you raise an error: "Unexpected end of file."

Workaround: Manually upgrade the Agent on the Hyper-V server to release 6.2.

105500

Hyper-V agentless

The Trustedinstaller process is called during every metadata request.

Workaround: None.

105445

Metadata

The RapidRecoveryCore service is deleted during an upgrade of the Core if any Microsoft Management Console (MMC) windows are open.

Workaround: Close all MMC windows before you begin upgrading the Core.

105282

Upgrade

In a specific case, replication fails to start with an "incorrect RPFS file size" error.

Workaround: None.

105048

Replication

Agentless backups fail with the error "Invalid URI: The hostname could not be parsed" when the shadow copy has the path "\\?\Volume{fb3687e7-57b5-11e7-80c4-f48e38cee0fd}\diskc.vhdx."

104393

Agentless

After an upgrade from release 5.4.3 to release 6.1, all task events convert to service events.

Workaround: None.

103945

Upgrading

On specific environments, the Core GUI launch after an upgrade from release 6.1.1 to release 6.1.2.

Workaround: Complete the following steps:

103783

Upgrading

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

Workaround: Copy the following DLLs from Coreservice\vddk\bin to the Coreservice folder:

Restart the Core service.

103477

Virtual exports

If the Core has more than 100 virtual machines under protection, it is not possible to protect an ESXi virtual machine agentlessly due to a timeout error in the wizard.

Workaround: Increase the .\CoreVMwarePRoxyService\ConnectionTimeout to 10 minutes.

102893

Agentless

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

Workaround: Specify the service name in the format - just hostname.

102756

Azure

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

Workaround: Contact Support for a script to run on the exported machine that solves the issue.

102390

Virtual exports

An unclear error message appears for an ESXi export with auto disk mapping.

Workaround: None.

27309

Virtual export

Table 8. DL Appliance known issues

Known Issue Description

Issue ID

Functional Area

The wrong translation appears in the German version of the Items Backed Up table on the Backup page. Future versions will be corrected.

Workaround: In the first column, the intended label is "der Zustand" instead of "Bundesland."

35031

Localization

Table 9. Documentation known issues

Known Issue Description

Issue ID

Functional Area

The license/copyright for the third-party component python minimal 2.7.7 does not appear in the list of third-party contributions in the product.

Workaround: The python minimal 2.7.7 component uses the Python 2.7 license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyrights:

106842

3PC

The license/copyright for the third-party component openssh-server 1.7.2 does not appear in the list of third-party contributions in the product.

Workaround: The openssh-server 1.7.2 component uses the OpenBSD 1.19 license, which is available at http://www.quest.com/legal/license-agreements.aspx. The component includes the following copyrights:

106841

3PC

A change was introduced in Rapid Recovery Core after documentation was published and translated related to log truncation for Oracle databases. The "Log truncation for Oracle" nightly job is now disabled by default, to keep parity with default behavior of log truncation for other supported applications. Future editions of the User Guide will update topics "About protecting Oracle database servers" and "About truncating Oracle logs" to note that the nightly job is disabled by default.

Workaround: Users are advised that log truncation for Oracle is disabled by default. You can enable this nightly job to automatically truncate logs on a daily basis, or you can manually truncate logs on demand.

106264

Technical documentation, nightly jobs, log truncation

System requirements for Rapid Recovery now appear only in the Rapid Recovery System Requirements Guide. References to system requirements in other technical documents now reference that guide instead. This includes the Rapid Recovery Installation and Upgrade Guide and the Rapid Recovery Third-Party Integration Guide. No other content changed in the latter document.

Information that previously appeared as appendices in the Rapid Recovery User Guide have been removed. These chapters will be published as the Rapid Recovery Commands and Scripting Reference Guide.

104973

Technical documentation

The Rapid Recovery User Guide procedure "Deploying a virtual machine in Azure" for release 6.2 contains unnecessary steps 4 through 8. Future versions of documentation are to be modified accordingly.

Workaround: When following this procedure, disregard steps 4 through 8. After performing step 3, skip to step 9. This step is performed on the Destination page of the Deploy to Azure Wizard.

101859

Azure export

The Rapid Recovery User Guide procedure "Setting up continual export to Azure" for release 6.1.x contains unnecessary steps 4 and 5. Future versions of documentation are to be modified accordingly.

Workaround: When following this procedure, disregard steps 4 and 5. Since you are defining ongoing continual export, you are not prompted to select a recovery point. After performing step 3, skip to step 6. Likewise, there is no Summary page at the end of the wizard. On the Volumes page of the wizard, click Finish (instead of Next).

101858

Azure export

Containers created in Azure are used to store virtual machines exported from the Rapid Recovery Core to your associated Azure account. If you create a specific container prior to performing virtual export, the Virtual Machine Export Wizard typically displays that container as one of the choices in the Container name field of the Destination window. If you create the container by typing a valid container name into the Container name field as part of the process of defining a virtual export, the container may not be immediately visible in the wizard. This behavior is not reflected in the appropriate procedures in the Rapid Recovery User Guide.

Workaround: If you create a container from the Virtual Machine Export Wizard, and that container is not accessible in the wizard UI, simply close the wizard, and launch it again, and you should then be able to access the newly created container. Future versions of documentation are to be modified accordingly.

101853

Azure export

When performing virtual export to Azure, the Rapid Recovery Core uses Azure storage and containers created using the Classic management model. Containers created in Azure using the newer Resource Manager deployment model are not recognized by the Core. The Rapid Recovery User Guide procedure "Creating a container in an Azure storage account" for release 6.1.x does not specify that the Classic management model is required. Future versions of documentation are to be modified accordingly.

Workaround: Use the Classic management model to create storage accounts and containers for virtual export. If you already have a storage account created using the Classic model, any new containers created for it will automatically use the correct model (Classic).

101837

Azure export

The issues listed in the Linux table below apply to release 6.1.3.527.

Table 10. Linux protection known issues

Known Issue Description

Issue ID

Functional Area

Snapshots and jobs for taking metadata fail for some Linux servers with RAID5 hardware.

Workaround: This defect was resolved in Linux Agent 6.1.3.527. Upgrade to this build if experiencing this issue.

104919

Protecting

Protection of volumes created with LVM-based storage pools fails. LVM functionality will be included in a future release.

Workaround: Contact Support to request a patch that addresses this issue.

103488

Protection

Unable to use TLS 1.2 with Linux Agent. This is related to the version of Mono in release 6.1.3. Upgrade to Linux Agent 6.2 when available, which includes TLS 1.1 and 1.2 support.

Workaround: None.

101279

TLS

An ESXi agentless RedHat machine is not bootable after a VirtualBox export.

Workaround: None.

31277

Virtual export

Agentlessly protected Linux machines are not bootable after BMR.

Workaround 1: Use the Rapid Recovery Agent on all supported Linux distributions instead of using agentless protection if BMR is required.

Workaround 2: To fix boot issues, engage a knowledgeable Linux administrator to update the volume, reinstalling grub and editing the content of /etc/fstab. Other steps may be required for individual distributions.

31206

BMR bootability

System requirements reference

System requirements for Rapid Recovery and all related components are now located in the Rapid Recovery System Requirements Guide. Please refer to this document on the technical documentation website.

Licensing Rapid Recovery software and appliances

Before you use and manage any version of Rapid Recovery, AppAssure, or Quest DL series backup and recovery appliance, you must first obtain a software license. To purchase licenses, contact the Quest 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.

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 (typically 10 days), the Core stops taking snapshots for non-trial licenses.

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 General Data Protection Regulation compliance.

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, and 9-digit Quest license number (in format 123-456-789).
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:
a.
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.
b.
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.
c.
Verify your account information. Check your email and verify your account information by clicking Verify email address.
The Add License Numbers page appears.
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:
b.
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.
4.
Enter your license numbers. For each nine-digit Quest license number included in your welcome email, click in the License Number field 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.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating