Welcome to our NEW support portal! We are now Quest, with a dedicated support site. Learn more.
These release notes provide information about the Dell Data Protection | Rapid Recovery™ release, build 18.104.22.168.
Dell Data Protection | Rapid Recovery software delivers fast backups with verified recovery for your VMs and physical servers, on-premise or remote. Dell™ Rapid Recovery is software built for IT professionals who need a powerful, affordable, and easy-to-use backup, replication, and recovery solution that provides protection for servers and business-critical applications like Microsoft® SQL Server®, Microsoft Exchange, and Microsoft SharePoint®. Using Rapid Recovery, you can continuously back up and protect all your critical data and applications from a single web-based management console.
Rapid Recovery release 6.0.2 is a minor release, with enhanced features. See Enhancements.
Previously named AppAssure, Rapid Recovery has been rebranded in release 6.0.x to reflect the next step in its evolution. The new name applies to Rapid Recovery Core, as well as the Rapid Recovery Agent software you can install on machines to protect their data.
Some other components have been rebranded for consistency. For more information on rebranding, see the Enhancements topic in Rapid Recovery 6.0.1 Release Notes.
For Rapid Recovery 6.0.x users that want to replicate on-premise Cores to the cloud, a new Azure VM is available. For more information, see the Dell Data Protection | Rapid Recovery Replication Target for Microsoft Azure Setup Guide available on the Dell Software website. There is an upgrade path for users of AppAssure Replication Target for Azure (release 5.4.3)
If you are using AppAssure Replication Target for Azure (release 5.4.3) and plan to upgrade your on-premise source Core, you can upgrade your target Core on Azure. See the updated Setup Guide for upgrade information.
Rapid Recovery 6.0.2 is a minor release, with enhanced features and functionality, and defect fixes.
The following is a list of enhancements implemented in Rapid Recovery release 6.0.2.
Additionally, release 6.0.x brought many other enhancements from release 5.4.x, such as rebranding from AppAssure to Rapid Recovery. Other changes included UI enhancements; OS support changes for Windows and Linux agents; virtual export and virtual standby to Microsoft Hyper-V cluster-shared volumes (CSV) running Windows Server 2012 or Windows Server 2012 R2 machines; importing archives on a schedule; and more. For detailed information on these changes, see Rapid Recovery 6.0.1 Release Notes.
The release is localized to the following languages: Chinese (Simplified), French, German, Japanese, Korean, Portuguese (Brazil), Spanish.
Recovery point data are stored in Recovery Point File System (RPFS) files in the repository. When you manually specify the deletion of a recovery point, or when the Core enforces rollup to merge or delete a recovery point, the specified recovery points are marked for deletion. This action creates a "Deleting of Index RPFS File" job on the Core. The relevant recovery points are immediately removed from the Core Console user interface.
The deletion job is immediately queued and then starts running in the background, concurrent with other Core operations. Deletion of recovery points is a processor-intensive task that may take hours. This delay in the removal of marked recovery points is known as the deferred delete feature of Rapid Recovery Core. This feature was first introduced in AppAssure release 5.4.1.
In Core environments under heavy load (such as undersized Cores, or environments with slow network speeds or infrastructure) performance of transfer jobs can be slow when performed concurrently with deferred delete jobs.
As an enhancement in release 6.0.2, Core now includes a new Deferred Delete option in nightly jobs. This option controls a single parameter: the ability to configure a maximum execution time for deferred delete during nightly jobs. The new deferred delete nightly job option is disabled by default.
When this new option is enabled, then after other nightly jobs have completed, a "Deleting records previously flagged for deletion" job is given the highest priority on the Core. Any new jobs for transfer, replication, and so on are queued behind the deferred delete job. In this way, Core processing is dedicated to removing deferred delete jobs, which complete much more quickly since other jobs are not running. When all marked recovery points are deleted, or when the maximum execution time period specified has passed, nightly jobs are completed, and the Core resumes normal operations. Transfers and other operations resume, and deletion of any remaining marked recovery points continues as a background job.
The default period for the maximum execution time for deferred delete is four hours. You can customize this timeout threshold in hours and minutes, from a minimum of 5 minutes to a maximum of 23 hours and 59 minutes. The amount of time for dedicated deletions should be determined based on load on your Core and the number of recovery points that are typically in the queue to be deleted.
Dell recommends using the default setting for this option (disabled) unless you are encountering transfer performance issues related to queued recovery point deletions. If you enable this new option, Dell recommends reviewing your Core jobs to ensure most recovery points marked for deletion are removed from the repository within a one-week period. This approach helps to balance maximum transfer performance with maximum reclamation of repository space.
For more detailed information on deferred delete, see Dell Knowledge Base article 198715, Understanding Deferred Delete in Nightly Jobs.
In addition to the Linux operating systems supported since Rapid Recovery release 6.0.1, the following Linux operating systems are now supported for Rapid Recovery Agent:
For a full set of software requirements for Rapid Recovery Agent, including other supported Linux operating systems and distributions, see the topic Rapid Recovery Agent software requirements.
Rapid Recovery release 6.0.2 includes improved integration with the VMware Virtual Disk Development Kit (VDDK) for creating and accessing VMware virtual disk storage. Rapid Recovery calls to the VDDK application program interfaces (APIs) have been separated into a VMware Proxy Service. As a result, if an API hangs (such as if a requested connection is temporarily unavailable), the process is terminated, and a new VDDK wrapper process is started.
This enhancement increases the likelihood that slow-responding or failed VMware API calls can be retried and likely performed. This affects setting or customizing the VMware proxy service port; changing timeout settings for the proxy; restarting the proxy service; and cleaning up snapshots when a repository is full.
The following Microsoft operating systems have recently reached end-of-life (EOL) and are no longer supported by Dell:
EOL applies to any service pack and any edition of the specified operating systems. When operating systems achieve the EOL phase, the software manufacturer stops supporting it. As a result, Dell does not support operating systems that have reached EOL.
If you protect machines in an AppAssure or Rapid Recovery Core that use an OS that has reached EOL, you do so at your own risk. If you experience problems recovering data from these machines, addressing these issues is outside the scope or responsibility of Dell Support.
In release 6.0.x, Microsoft Windows® 10 support includes the following exceptions:
Detailed information is now available about the operating systems supported by Rapid Recovery. See the following resources:
Rapid Recovery Release 6.0.2 includes updates to the following product documentation.
Context-sensitive help is generated from this document, and is accessed from the Rapid Recovery Core. Some minor edits or additions that appeared in the Dell Data Protection | Rapid Recovery User Guide release 6.0.1 but not in help files have now been updated. Help files also include minor updates to improve the appearance of tables in XML format. Information about third-party components, previously included in release notes, is accessible in release 6.0.x in contact-sensitive help. In the Rapid Recovery Core console, from the Help menu, select About, and then click Third-party contributions.
The following documentation has been discontinued:
Additional information about APIs is available in HTML files included in the SDK, in the form of reference materials and samples. You can obtain the SDK from the Downloads page of the Dell Data Protection | Rapid Recovery License Portal.
Issues resolved in this release are listed below.
|Resolved issue||Issue ID||Functional area|
|Rapid Recovery Central Management Console did not display images correctly if installed on any machine without the AppAssure or Rapid Recovery Core service.||32532||MCMP|
|The Rapid Recovery Central Management Console failed to start on a domain controller with the error 'An error occurred during the request execution.'||32123||MCMP|
|Rapid Recovery Central Management Console did not display images correctly for any core server if the Core service was not running on the Central Management Console.||32093||GUI|
|Resolved issue||Issue ID||Functional area|
|When the number of concurrent agentless transfers was increased from default of 3 to 10, performance of agentless transfer decreased, and frequency of transfer failures increased.||33286||Agentless protection|
|Repository did not mount after upgrade to Rapid Recovery 6.0 if record mode for RPFS record was changed to 0. In rare circumstances, the record mode for RPFS records may be changed to an invalid value due to defects in builds prior to 5.4.1.||32974||Repository|
|CSV reports were incorrectly formatted.||32966||Reporting|
|Migration step did not start for Background Job Settings.||32670||Backward compatibility|
|There was no ability to modify SQL metadata gathering timeout when using UseSqlQuery option.||32639||Metadata|
|Cores with a non-default deduplication cache size displayed an incorrect free space calculation during upgrade.||32608||Installer|
|Core Console GUI did not display after upgrade if Core had any custom groups established.||32488||Core|
|Core install fails with the error "Application catch an exception System.NullReferenceException depth 0: Object reference not set to an instance of an object. (0x80004003)" when installing in silent mode.||32100||Installer|
|A restore of the Core settings with repositories could not be performed in the "Restore Repositories" pop-up after fixing the path for the repository.||31990||GUI|
|Checkdisk of system volume fails after restore in ESXi Agentless.||31981||VMware agentless|
|Several check jobs (including SQL Attachability, Exchange Mountability, Exchange Checksum, Recovery point checks) in some circumstances had caused deadlock during execution which could not be cancelled.||31881||Core|
|Sometimes the Core service crashes during simultaneous deploy of multiple Linux agents when upgrading agents.||31878||Bulk deploy|
|Full virtual standby export occured in place of incremental exports after an incremental snapshot. This event occurred if the Core ran on a VM located on the same ESXi server to which virtual standby export was established.||31877||Virtual standby|
|Transfer failed if any disk on VM used format ...-000001.vmdk in ESXi agentless protection.||31738||VMware agentless|
|Transfers for ESXi agentless machines were stuck on a specific environment.||31352||VMware agentless|
|Replication failed with error "...Failed to synchronize the lists of consumed and outstanding seed drives" if upgrading source and target Cores from release 5.4.3 with outstanding seed drives on the source Core.||30339||Replication|
|The "Background Job Delayed" event created high load on Mongo DB, which led to delays in email notifications.||29450||Alerts|
|Replication in old (pre-5.4.1) replication mode tried (and failed) to transfer volume images to the target Core that were already replicated.||25648||Replication|
|There was no ability to schedule Deferred Delete jobs.||04739||Deferred delete|
|Resolved issue||Issue ID||Functional area|
|Links are duplicated on the top link bar if restoring only subsites during an out-of-place restore.||31629||GUI|
|Resolved issue||Issue ID||Functional area|
|Protected Linux machines crashed on startup if the machine contained devices that were not listed in the LVM configuration.||32880||Linux Agent|
|Rapid Recovery Agent service failed to start on Linux machines if the volume group name containing the swap volume contained a hyphen.||32715||Linux Agent|
|SLES 12 was not bootable after BMR.||31762||Linux Live DVD|
|Agent fails to take next snapshot after a previous snapshot fails because the new generated data was larger than the size of the datastore.||31695||Linux Agent|