Rapid Recovery 6.1 Release Notes
Rev. A00
Dell Data Protection | Rapid Recovery™ 6.1
Release Notes
December 2016
These release notes provide information about the Dell Data Protection | Rapid Recovery™ release, build 6.1.0.645.
Current Version: 6.1.0
Topics:
•
About Dell Data Protection | Rapid Recovery 6.1
•
New features
•
Enhancements
•
Deprecated in this release
•
Resolved issues
•
Known issues
•
Rapid Recovery system requirements
•
Product licensing
•
Getting started with Rapid Recovery
•
Globalization
•
About Dell
About Dell Data Protection | Rapid Recovery 6.1
Dell Data Protection | Rapid Recovery software delivers fast backups with verified recovery for your VMs and physical servers, onpremises 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.1 is a minor release, with new features and enhanced functionality. Support for some features, items, or related
components have changed. See New features, Enhancements, and Deprecated in this release.
Previously named AppAssure, Rapid Recovery has been rebranded in release 6 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.
Dell Data Protection | Rapid Recovery 6.1
Release Notes
1
Repository upgrade advisory
Upgrading the Core software to release 6.1 from any earlier version (for example, Rapid Recovery 6.0x, AppAssure 5.x) changes the
schema in your repository. The updates let you use new features in the latest release, including the ability to protect guests on a Microsoft
Hyper-V host without installing Rapid Recovery Agent on each guest.
Anytime you change the structure of your repository through an upgrade, you cannot downgrade the version of Core. Should you
determine in the future that you want to use an earlier version of Core after upgrade to this release, you will need to archive the data in
your repository. You could then re-import the information manually, which can be a substantial effort.
For new users of Rapid Recovery Replication Target for Azure
New users of Rapid Recovery Core release 6.1 can replicate their on-premises Cores in the Azure cloud. To create the replication target
VM, search the Azure Marketplace gallery for the Rapid Recovery Replication Target VM in Azure. For detailed steps, see the Dell Data
Protection | Rapid Recovery Replication Target for Microsoft Azure Setup Guide.
Upgrade advisory for current users of AppAssure Replication
Target for Azure release 5.4.3
If using replication, the source Core must not run a version of Rapid Recovery more recent than the target Core, or your cloud replica
ceases to replicate. The target Core can use a higher version of the Core software.
If you currently use AppAssure Replication Target for Azure (release 5.4.3) with an AppAssure 5.4.3 Core, and plan to upgrade your onpremises source Core to Rapid Recovery release 6.x, you can upgrade your target Core on Azure. Following are the basic steps for
upgrading:
1
Archive your repository (optional, recommended).
2
Upgrade your target Core on the Azure VM.
3
Update the existing parameters in the configuration script on the Azure VM.
4
Run the updated configuration script on the Azure VM.
5
Upgrade any other target Cores.
6
Upgrade source Cores that replicate to your Azure VM.
These steps are detailed in the topic "Upgrading from AppAssure 5.4.3 Replication Target" in the Dell Data Protection | Rapid Recovery
Replication Target for Microsoft Azure Setup Guide. Following this document is the best path for success for upgrading from an
AppAssure replication target to a Rapid Recovery replication target.
Other relevant factors:
•
You can continue to replicate an AppAssure 5.4.3 Core to an existing version 5.4.3 target Core VM on Azure. However, the 5.4.3
version of the replication target product is no longer available on the Azure marketplace.
•
If establishing replication on Azure for the first time, you must use the Rapid Recovery Replication Target VM product from the
Azure marketplace with a Rapid Recovery Core version 6.0.1 or later.
2
Dell Data Protection | Rapid Recovery 6.1
System requirements documentation advisory
For each software release, we review and update the system requirements for Rapid Recovery software and components. If using
localized versions of product documentation, always refer to the release notes for the most current system requirements. Release notes
are sometimes updated and re-issued in a release cycle.
Due to production deadlines for translating content, localized (non-English) versions of the following release 6.1 documents contain
outdated system requirements:
•
Dell Data Protection | Rapid Recovery Installation and Upgrade Guide
•
Dell Data Protection | Rapid Recovery Third-Party Integration Guide
Updated system requirements for Rapid Recovery release 6.1 are available in the release notes for all supported languages.
New features
New features in Rapid Recovery release 6.1:
•
Virtual export to Microsoft Azure
•
Rapid Snap for Virtual now supports Hyper-V® agentless (host-based) protection
•
Auto discovery of new Hyper-V or ESXi VMs
•
Tier recovery points to DR backup and deduplication appliances for secondary storage
•
File search and restore feature
•
New ability to run pre and post snapshot scripts on Linux machines
Related links
Enhancements
Deprecated in this release
Virtual export to Microsoft Azure
From the Rapid Recovery Core, you can export a recovery point from a repository to a virtual machine (VM). In Rapid Recovery release
6.1, we extend the platforms to which you can export recovery points to include Microsoft's Azure.
As with other virtualization platforms, you can perform a one-time virtual export, or you can set up continual export to a virtual standby,
which updates a VM with new data after the Core captures each new snapshot.
Working with Azure involves aspects unique to that cloud service provider. Unlike virtual export for other platforms, virtual export for
Azure is broken into two distinct processes: exporting, and deploying. This distinction was created in part to defray customer costs until
necessary. For Azure accounts, Microsoft charges fees for the following three services:
•
Storage space. Purchase storage space by attaching data disks to your Azure account. You can expand your storage space at any
time by adding more disks.
•
Compute resources. Azure offers infrastructure as a service (IaaS), priced based on the level of robustness of your memory, CPU,
and network infrastructure. Creating and running a virtual machine is an example of a process that uses compute resources.
•
Egress data. When you remove information from Azure servers to another source, fees are applied.
When you export a recovery point to Azure, the necessary set of files is extracted from Rapid Recovery, validated, and uploaded to the
specified container in Azure. Other than costs for the required storage, exporting by itself does not incur any Azure fees.
The deployment process uses Azure cloud REST APIs to create a VM hardware instance in a new storage container, and injects the virtual
hard disk (VHD) into the new VM. This process creates and boots a replica of the protected machine on Azure (the original machine must
Dell Data Protection | Rapid Recovery 6.1
3
be powered off). The original set of files exported to Azure persists, and continues to update after each snapshot. The deployed VM
contains your data at the time of deployment. From an Azure account perspective, after you deploy, you are then charged compute fees
for the VM on its servers. Also, since the deployed VM is a copy of the exported files, the deployment process doubles the amount of
storage space consumed on Azure for that virtual export.
For a one-time virtual export, there is no mechanism for deploying as a separate process. Thus, for a one-time export, Rapid Recovery
deploys to Azure automatically when you create the VM. This action triggers compute fees immediately, and consumes storage space.
When establishing virtual standby for a protected machine on Azure, to avoid use of extra storage space and VM charges, you can simply
define the export process. The result is an initial virtual export to Azure which is continually updated. Each time a snapshot is captured on
the Core, the exported files are refreshed in your Azure account with updated information. Before the virtual export can be used as a
bootable VM, you must deploy it, which triggers VM costs on Azure. Until you convert the exported files for a protected machine to a
bootable VM, no VM (compute) costs are incurred in your Azure account.
For Azure, export and eventual deployment create a VM using the classic VM management, not the newer resource manager model.
Rapid Snap for Virtual now supports Hyper-V® agentless
(host-based) protection
Rapid Recovery release 6.1 extends the Rapid Snap for Virtual feature to the Hyper-V hypervisor platform. When using Rapid Recovery,
administrators can install the Rapid Recovery Agent on the Hyper-V host, and protect guest virtual machines without needing to install the
Agent on each guest.
Since the Rapid Recovery Agent software is not required to be installed on every VM, this feature is known in the industry as agentless
protection. Since the Agent is installed on the host, we also refer to this as host-based protection.
When using host-based protection, the built-in virtual hard disk (VHD) parser converts changes made to VHD files to changes in the
resulting volume or disk image. Creation of a volume image is supported for FAT, NTFS, and ReFs file systems. For Windows volumes that
are dynamic disks, or for unsupported file systems (as indicated in system requirements), Rapid Recovery creates disk images.
The new AAFileFilter driver provides file-level protection supporting agentless and cluster-shared volume (CSV) support.
Hyper-V® host-based protection supports the following features in release 6.1: Archiving, recovery point integrity check, mounting,
protection of VM (including auto-discovery), protection of Windows Server 2012 R2 CSV, replication, and restore of VM (for VHDX but
not VHD). Also supported are rollup, virtual export, file-level restore for volume images, and for Linux agents only, file-level restore on disk
images.
When protecting clusters, the Agent software and supporting driver is required on each node of a cluster in which cluster-level support is
required. You can also protect clusters agentlessly if you do not need volume-specific recovery. The choice is yours.
Some limitations of this feature are described in the following list.
•
Concurrent operations with virtual disks that have same ID (cloned VMs) are not supported. The Core detects such situation and
prevents multiple background jobs requiring access to such virtual disks to run concurrently. Thus, for example, transfer and rollback
jobs are queued and start only when the previous job using the VHD completes.
•
Windows 10 does not have a Hyper-V VSS writer. As a result, all snapshots taken from Windows 10 VMs are marked yellow on the
Recovery Points page of the Core Console, indicating they are crash-consistent.
•
Application-consistent snapshots require a SCSI controller installed on the VM, as described in this Microsoft blog . These snapshots
have other requirements, as described in the MSDN knowledge base article Backing Up and Restoring Virtual Machines.
•
Agentless protection does not support advanced features such as SQL attachability checks and Exchange mount integrity checks.
•
VHDX formats are fully supported, but deprecated format VHD is not currently supported.
For more information, see the topic “Understanding Rapid Snap for Virtual” in the Dell Data Protection | Rapid Recovery User Guide.
4
Dell Data Protection | Rapid Recovery 6.1
Auto discovery of new Hyper-V or ESXi VMs
When you use Rapid Snap for Virtual (agentless protection) to protect virtual machines (VMs) on a Hyper-V server or cluster or an ESXi
host, you have the option to automatically protect any new VMs that you create on that host. This is an optional setting on the Select
Machines page of the Protect Multiple Machines Wizard. For VMs that are already protected, you can access the Settings page of the
protected Hyper-V host , and enable the Auto protect new virtual machines option.
Tier recovery points to DR backup and deduplication
appliances for secondary storage
As of Rapid Recovery release 6.1, you can relocate recovery points from your primary repository to an R3 repository on a Dell DR series
backup and deduplication appliance. This action frees up storage in your primary repository.
•
•
•
•
•
•
•
You must first add the DR appliance as a secondary repository on your Rapid Recovery Core.
NOTE: In this release, you can add a single DR repository for tiering older recovery points to secondary storage. For more
information on creating a new R3 repository on a DR, see the topic Creating an R3 repository in the Dell Data Protection |
Rapid Recovery User Guide.
You can then specify the age at which you want recovery points to tier to the appliance. You can specify the age by weeks, months or
years. The shortest period you can set is one week.
To establish tiering, select the Relocate outdated recovery points to an R3 repository option in the retention policy settings for your
Core or for a specific protected machine. For more information, see the Dell Data Protection | Rapid Recovery User Guide topics
"Configuring Core default retention policy settings" or "Customizing retention policy settings for a protected machine," respectively.
Recovery points are first saved to the primary repository associated with your Core. When they reach the age threshold you set, they
are transferred to the DR storage appliance.
After you set the relocation option in the relevant retention policy, tiering of outdated recovery points begins during the nightly rollup
job when a recovery point meeting the age threshold exists. When recovery points of the appropriate age exist, you can start tiering
immediately by forcing rollup.
Before tiering recovery points for the selected protected machine begins, a base image is automatically converted from the oldest
recovery point that will remain in your original DVM repository. This image serves as an anchor to ensure a complete recovery point
chain in the original DVM repository. With a complete recovery point chain, you can restore from recent recovery points on the Core or
older recovery points on the DR. As recovery points age, anchor base images adjust automatically when required.
When viewing recovery points for a protected machine, a yellow icon
appears in the Contents column for those recovery points
that are tiered to the DR appliance. Recovery points without the icon reside on the primary repository associated with the Core.
Protected machines with backup policies set for less than once per week that are set for tiering to the DR always have at least one
recovery point in the primary repository.
NOTE: Before tiering recovery points to a DR appliance, you must upgrade the appliance software to DR OS version 4.x.
File search and restore feature
Rapid Recovery release 6.1 introduces the ability to find a file that you want to restore from among the recovery points of a protected
machine. After the file is found, it can be restored directly from the search results.
The search feature uses filemasks and wildcards to search for a file through the recovery points of a specified machine. A time range filter
helps narrow the results from every recovery point that includes the file to a more manageable number of recovery points created within
the selected timeframe. More options recursively search within subdirectories of a location or only in a specified location; increase search
speeds on NTFS volumes; and limit the recovery points searched to a set number. The results include every recovery point that contains
the sought-after file.
Files can only be restored to the local Core. There is no ability to restore the file to a protected machine.
Dell Data Protection | Rapid Recovery 6.1
5
For more information, see “About the file search and restore feature” in the Dell Data Protection | Rapid Recovery User Guide.
New ability to run pre and post snapshot scripts on Linux
machines
Appendix D of the Dell Data Protection | Rapid Recovery User Guide includes sample scripts for protected machines. For Windows, these
run as PowerShell scripts. For Linux, these typically run as Bourne shell and Bash scripts. Scripts provided have file extensions of .ps or .sh,
as appropriate.
Some scripts apply only to one platform. For example, pre and post scripts for nightly jobs only apply to the Core, and have no Linux
equivalents.
The Linux scripts in previous releases included PreTransferScript, PostTransferScript, and PostExportScript.
New in Rapid Recovery 6.1.0 is the ability to run scripts at more distinct periods within the backup process. This is designed for use with
protected Linux machines, which take advantage of these distinctions. Accordingly, new sample scripts PreSnapshotScript and
PostSnapshotScript are included in the User Guide appendix. For Linux, these scripts have a file extension of .sh and run as Bourne shell or
Bash commands.
NOTE: Scripts run using the interpreter defined in the first line of the script; if the specified interpreter is not available, the
script uses the default shell defined in the $SHELL environment variable. All sample shell scripts provided in the User Guide are
identified in the first line of the script (#!/bin/bash) as Bash scripts. While you can substitute and use any interpreter, these
scripts were tested and run successfully specifically as Bourne shell or Bash scripts.
For both Windows and Linux machines, a PreTransferScript executes before the backup transfer process begins, and a PostTransferScript
executes after the backup transfer has completed.
For snapshots on Linux machines (as with Windows machines), when a transfer starts, a short preparation process takes place. But Linux
backups differ from snapshots for Windows machines because data is read from the original device for the protected machine, and then
data is read from a copy device, before the transfer is completed.
You can now run a PreSnapshotScript on a Linux machine after the transfer preparation but before data is read from the original device.
You can also run a PostSnapshotScript after the first read is complete and before the read for the copy device takes place.
This ability allows more flexibility if needed for scripting when capturing snapshots on Linux machines. Because of this distinction, this
functionality is unique to Linux backups.
6
Dell Data Protection | Rapid Recovery 6.1
Figure 1. The point in a snapshot in which pre and post scripts run
Supporting this new ability, two sample scripts are included in the User Guide that can be executed as PreSnapshot and PostSnapshot
shell scripts.
As always, any changes to provided scripts is considered customization, which is not typically supported by Dell Product Support.
For more information on pre and post scripts, see the topic “Execution timing for pre and post scripts” in the Dell Data Protection | Rapid
Recovery User Guide.
Enhancements
Rapid Recovery release 6.1 is a minor release, with new features, enhanced functionality, and defect fixes.
The following is a list of enhancements implemented in Rapid Recovery release 6.1.
•
Updated samples and description of Linux scripts
•
BTRFS support
•
New drop-down menu to switch between tasks, important alerts and all events
•
Reporting enhancements
•
New SQL Server version supported
•
Windows operating system support changes
•
Enhanced protection schedules
•
Ability to bulk cancel running tasks
•
Command Line Interface and PowerShell Module command enhancements
•
Mailbox Restore for Exchange enhancements
Related links
New features
Deprecated in this release
Dell Data Protection | Rapid Recovery 6.1
7
Updated samples and description of Linux scripts
Appendix D of the Dell Data Protection | Rapid Recovery User Guide has been updated. Specific improvements relate to Linux Bourne shell
and Bash scripts. Clarifications are indicated below.
•
Descriptions have been updated to clarify the ability of the Linux shell scripts to be executed with Bourne shell or Bash for any
supported versions of Linux.
Descriptions of all of the existing Linux sample scripts have been enhanced.
A new sample is provided for the post export script.
Two new sample scripts (PreSnapshotScript and PostSnapshotScript.sh) support the new ability to run shell scripts at specific points
within the backup transfer process. Because this functionality is relevant only to Linux machines, these sample scripts are provided for
Linux. There are no corresponding PowerShell scripts.
The pre and post export and snapshot scripts now reference a new diagram differentiating when each script is started.
•
•
•
•
BTRFS support
Beginning with release 6.1, Rapid Recovery supports B-tree file system (BTRFS) volumes on certain protected Linux machines.
BTRFS is supported only on operating systems with kernel version 4.2. or later. Compliant operating systems currently include Ubuntu
versions 14.04.4, 15.10, and 16.04. SUSE Linux Enterprise Server versions 12 and 12 SP1 have older kernel versions, and so Rapid Recovery
does not support their implementations of BTRFS.
When mounting a BTRFS volume from a compatible operating system, you must include the following parameter:
mount -o nodatasum,device=/dev/xxx /dev/xxx /mnt/yyy9
New drop-down menu to switch between tasks, important
alerts and all events
A new drop-down menu lets you switch the events view between tasks, alerts, and the journal. This menu appears to the right of the title
in the Tasks, Alerts or Journal pane.
Events logged by the Core are visible from the Core Console, and fall into three categories:
•
Tasks. A task is a job that the Rapid Recovery Core must perform, such as transferring data in a regularly scheduled backup, or
performing a restore from a recovery point.
Alerts. An alert is a priority notification related to a task or event, such as an error, warning, or important informational message.
Journal. The journal shows a complete list of all logged events. This list is more comprehensive than the set included in alerts.
•
•
You can view events that pertain to the Core by clicking
(Events) from the icon bar.
If you first navigate to a protected or replicated machine, and then select Events from the menu at the top of the page, you can view
events for the specified machine.
Regardless of whether you are viewing events for the Core for a specified machine, the default view for events is the Tasks page. By
clicking the drop-down menu to the right of the page title, you can select another view of events.
For example, if viewing tasks, click
(the downward-facing arrow immediately to the right of the Tasks title). A drop-down menu
appears. From the menu, select Tasks, Alerts, or Journal. From any view you can select the other events options.
8
Dell Data Protection | Rapid Recovery 6.1
•
From the top left of the current event view, click the drop-down arrow next to the page title and select another view. For example, if
viewing tasks, click
(the downward-facing arrow immediately to the right of the Tasks title). A drop-down menu appears, from
which you can select Tasks, Alerts, or Journal.
•
and from the drop-down menu, select Tasks.
•
(the downward-facing arrow) to the right of the Tasks title). A
To switch from a view of tasks to the alerts or journal view, click
drop-down menu appears, and from the drop-down menu, select Tasks.
•
Alerts. An alert is a priority notification related to a task or event, such as an error, warning, or important informational message.
•
Journal. The journal shows a complete list of all logged events. This list is more comprehensive than the set included in alerts.
To switch from Tasks to Alerts, click
Tasks.
(the downward-facing arrow to the right of the Tasks title), and from the drop-down menu, select
For either and you can view events for a specific protected or replicated machine.As in previous releases, you can view system events that
have been logged for the Core or for specific protected replicated machines from the Core Console. As of this release, the method to
choose between these types of events has changed.
When you click Events from the icon bar, the default view for events is the Tasks page.
Reporting enhancements
New to Rapid Recovery release 6.1 is the Job Summary report. This enhancement to existing reporting for Rapid Recovery is available
when reporting from the Core perspective only; this report is not available from reports for a protected machine. This report has a single
summary, showing summary information about all jobs performed on the Core, including a count of failed, passed, and canceled jobs. This
report differs from the Job report in key respects. The job report shows details for each job, such as start and end time, job duration,
result, data processed, and so on. The new Job Summary report lists each job as a separate line in the report. It contains summary
information about each type of job, such as its success statistics, the number of successes and failures, and so on.
Report parameters for this report type include date range, protected machines, and job types.
In this release, the Job Summary report is available both from the Rapid Recovery Core Console and from the Rapid Recovery Central
Management Console.
For information on how to generate a Job Summary report, see the Dell Data Protection | Rapid Recovery User Guide topics Generating a
report from the Core Console and (for multiple Cores) Generating a report from the Central Management Console.
New SQL Server version supported
Rapid Recovery now offers support for SQL Server 2016. It has been tested with release 6.1 of Rapid Recovery and verified to be
compatible with the software.
For information about a newly deprecated version of SQL Server, see SQL Server version deprecated.
Windows operating system support changes
Windows Server® 2016 is now supported. It has been tested with release 6.1 of Rapid Recovery and verified to be compatible with the
software.
As of Rapid Recovery release 6.0.x, the following Microsoft operating systems have recently reached end-of-life (EOL) and are no longer
supported by Dell:
•
Windows Server® 2003 extended support ended on July 14, 2015.
Dell Data Protection | Rapid Recovery 6.1
9
Windows XP® extended support ended on April 8, 2014.
•
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:
•
Virtual exports of Windows 10 protected machines to Oracle® VirtualBox are missing SCSI controller drivers.
•
The Rapid Recovery Add-on for the Kaseya® Management Console is not currently supported on Windows 10 machines.
Detailed information is now available about the operating systems supported by Rapid Recovery. See the following resources:
•
Rapid Recovery release 6.1 operating system installation and compatibility matrix
•
Rapid Recovery Core and Central Management Console requirements
•
Rapid Recovery Agent software requirements
Linux operating system support changes
The following new Linux versions are now available:
•
Red Hat Enterprise Linux (RHEL) 6.8 was released on May 10, 2016.
•
Oracle Linux was released on May 20, 2016.
•
CentOS Linux was released on May 25, 2016.
No major changes occurred to the kernels. These versions of Linux have been tested and are supported for Rapid Recovery Agent release
6.1.
Enhanced protection schedules
When creating a protection schedule, you can define protection once daily by selecting Daily protection time and specifying the time for
the snapshot. Alternatively, you can select how often to protect your machines on weekdays, and select a different interval for weekends.
Using the advanced mode, you can also define additional intervals for protection.
You can toggle between the two modes from the Protection Schedule dialog box.
For more information on setting protection schedules, see the Dell Data Protection | Rapid Recovery User Guide topics "Creating a
custom protection schedule from a wizard in Simple Mode," or "Creating multiple protection schedule periods in Advanced Mode,"
respectively.
Ability to bulk cancel running tasks
New in Rapid Recovery release 6.1 is the ability to cancel multiple running jobs at one time.
On the Tasks version of the Events page, each job now includes a selectable checkbox. When multiple background jobs are running on the
Rapid Recovery Core, you can now select more than one task on the Events page, and then click Cancel to stop their progress.
Instances when you may want to cancel multiple tasks include troubleshooting and performing manual upgrades.
The ability to cancel multiple running jobs at once also exists from the button bar of the Core Console, under Running Tasks.
10
Dell Data Protection | Rapid Recovery 6.1
Command Line Interface and PowerShell Module command
enhancements
Rapid Recovery has added the following capabilities to the Command Line and PowerShell scripting utilities.
New Command Line command
In release 6.1, there is now the ability to add and delete replication.
To delete replication, list the Core and affected protected machine (using a comma to separate), and then specify whether the replication
operation is -incoming or -outgoing. For example, removing replication for a protected machine on a target core would use the following
command:
>cmdutil /deletereplication -incoming
New PowerShell Module cmdlet
Rapid Recovery has added the ability to create a boot CD using PowerShell.
The command uses New-Bootcd to create an ISO image and save it to a specified location. All possible parameters — including
parameters for IP address, mask, default gateway, DNS server, ISO file path, VNC port, VNC password, and driver path — are optional.
For example, the following command and parameters would create an ISO image for the protected machine with the IP address of
192.168.20.88 and save it to the D: drive of the local machine:
New-Bootcd -ip 192.168.20.88 -mask 255.255.255.0 -defaultgateway 192.168.20.2 -dnsserver
192.168.20.2 -isofilepath D:\Bootcd\newbcd.iso
Progress tracking
Whenever a user performs an action using the Command Line Utility or PowerShell Module, the progress of the percentage of the action
completed now displays in the interface. Progress tracking is available for the following commands:
•
•
•
•
•
•
•
•
•
•
•
Import archive
Force base image
Force incremental image
Force replication
Force rollup
Force attachability check
Force mountability check
Force checksum check
Force log truncation
Force export to VM
Create boot CD
Mailbox Restore for Exchange enhancements
Rapid Recovery has added the following improvements to release 6.1 Mailbox Restore. For more information about any of the
enhancements, see the Rapid Recovery Mailbox Restore for Exchange User Guide.
Dell Data Protection | Rapid Recovery 6.1
11
Hiding of system mailboxes and folders
Mailboxes and folders related to system operations are now hidden in Mailbox Restore by default. These locations do not contain
messages or items that do little more than clutter the navigation tree of locations that may be of more interest. The result is a cleaner and
more useful list of mailboxes and folders from which users can restore Exchange items. System mailboxes and folders can be shown by
selecting the appropriate option in the Mailbox Restore settings.
New saving formats
Mailbox Restore now offers the ability to save a message or other item as a .msg, .txt, or .eml file.
A .msg file is compatible with any mail program that uses Microsoft's Messaging Application Programming Interface (MAPI), including
Microsoft Outlook. A .txt file is a text file with no formatting that users can open with a program such as Notepad. An .eml file is in a
format that works with Outlook and Microsoft Internet Explorer.
Improved Properties windows
Previously, the Properties window for an Exchange item or folder displayed only general and MAPI properties. The properties are readonly, but the following changes have been made to make this window more interactive:
•
•
•
•
New tabs that let you view the recipient of a message and any attachments associated with that message.
The ability to view properties for an attachment.
The ability to right-click and save the message or attachment as a .msg, .txt, or .eml file.
The ability to view permissions for a selected folder.
Search enhancements
Several improvements were made to the search function in Mailbox Restore. These improvements include the ability to pause a search,
search within search results, search among multiple item types at once, and edit a search.
Previously, there was an ability to stop a search in progress; however, the search could only be restarted from the beginning. The pause
function lets users temporarily stop a search in progress and then resume the search where it left off, without losing any progress.
In the Advanced Search window, there is now the ability to select more than one item type as search criteria. Also, a new option lets users
edit search criteria by clicking Update, which replaces the criteria with the change rather than adding to the existing entry. In a previous
search, there is also the option to "search in already found messages," which narrows the search field to pre-existing results and delivers
faster and more accurate searches.
Exchange 2016 support
Rapid Recovery Mailbox Restore for Exchange now offers support for Exchange Server 2016. It has been tested with release 6.1 of Rapid
Recovery and Mailbox Restore and is verified to be compatible with both products.
Deprecated in this release
The following is a list of features, items, or related components that are no longer supported starting with Rapid Recovery release 6.1.
Related links
New features
Enhancements
12
Dell Data Protection | Rapid Recovery 6.1
SQL Server version deprecated
Microsoft ended extended support for SQL Server 2005 on April 12, 2016, based on their support lifecycle policy. Thus, Dell no longer
intends to test SQL Server 2005 when performing compatibility, system, SQL attachability, and other tests.
Customers are advised that continued use of SQL Server 2005 with Rapid Recovery is at their own risk. Standard support agreements do
not address questions or issues customers have with SQL Server 2005.
For information about the new version of SQL Server Rapid Recovery supports, see New SQL Server version supported.
Hypervisor hosts deprecated
Rapid Recovery no longer supports VMware vSphere on ESX 4.0 and 4.1 as a hypervisor host, since ESX has reached end of life and is no
longer supported by VMware.
ESXi 5.0 and 5.1 reached end of life on August 24, 2016. These versions of ESXi were tested and function properly in Rapid Recovery
release 6.1. However, future major releases of our software are not expected to support ESXi 5.0 and 5.1. Prepare any migration
accordingly.
Resolved issues
Issues resolved in this release are listed below.
Table 1. Central Management Console resolved issues
Resolved issue
Issue ID
Functional area
If a network error occurred at a specific phase of replicating a recovery point, the file version
may have been simultaneously deleted and created, causing a recovery point without
recoverable data.
35603
Replication
Downloading or reviewing reports failed for users with a large number of events due to no
ability to change the ClientTimeoutSettings in the registry.
35532
Reports
There was an inability to download more than 10 reports from the Rapid Recovery Central
Management Console.
35319
Reports
There was an inability to generate a report for more than 10 Cores simultaneously from the
Rapid Recovery Central Management Console due to an overly long URL string.
34674
Reports
Adding access for a domain user or group failed in a specific environment with a timeout error.
34280
Central Management
Console
There was an inability to create new users or groups in Central Management Console if using
old Windows account management algorithm, resulting in error: 'Object reference not set to an
instance of an object.'
33831
Central Management
Console
There was an inability to add a user or group to the Central Management Console with a
domain controller.
33600
Central Management
Console
Error: "Sequence contains no elements" appeared when adding a domain user or group to
access in the Central Management Console.
33459
Central Management
Console
Impossible to repair or remove Rapid Recovery Agent or Central Management Console from
Control Panel "Programs and Features" after uninstalling Core.
30747
Installer
Dell Data Protection | Rapid Recovery 6.1
13
Table 2. Core and Windows resolved issues
Resolved issue
Issue ID
Functional area
Some jobs were missing from the Events page when there were many jobs and if all filters were 35593
off.
Events
Incorrect hypervisor status appeared on Virtual Standby page of appliance.
35466
Virtual Standby
The seed drive job for one target Core blocked the replication job for all target Cores that
replicate the same machines.
35437
Replication
Hyper-V export failed in a specific environment with errors: "disk1.vhd is being used by another
process" and "the operation with VHD virtual disk failed --->
System.UnauthorizedAccessException: Access to the path disk1.vhd is denied."
35404
Hyper-V export
When managing groups of agentlessly protected machines in the Core Console, actions allowing 35266
user to force snapshot, pause protection, and refresh metadata did not appear.
Agentless protection
Incorrect size of repository files on specific environments was causing rollup failures.
35261
Repository
When two or more exports started simultaneously, the Core crashed at the beginning of the
export with an "AccessViolationException" or "0xc0000374" exception.
35159
VM export
Mounting an archive failed if the archive contained recovery points for cloned VMs.
34946
Mounting archives
Connection to the License Portal failed with timeout error on specific environment because
timeout settings specified in Core.Service.exe.config were ignored.
34929
Connection
Lengthy archive to Azure job in a specific case indicated cancelation when logs reveal the job
actually failed.
34918
Archive
After deleting one of multiple repositories, a failed OnRecoveryPointDeleted event subscription
resulted in orphaned recovery points.
34849
Repository
Erroneously, the CSV format was available for exporting a scheduled Summary report for the
Core.
34843
Reporting
Could not export a VM to VSAN.
34762
VM export
When running Virtual Standby for a small number of protected machines, the postprocessing
step of an export took longer than it should have on Windows Server 2012 R2.
34725
Virtual Standby
In a Core Job report, after performing a CSV export of the report, the delimiter appeared as a
semicolon instead of a comma.
34724
Reporting
After viewing events specific to one protected machine, those events persisted in the Events
page when you changed the view to another protected machine.
34615
Events
There was no ability to create a seed drive larger than 2TB.
34586
Archive
When Agent software was installed on a DAG SCC cluster and protected as a simple protected
machine, recovery points were disabled for virtual export in specific cases.
34577
VM export
Local timestamp is incorrect for email notifications.
34467
Email notifications
Selected alerts for email notification enabled only for one protected machine were sent to all
protected machines.
34442
Alerts
Alert records were different in Home and Events pages.
34441
Alerts
Sometimes nightly integrity check jobs failed with error: "System.IO.IOException depth 0: The
parameter is incorrect on specific environment."
34414
Nightly jobs
Uninformative error message was shown when attempting to create a second repository on a
shared server.
34428
Repository
Unable to create archive to Amazon s3 cloud to bucket in EU1 (Frankfurt) region.
34331
Archive
When performing Virtual Standby to an ESX virtual machine, exports sometimes failed with the
error, "Vddk Handle is invalid."
34301
Virtual Standby
14
Dell Data Protection | Rapid Recovery 6.1
Resolved issue
Issue ID
Functional area
When deploying an upgrade of the Agent installation software with a custom port specified, the 34271
port changed to the default port 8006, causing deploy failures.
Upgrading
The index file in the repository did not shrink after the volume for the protected machine
shrank.
34227
Repository
Due to the absence of vmguest.iso file in Windows 10 builds, Hyper-V export to Windows 10
failed with error message: "The operation with VHD virtual disk failed. The operation could not
be completed because no available locations were found on the disk controller."
34188
Hyper-V export
The nightly rollup job started simultaneously for all protected machines when it should have
performed the rollup job for each machine separately.
34173
Rollup
Agentless protected vCenter with two ESXi hosts could not auto-protect copied VM.
34158
Agentless protection
If a replicated recovery point contained a volume that shrank when the base image was
created, corruption appeared on the target Core.
34156
Replication
Created a unique description for filter drive 'aavolflt' which incorrectly matched the description
of other drivers.
34112
Drivers
If the protected machine has "Shadow Copy Schedule" enabled for one or more volumes, and
its protection schedule overlaps with the protection schedule on the Core, then sometimes a
base image is taken instead of an incremental image.
34065
Protection
The password for a protected machine was not encrypted in output of the API if Core and
Agent were upgraded from release 5.4.3.
33960
Upgrading
Recovery points of volume with a non-default size not divisible by 8192 were not mounted from 33855
attached archive.
Archive
There was no ability to set up scheduled Summary reports for replicated machines.
33844
Reporting
The PowerShell Get-RecoveryPoints cmdlet failed with a timeout error.
33843
PowerShell
After a replication job, protected and replicated machine notification settings were
synchronized.
33763
Replication
Recovery points of full 2TB volume are not mounted from attached archive.
33729
Archive
EFI partition did not appear on the Agent summary page of the Core Console for a specific
environment.
33642
Agent summary
The restricted GET method length prevented users from performing a Get API request.
33563
REST API
Machines with a specific PCIe application accelerator flash drive (SanDisk Fusion ioMemory™
SX350) could not be protected; the following serialization exception error appeared:
"Replay.ServiceHost.Implementation.Hosting.ServiceHost ... Service Host Error: Service error
while handling request...: Enum value '2046' is invalid for type
'Replay.Common.Contracts.Metadata.Storage.StorageBusType' and cannot be serialized."
33532
Protection
When using agentless protection, the hypervisor host incorrectly consumed a license on the
License Portal.
33525
Agentless protection
Unclear error message appeared if you performed a Hyper-V virtual export to a node for which
the cluster service was stopped.
33511
Hyper-V export
Incremental archive creation failed with the error "Out of space on the target" in a specific case 33473
due to an incorrect space validation.
Archive
For very large databases performing a mountability check job, cancel actions were ignored and
job sometimes hung.
33462
Mountability check
Sometimes virtual exports hung for virtual standby jobs during postprocessing.
33460
Virtual Standby
After expanding seed drive properties for outgoing replication in the Core Console, incorrect
timestamp appeared in Earliest and Latest Recovery Points on Outgoing Replication tab.
33444
Replication
Core system events logs were spammed by 'DCOM' error if cluster was protected.
33434
Events log
Dell Data Protection | Rapid Recovery 6.1
15
Resolved issue
Issue ID
Functional area
In some cases, if replication failed due to a temporary connection problem, automatic retries
were not performed. There should be 2 attempted retries before a replication job terminates.
33423
Replication
Duplicated e-mail messages were sent by the Core when there was more than one notification
group with email settings enabled.
33421
Email notifications
Archive certificates validation on both Cores and protected machines were not removed from
the archive check job, although certificates are not used when importing an archive.
33354
Archive
After leaving the Events page opened for some time, items listed in the Events grid stopped
updating in Chrome browser.
33345
Events
In the archive wizards, the reason for selecting the option to build recovery point chains (fix
orphans) was unclear.
33342
Archive
Rarely, on very busy systems, virtual standby export failed to start with incorrect RPFS file size
error.
33308
Virtual Standby
Error: "Sequence contains no matching element" repeatedly appeared in the Core log during
mountability check.
33301
Mountability check
Sometimes export for Agentless failed with "Object reference" error on post-processing step.
33291
Agentless protection
There was no ability to open the Settings page on an Windows Enterprise environment.
33273
GUI
Incorrect failure reason displayed in UI if job failed with specific errors.
33242
Logging
In the Deploy Machines wizard, if the Core had been upgraded from AppAssure 5.x to Rapid
33239
Recovery 6.x, a protected cluster from the local Core could not connect due to the error "Value
cannot be null...."
Deploying
There was no ability to disable SNMP and then configure Community type.
33185
SNMP support
There was no ability to perform Hyper-V export for more than 2 TB disks with VHDx disk
format if you selected one-time export.
33180
Hyper-V export
MongoDB service was configured to use an insecure REST interface.
33171
Mongo
There was no validation process when configuring a retention policy using the API.
33168
REST API
Heartbeat failed with error "Unable to contact licensing server" with authentication problem
(such as AD or LDAP outage, incorrect credentials, or corrupt Exchange installation).
33151
Licensing
Agentless protection of machines with virtual RDMs did not work. The protected machine failed 33039
to protect, or showed no disk information.
Agentless protection
Replication failed with uninformative error message when the source Core did not receive a
proper response from the target (often caused by networking issues between the Cores).
32995
Replication
It was possible to start a VMware ESXi virtual export for a hard disk drive with 4096 bytes per
sector. VMware only supports disks with 512 bytes per sector.
32972
ESXi export
Windows System State backup did not work properly when Rapid Recovery Agent was installed 32967
on the machine.
Software conflict
RecoveryPointsInfo and MasterCoreInfo properties were removed from the Get32954
ReplicatedServers PowerShell cmdlet. This change to the cmdlet was intentional. Please update
scripts to work without these properties.
PowerShellModule
If one of the ESXi hosts added to vCenter was offline, ESXi export failed for all agents with
error "FormatException...."
32897
ESXi export
After upgrading from AppAssure 5.4.3 to Rapid Recovery 6.0 with notifications already
configured, sometimes notifications did not work properly.
32879
Backward compatibility
After an upgrade from AppAssure 5.4.3, the error: "Object reference not set to an instance of
an object" appeared on the Boot CDs tab if boot CDs were created prior to upgrade.
32878
Backward compatibility
Migration steps did not start during a clean install of Rapid Recovery if a previous HKLM/
Software/AppRecovery registry branch was present.
32863
Installer
16
Dell Data Protection | Rapid Recovery 6.1
Resolved issue
Issue ID
Functional area
Checkboxes for all previously selected alerts did not display when the 'Edit Notification Group'
window is opened in Internet Explorer.
32797
Events
Archive creation process behaved incorrectly if the previous archive attempt was interrupted
and the "erase completely" recycle action was selected.
32780
Archive
In rare cases, PreHyperVAgentScript did not run on the Hyper-V host during VM export. See
Microsoft KB https://support.microsoft.com/en-us/kb/2779204 for details.
32712
Hyper-V export
There was no ability to clear the option "Truncate SQL/Exchange logs" on the Nightly jobs
panel.
32307
Nightly jobs
Replication failed with error: "Unable to read data contract from stream due to incorrect RPFS
file size" if metadata for a recovery point or volume image was not written successfully due to
environmental issues such as low memory or full repository.
32226
Transfers
On some large environments, the Summary report failed with the error "Unexpected server
response (500)."
31909
Reporting
ESXi/VirtualBox virtual export failed for Windows-based agentless VM on specific environment. 31831
ESXi/VirtualBox export
In rare cases, most commonly caused by environmental issues on an Exchange agent, the
mountability queue broke the order of the Virtual Standby export queue, causing a full export
(instead of an incremental).
31803
Jobs
If users of ESXi Agentless protection performed virtual export of BusLogic Parallel controllerbased machines to ESXi and VMware, the exported machines were not bootable.
31775
VM Export
There was no link to "fix path" on a repository that had been opened using the "open existing
repository" option.
31473
GUI
There was no ability to change Snapshot Cleaning Timeout on the Settings page for a
protected machine.
31460
GUI
The error "Failed Services ScheduleBackupService: Ambiguous choice between types in
application domain: preferred assembly does not contian type with such name while two or
more others do. Type name: Replay.Core.Contracts.Backup.ScheduledArchiveCollection"
appears after an upgrade from AppAssure 5.4.3 to Rapid Recovery 6.0.1.
31310
Archive
There was incorrect export validation during Hyper-V export on Cluster-Shared Volumes.
31051
Hyper-V export
In the Universal Recovery Console (URC), when restoring from an archive, the progress ball for 30996
the successfully restored volume was at 0%.
URC
Sometimes new volumes were not taken under protection automatically after metadata
refreshed using agentless ESXi auto protection.
30968
VMware agentless
Mountability check failed with error: "Mandatory database was not found" if more than two
Exchange 2013 databases were located on the same mounted volume.
30818
Mountability check
It was impossible to repair or remove Rapid Recovery Agent or Central Management Console
from Control Panel "Programs and Features" after uninstalling Core.
30747
Installer
Server error "Object '/...rem' has been disconnected or does not exist at the server" appeared
when opening Core or protected machine settings.
30629
Core
Uninformative error: "Object reference not set to an instance of an object" appeared for virtual
export if the destination volume was missing.
30477
Virtual export
Boot CD started with random IP even if user specified a particular IP during creation of the
Boot CD image.
30365
URC
Volume letters were not assigned during BMR for GPT partitions.
30319
URC
Functionality for archives has changed to allow recovery points to be archived without a full
recovery point chain. The default behavior is to select the "Build recovery points chains (fix
orphans)" option in the Options page of the Archive Wizard.
30297
Repository
Dell Data Protection | Rapid Recovery 6.1
17
Resolved issue
Issue ID
Functional area
When running "Maintaining repository" job on a DVM repository, logic previously allowed
records over the maximum record allotment.
29918
Repository
Core hung during generation of HTML report for Core with greater than 300,000 event
records.
29788
Reporting
In some cases, when a Core contained more than 300,000 event records, reports failed to
generate with error "Failed to generate report file."
29786
Reporting
On specific environments, Deferred Delete jobs were slowed down when a DVM flush action
was called too frequently.
29420
DVM
PDF and HTML reports did not export for a Core with more than 300,000 event records.
29265
Reporting
Nightly recovery points integrity check was not performed for some protected machines if one
or more had no volumes protected.
28741
Nightly job
Replication stayed paused after completing "Copy to seed drive" job if the same job was
previously interrupted.
27749
Replication
Error: "DvmBadRecord" appeared if an agent volume was extended during a backup.
26579
Repository
In rare cases (when hundreds of SQL databases exist on a volume), SQL Writer status changed 22155
from stable to failed "nonretryable" state when Rapid Recovery took a snapshot.
Core
Table 3. DocRetriever for SharePoint resolved issues
Resolved issue
Issue ID
Functional area
When using DocRetreiver Console to restore SharePoint calendar items, the Resources field
was not restored.
32966
Restoring
This defect addressed the inability of DocRetriever Console to open a singular site collection
backup in SharePoint 2013. The defect has been closed and the item is tracked as a pending
feature request.
17238
DR
Resolved issue
Issue ID
Functional area
Rapidrecovery-vss module installation failed with the error: "Your kernel headers for kernel
3.10.0-327.28.3.el7.x86_64 cannot be found …".
35550
Installer
If Security-Enabled Linux (SELinux) was enabled, a kernel panic (KP) appeared upon reboot
after the Agent was installed.
35548
Linux
An out-dated kernel prevented the default CentOS 7 instance from installing on a network
block device (NBD).
34913
Linux
Product documentation: The procedure "Installing the Agent software on off-line Linux
machines" in the Installation and Upgrade Guide versions 6.0.1 and 6.0.2 contained incorrect
information about where to obtain the downloader script. The topic is updated in the release
6.1.0 document.
33628
Linux
Product documentation: Update installation commands for SLES to use Zypper. Two
commands shown in the Installation and Upgrade Guide for installing Rapid Recovery Agent
software on SUSE Linux Enterprise Server (SLES) were incorrect. SLES uses the Zypper
package manager, but the commands shown for steps 5 and 6 are apt commands.
33583
Linux
Transfers failed when a protected Linux machine with multipath enabled was connected to an
EqualLogic iSCSI target.
33528
Protection
Exporting failed for Linux protected machines that had more than one iSCSI session to iSCSI
target.
33527
Exporting
Table 4. Linux resolved issues
18
Dell Data Protection | Rapid Recovery 6.1
Resolved issue
Issue ID
Functional area
When installed on a Linux machine, the Agent software could not gather physical disk
information for an LVM volumes created in a multipath device.
33106
Installer
5.4 Linux Agent software installation failed when installing on non-English locales.
33042
Linux
In some cases, the controller type for a Linux protected machine was not detected, resulting in 32938
failure of virtual export with error: "System.InvalidOperationException: Sequence contains more
than one matching element."
Linux
Ubuntu x32 machine was not bootable after Hyper-V export.
31307
VMware agentless
Virtual Machine type was displayed as 'Physical' for Linux Agents installed on virtual machines
with SATA disks.
28583
Linux
RAM consumption grew during transfers of large amounts of data on SLES 11 x64.
27509
Linux
Known issue
Issue ID
Functional area
LMU hung if user tried to open "Active mounts" window or to mount recovery points
immediately after more than 5 recovery points were dismounted.
31707
Local Mount Utility
If you mounted more than 20 recovery points in LMU and then dismounted in LMU, dismounted 31706
recovery points were still displayed as Remote Mounts in the Core Console.
Local Mount Utility
There was no ability to specify domain credentials as default Core credentials in Local Mount
Utility.
34395
Local Mount Utility
Volume image failed to mount in Local Mount Utility after shrinking a virtual hard disk.
35063
Local Mount Utility
Known issue
Issue ID
Functional area
If there was an incorrect value stored in the database for the mailbox owner's unique mailbox
identifier, a restore action to the original location failed with error: "Could not open message
store."
33440
MR
Exchange 2016 databases were not supported; support is planned for release 6.1. In release
6.0x, Exchange 2016 databases were incorrectly identified as Exchange 2013 databases.
30924
MR
Table 5. Local Mount Utility resolved issues
Table 6. Mailbox Restore resolved issues
Known issues
The following is a list of 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
Issue ID
Functional area
Virtual export fails with the error "No physical extents have been found for cluster offset
'19626746' cluster length '520.' Extent disk #'1' LCL '19627264' LCF '0' PSF '264192'" after
specific steps.
Workaround: Take a new base image, and then attempt the export again.
35626
VM export
There is incorrect validation for the "Maximum connection pooling size" and "Minimum
connection pooling size" fields for the connection to MongoDB.
35607
GUI
Dell Data Protection | Rapid Recovery 6.1
19
Known issue
Issue ID
Functional area
35572
GUI
Workaround: Since validation on these fields is not functioning, take care to specify the correct
values for the "Maximum connection pooling size" and "Minimum connection pooling size"
fields.
In the Settings page of the Core Console, validation in the client timeout fields sometimes work
incorrectly, showing the error "Uncaught Error."
Workaround: Refresh the page.
In the Korean translation of the user interface, the Pause button has the incorrect translation of 35557
일지 중지.
Workaround: The Korean translation of the Pause button should read as 일시 중지.
Localization
On the Schedule page of the Archive wizard, the tooltip text is wrong in all translations.
Workaround: This is a cosmetic issue that does not require a workaround.
35556
Localization
In the Protect Machine wizards, the "Encrypt data using Core-based encryption with an
existing key" option is highlighted when it is not selected.
Workaround: This is a cosmetic issue that does not require a workaround.
35554
GUI
Volumes are not available after a recovery point from an attached archive created from an
agentless Windows Server 2008 R2 protected machine is mounted as Writable.
Workaround: Import the archive to the repository, and then mount the recovery point as
Writable.
35542
Agentless protection
The email notification template reverts to the default after the Core service restarts.
Workaround: Contact Support and request the custom binary that addresses this issue.
35483
GUI
Replication to a second target Core does not start if volumes are missing from the source Core. 35358
Workaround: On the Summary page for the affected protected machine, remove the missing
volume from protection.
Replication
On a specific environment, the GPT volume on an agentlessly protected virtual machine cannot 35100
be opened from a mount point mounted in Read-only mode.
Workaround: Create another mount type, or mount the volume using the Local Mount Utility
on a machine running Windows Server 2012.
Agentless protection
A base image is taken whenever the NTFS Boot Sector is changed.
Workaround: Contact Support and request the custom binary that addresses this issue.
Filter driver
34981
Unexpected base images are generated for the ESXi virtual machines that have snapshots with 34916
quiescing enabled.
Workaround: Disable quiescing.
Transfers
When viewing the Core Console in the Dashboard view in languages other than English, the
word "Transfer" is not translated when searching for all transfer events using the Transfer Job
per Machine widget.
Workaround: This is a cosmetic issue that does not require a workaround.
34774
Localization
Export rate is slow for recovery points from repositories that have high fragmentation.
Workaround: Option 1: Pause machine protection, archive all recovery points for that machine,
remove the repository, create a new repository, assign the protected machine to the new
repository, import the archive to the new repository, and then resume protection.
34758
Repository
Option 2: Contact Support and request the custom binary that addresses this issue.
20
Dell Data Protection | Rapid Recovery 6.1
Known issue
Issue ID
Functional area
Performance on the Virtual Standby page is slow when there are several export jobs in the
queue or in progress.
Workaround: Decrease the number of concurrent export jobs allowed.
34434
Performance
On the Events page and the Delete Recovery Points Range window, the date and time pickers
work incorrectly.
Workaround: Refresh the page.
34347
GUI
Information about allocated space for some volumes is unavailable. A warning message appears 33551
on the Summary page for a protected machine if it is a virtual machine located on an NFS
datastore.
Workaround: There is no workaround at this time. There are issues with gathering metadata on
the NFS.
GUI
There is no ability to inject drivers from the Rapid Recovery Universal Recovery Console (URC)
after restoring data for older operating systems (such as Windows Server 2003, Windows
Server 2008, Windows Vista) to a successfully boot-restored machine.
Workaround: Restore on hardware with included driver support. Use x86 boot CD from
5.4.3.106 build. Install the OS, install the Rapid Recovery Agent software, then restore the
volumes.
33359
URC
Replication rate becomes extremely slow if you start a virtual export job while replication job is
running.
Workaround: Configure jobs so they do not run in parallel.
33230
Replication
Disk metadata size skews progress tracking during archive. For example, if there are many
databases on a volume, the progress bar stays at 1% for too long, then speeds up.
Workaround: There is no workaround at this time.
32044
Archive
When the target network storage volume runs out of space, if more than one archive job is in
progress, then all running archive jobs fail with error: "There is not enough space on the disk."
Workaround: Create different schedules for running each archive so that the archives do not
run simultaneously in the network share.
31827
Archive
WinXPx86 machine is not bootable after virtual export. Issue relates to controller drivers for
SCSI and IDE controllers not present in the exported VM.
Workaround: There is no workaround at this time.
31705
VM export
ESXi agentless restore or virtual export using SAN transport mode fails with the error, "One of
the parameters was invalid."
Workaround: Use Network Transport mode for rollback.
29508
VMware agentless
ESXi virtual export with auto disk mapping fails with unclear error.
27309
ESXi export
Known issue
Issue ID
Functional area
The error "Cannot find the original destination..." appears after trying to perform an in-place
restore of a site from the "Farm" backup.
35614
Restoring
An error message for ESXi virtual export with auto disk mapping does not clearly describe the
issue.
Workaround: Use manual disk mapping.
Table 8. DocRetriever known issues
Dell Data Protection | Rapid Recovery 6.1
21
Known issue
Issue ID
Functional area
Known issue
Issue ID
Functional area
An exported Linux machine with an EFI partition is not bootable on VMware ESXi, because
specific volumes are not mounted after the export of the Linux machine.
Workaround: There is no workaround at this time.
35288
ESXi export
Users who have 'safenet' encrypted file partitions are unable to protect Linux machines using
the Rapid Recovery Agent.
Workaround: Contact Support and request the custom binary that addresses this issue.
35226
Protection
Workaround: Perform an out-of-place restore and manually specify the appropriate restore
location.
Table 9. Linux protection known issues
Red Hat® Enterprise Linux® (RHEL) protected machine is not bootable after VirtualBox export 31277
of ESXi Agentless machine.
Workaround: There is no workaround at this time.
VirtualBox export
Agentless protected ESX Ubuntu machine is not bootable after BMR.
Workaround: Use the Rapid Recovery Agent on Ubuntu instead of using agentless protection.
VMware agentless
31206
Rapid Recovery system requirements
This section describes the system and license requirements for installing the Rapid Recovery Core, Rapid Recovery Agent, and Rapid
Recovery Central Management Console.
Recommended network infrastructure
For running Rapid Recovery, Dell requires a minimum network infrastructure of 1 gigabit Ethernet (GbE) for efficient performance. Dell
recommends 10GbE networks for robust environments. 10GbE networks are also recommended when protecting servers featuring large
volumes (5TB or higher).
If multiple network interface cards (NICs) are available on the Core machine that support NIC teaming (grouping several physical NICs into
a single logical NIC), and if the switches on the network allow it, then using NIC teaming on the Core may provide extra performance. In
such cases, teaming up spare network cards that support NIC teaming on any protected machines, when possible, may also increase
overall performance.
If the core uses iSCSI or Network Attached Storage (NAS), Dell recommends using separate NIC cards for storage and network traffic,
respectively.
Use network cables with the appropriate rating to obtain the expected bandwidth. Dell recommends testing your network performance
regularly and adjusting your hardware accordingly.
These suggestions are based on typical networking needs of a network infrastructure to support all business operations, in addition to the
backup, replication, and recovery capabilities Rapid Recovery provides.
UEFI and ReFS support
Unified Extensible Firmware Interface (UEFI) is a replacement for Basic Input/Output System (BIOS). UEFI is used in the Windows 8,
Windows 8.1, Windows 10, Windows Server® 2012, Windows Server 2012 R2, and Windows Server 2016 operating systems. For Windows
22
Dell Data Protection | Rapid Recovery 6.1
systems, UEFI uses the Extensible Firmware Interface (EFI) system partitions that are handled as simple FAT32 volumes. Protection and
recovery capabilities are available in Rapid Recovery for EFI system partitions.
Rapid Recovery also supports the protection and recovery of Resilient File System (ReFS) volumes for Windows Server 2012, 2012 R2,
and Windows Server 2016.
Rapid Recovery also supports UEFI for protected machines with the Linux® distributions we support. These include Red Hat® Enterprise
Linux® (RHEL®), CentOS™, Debian ®, Ubuntu®, SUSE® Enterprise Linux (SLES®), and Oracle® Linux.
Support for dynamic and basic volumes
Rapid Recovery supports taking snapshots of all dynamic and basic volumes. Rapid Recovery also supports exporting simple dynamic
volumes that are on a single physical disk. As their name implies, simple dynamic volumes are not striped, mirrored, spanned, or RAID
volumes.
The behavior for virtual export of dynamic disks differs, based on whether the volume you want to export is protected by the Rapid
Recovery Agent software, or is a VM using agentless protection. This is because non-simple or complex dynamic volumes have arbitrary
disk geometries that cannot be fully interpreted by the Rapid Recovery Agent.
When you try to export a complex dynamic disk from a machine with the Rapid Recovery Agent software, a notification appears in the
user interface to alert you that exports are limited and restricted to simple dynamic volumes. If you attempt to export anything other than
a simple dynamic volume with the Rapid Recovery Agent, the export job fails.
In contrast, dynamic volumes for VMs you protect agentlessly are supported for protection, virtual export, restoring data, and BMR, and
for repository storage, with some important restrictions. For example:
•
•
Protection: In the case when a dynamic volume spans multiple disks, you must protect those disks together to maintain the integrity of
the volume.
Virtual export: You can export complex dynamic volumes such as striped, mirrored, spanned, or RAID volumes from an ESXi or HyperV host using agentless protection.
However, the volumes are exported at the disk level, with no volume parsing. For example, if exporting a dynamic volume spanned
across two disks, the export will include two distinct disk volumes.
•
CAUTION: When exporting a dynamic volume that spans multiple disks, you must export the dynamic disks with the
original system volumes to preserve the disk types.
Restoring data: When restoring a dynamic volume that spans multiple disks, you must restore the dynamic disks with the original
system volumes to preserve the disk types. If you restore only one disk, you will break the disk configuration.
Repository storage: Additionally, Rapid Recovery supports the creation of repositories on complex dynamic volumes (striped, mirrored,
spanned, or RAID). The file system of the machine hosting the repository must be NTFS or ReFS.
Support for Cluster Shared Volumes
Rapid Recovery release 6.1 lets you protect, restore, replicate, and archive virtual machines hosted on cluster-shared volumes (CSVs)
running on Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016 with the Rapid Recovery Agent software.
For CSVs running on Windows Server 2008 R2, Rapid Recovery supports native backup. You can restore CSVs from a recovery point, or
perform virtual export to a Hyper-V CSV. There is no support for cluster-shared volumes running on earlier Windows operating systems,
such as Windows 2008.
Rapid Recovery does not support virtual export of a cluster-shared volume protected using Rapid Recovery Agent.
In contrast, in Rapid Recovery release 6.1, you can perform virtual export to a Hyper-V CSV running Windows Server 2012, Windows
Server 2012 R2, or Windows Server 2016.
Dell Data Protection | Rapid Recovery 6.1
23
For other operating systems, the Rapid Recovery Agent service can be run on all nodes in a cluster, and the cluster can be protected as a
cluster within the Rapid Recovery Core. However, CSVs do not display in the Core Console and are not available for protection. All local
disks (such as the operating system volume) are available for protection.
The following table depicts current support in Rapid Recovery Core for cluster-shared volumes protected with Rapid Recovery Agent.
Table 10. Rapid Recovery support for cluster-shared volumes on machines protected with Rapid Recovery Agent
1
Rapid Recovery Cluster Shared Protect, Replicate, Rollup,
Volumes Support
Mount, and Archive
Restore CSV Volumes
Virtual Export to
Hyper-V CSV
Rapid Recovery version
6.0.x
6.1
6.0.x
6.1
6.0.x
6.1
Windows Server 2008 R2
Yes
Yes
Yes
Yes
Yes
Yes
Windows Server 2012
No
No
No
No
Yes
Yes
Windows Server 2012 R2
No
No
No
No
Yes
Yes
Windows Server 2016
No
No
No
No
No 1
Yes
Windows Server 2016 was not tested on Rapid Recovery release 6.0.x and is therefore not supported.
If using Hyper-V host-based protection, Rapid Recovery release 6.1 supports protection of VMs on Hyper-V cluster-shared volumes
running Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016. The VMs themselves are protected, not the volumes.
Table 11. Support for cluster-shared volumes using host-based protection on Hyper-V
Windows Server 2012
Windows Server 2012
R2
Windows Server 2016
Protect, Replicate, Rollup, Mount, and Archive VMs
on CSV
No 1
Yes
Yes
Restore VMs hosted on CSV
No 1
Yes
Yes
Virtual Export from
Hyper-V CSV
No
1
Yes
Yes
Virtual Export to
Hyper-V CSV
No 1
Yes
Yes
1 Windows Server 2012 is not supported in this scenario. Full support (and future functionality) for CSVs using Hyper-V host-based
protection is planned primarily for Windows Server 2012 R2 and later operating systems.
Hypervisor support in Rapid Recovery
In general, Rapid Recovery protects virtual machine guests hosted on a hypervisor (such as KVM or XenServer) using the Rapid Recovery
Agent software.
Each protected machine hosted on a hypervisor must meet or exceed documented system requirements. See Rapid Recovery Agent
software requirements for OS, architecture, memory, processor, server application, storage, network, and network hardware
requirements.
Individual hypervisors may also restrict support to specific operating systems. See appropriate documentation for each relevant hypervisor.
For successful use of Rapid Recovery, the overarching requirement is that Cores are properly sized, and have sufficient resources and
infrastructure to support backup, replication, and other features you need. These resources are in addition to any requirements for the
24
Dell Data Protection | Rapid Recovery 6.1
original purpose of the machines. For guidance for sizing your hardware, software, memory, storage, network, and network hardware, see
knowledge base article 185962, “Sizing Rapid Recovery Deployments.”
Agentless support for hypervisors in Rapid Recovery release 6.0.2 is limited to VMware/ESXi. Guest machines must meet other
requirements such as installation of VMware Tools. Rapid Recovery release 6.1 agentless support includes host-based support for Hyper-V,
in which the Agent software is required only on the host. For more information about agentless support, see Rapid Snap for Virtual
agentless protection.
Virtual export is supported only for VMware/ESXI, Hyper-V, and VirtualBox hypervisors and on the Azure platform.
Virtual export hypervisor license requirements
Rapid Recovery Core supports virtual export to a variety of hypervisor platforms. When exporting to ESXi, Hyper-V, or VMware
Workstation, you must use the full licensed versions of those hypervisors, not free versions.
Rapid Recovery Core installation requirements
Install the Rapid Recovery Core on a dedicated Windows 64-bit server. Servers should not have any other applications, roles, or features
installed that are not related to Rapid Recovery. As an example, do not use the Core machine to also serve as a hypervisor host (unless the
server is an appropriately sized Dell DL series backup and recovery appliance).
As another example, do not use the Core server as a high-traffic web server. If possible, do not install and run Microsoft Exchange Server,
SQL Server®, or Microsoft SharePoint® on the Core machine. If SQL Server is required on the Core machine – for example, if you are
using Dell Data Protection | Rapid Recovery DocRetriever for SharePoint – make sure you allocate more resources, in addition to those
needed for efficient Core operations.
Depending on your license and your environment requirements, you may need to install multiple Cores, each on a dedicated server.
Optionally, for remote management of multiple Cores, you can install the Rapid Recovery Central Management Console on a 64-bit
Windows computer.
For each machine you want to protect in a Rapid Recovery Core, install the Rapid Recovery Agent software version appropriate to that
machine's operating system. Optionally, you can protect virtual machines on a VMware ESXi host without installing the Rapid Recovery
Agent. This agentless protection has some limitations. For more information, see Rapid Snap for Virtual agentless protection.
Before installing Rapid Recovery release 6.1, ensure that your system meets the following minimum hardware and software requirements.
For additional guidance for sizing your hardware, software, memory, storage, and network requirements, see knowledge base article
185962, “Sizing Rapid Recovery Deployments.”
CAUTION: Dell does not support running the Rapid Recovery Core on Windows Core operating systems, which offer limited
server roles. This includes all editions of Windows Server 2008 Core, Windows Server 2008 R2 Core, Windows Server 2012
Core, Windows Server 2012 R2 Core, and Windows Server 2016 Core. Excluding Windows Server 2008 Core, these Core edition
operating systems are supported for running the Rapid Recovery Agent software.
NOTE: Dell does not recommend installing Rapid Recovery Core on an all-in-one server suite such as Microsoft Small Business
Server or Microsoft Windows Server Essentials.
CAUTION: Dell does not recommend running the Rapid Recovery Core on the same physical machine that serves as the Hyper-V
host. (This recommendation does not apply to Dell DL series of backup and recovery appliances.)
Dell Data Protection | Rapid Recovery 6.1
25
Rapid Recovery release 6.1 operating system installation and
compatibility matrix
Microsoft Windows operating systems
Rapid Recovery Core must be installed on an appropriately sized server running a supported 64-bit Microsoft Windows operating system.
The following table and notes list each Windows operating system and describes compatibility for each Rapid Recovery component or
feature.
NOTE: This information is provided to educate users on compatibility. Dell does not support operating systems that have
reached end of life.
Table 12. Rapid Recovery components and features compatible with Windows operating systems
Windows OS
Core/
Agent
Central
Manage
ment
Console
Agentless LMU
MR
DR
URC
Restore
VM Export
to Azure
Windows XP SP3
No
No
Yes
No
No
No
Yes1
No
Windows Vista™
No
No
Yes
No
No
No
Yes1
No
No
Windows Vista SP2
No
Yes
Yes
Yes
Yes
Yes
Yes1
Windows 7
No
No
Yes
No
No
No
Yes
Yes3
Windows 7 SP1
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes3
Windows 8
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes3
Windows 8.1
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes3
Windows 10
Yes2
Yes2
Yes2
Yes
Yes
Yes
Yes
Yes3
Windows Server 2003
No
No
Yes
No
No
No
Yes1
No
Windows Server 2008
No
No
Yes
No
No
No
Yes1
Yes3
Windows Server 2008 SP2
Yes
Yes
Yes
Yes
Yes
Yes
Yes1
Yes3
Windows Server 2008 R2
No
No
Yes
No
No
No
Yes
Yes3
Windows Server 2008 R2 SP1
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes3
Windows Server 2012
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes3
Windows Server 2012 R2
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes3
Windows Server 2016
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Windows installation and support notes:
1
The boot CD supports bare metal restore, but does not support driver injection.
2
In general, AppAssure 5.4.x and Rapid Recovery 6.x components work on Windows 10, with two exceptions:
•
26
The Rapid Recovery Add-on for Kaseya® cannot be installed on Windows 10.
Dell Data Protection | Rapid Recovery 6.1
•
3
SCSI controller drivers are missing in Windows 10 machines exported to VirtualBox hypervisor.
VM export to Azure works only for x64 editions of operating systems listed.
Linux operating systems
Linux operating systems are supported as protected machines in a Rapid Recovery Core. You can use agentless protection, or install the
Rapid Recovery Agent. The following table and notes list each supported Linux operating system and distribution, and describes support
for each Rapid Recovery component or feature.
Table 13. Compatible Rapid Recovery components and features by Linux operating system
Linux OS or distribution
Agent
Agentless
Live DVD
Red Hat Enterprise Linux 6.3 - 6.8
Yes
Yes
Yes
Red Hat Enterprise Linux 7.0 - 7.2
Yes
Yes
Yes
CentOS Linux 6.3 - 6.8
Yes
Yes
Yes
CentOS Linux 7.0 - 7.2
Yes
Yes
Yes
Debian Linux 7, 8
Yes
Yes
Yes
Oracle Linux 6.3 - 6.8
Yes
Yes
Yes
Oracle Linux 7.0 - 7.2
Yes
Yes
Yes
Ubuntu Linux 12.04 LTS, 12.10
Yes
Yes
Yes
Ubuntu Linux 13.04, 13.10
Yes
Yes
Yes
Ubuntu Linux 14.04 LTS, 14.10
Yes1
Yes1
Yes1
Ubuntu Linux 15.04, 15.10
Yes1
Yes1
Yes1
Ubuntu Linux 16.04 LTS
Yes1
Yes1
Yes1
SUSE Linux Enterprise Server 11 SP2 or later
Yes
Yes
Yes
SUSE Linux Enterprise Server 12
Yes1
Yes1
Yes1
Linux installation and support notes:
1
B-tree file system (BTRFS) is supported only on operating systems with kernel version 4.2. or later. Compliant operating systems
currently include Ubuntu versions 14.04.4, 15.10, and 16.04. SUSE Linux Enterprise Server versions 12 and 12 SP1 have older kernel
versions, and so Rapid Recovery does not support their implementations of BTRFS.
Rapid Recovery Core and Central Management Console
requirements
Requirements for the Rapid Recovery Core and the Central Management Console (CMC) are described in the following table.
Operating system requirements for the Central Management Console are identical to the requirements for the Rapid Recovery Core.
These components can be installed on the same machine or on different machines, as your needs dictate.
Dell Data Protection | Rapid Recovery 6.1
27
Table 14. Rapid Recovery Core and Central Management Console requirements
Requirement
Details
Operating system
The Rapid Recovery Core and Central Management Console require one of the following 64-bit Windows
operating systems (OS). They do not run on 32-bit Windows systems or any Linux distribution. Rapid Recovery
Core requires one of the following x64 Windows operating systems:
•
•
•
•
•
•
Microsoft Windows 7 SP1
Microsoft Windows 8, 8.1*
Microsoft Windows 10
Microsoft Windows Server 2008 SP2, 2008 R2 SP1 (except Core editions)
Microsoft Windows Server 2012, 2012 R2* (except Core editions)
Microsoft Windows Server 2016* (except Core editions)
Windows operating systems require the .NET Framework 4.5.2 to be installed to run the Rapid Recovery Core
service. Additionally, any OS marked with * requires the ASP .NET 4.5x role or feature. When installing or
upgrading the Core, the installer checks for these components based on the OS of the Core server, and installs or
activates them automatically if required.
The Rapid Recovery Core supports all x64 editions of the Windows OS listed, unless otherwise indicated. The
Rapid Recovery Core does not support Windows Server core editions.
If any operating system listed specifies a service pack (for example, Windows 7 SP1), then the OS with the
specified service pack is the minimum requirement. If an operating system is listed without a service pack (for
example, Windows 8), then the base operating system is supported. Any subsequent SP for a listed OS is also
supported, unless explicitly excluded.
For optimal performance, it is recommended that you install the Rapid Recovery Core on more recent operating
systems such as Windows 8.1 (or later) and Windows Server 2012 (or later).
Architecture
64-bit only
Memory
8GB RAM or more
Dell highly recommends using Error Checking & Correction (ECC) memory, to ensure optimum performance of
Rapid Recovery Core servers.
Processor
Quad-core or higher
Storage
Dell recommends locating your repository on direct attached storage (DAS), storage area network (SAN), or
network attached storage (NAS) devices (listed in order of preference).
NOTE: If installing on a NAS, Dell recommends limiting the repository size to 6TB. Any storage device
must meet the minimum input/output requirements. See Dell knowledge base article 185962, “Sizing
Rapid Recovery Deployments” for guidance in sizing your hardware, software, memory, storage, and
network requirements.
Network
1 gigabit Ethernet (GbE) minimum
NOTE: Dell recommends a 10GbE network backbone for robust environments.
Network hardware
Use network cables with the appropriate rating to obtain the expected bandwidth.
NOTE: Dell recommends testing your network performance regularly and adjusting your hardware
accordingly.
28
Dell Data Protection | Rapid Recovery 6.1
Rapid Recovery Agent software requirements
Requirements for the Rapid Recovery Agent software are described in the following table.
Table 15. Rapid Recovery Agent software requirements
Requirement
Details
Operating system
The Rapid Recovery Agent software supports 32-bit and 64-bit Windows and Linux operating systems, including
the following:
•
•
•
•
•
•
•
•
•
•
•
•
•
Microsoft Windows Vista SP2
Microsoft Windows 7 SP1
Microsoft Windows 8, 8.1*
Microsoft Windows 10
Microsoft Windows Server 2008 SP2, 2008 R2 SP1 (all editions except Windows Server 2008 Core)
Microsoft Windows Server 2012, 2012 R2*
Microsoft Windows Server 2016*
Red Hat Enterprise Linux (RHEL) 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2
CentOS Linux 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2
Oracle Linux 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2
Debian Linux 7, 8
Ubuntu Linux 12.04 LTS, 12.10, 13.04, 13.10, 14.04 LTS, 14.10, 15.04, 15.10, 16.04 LTS
SUSE Linux Enterprise Server (SLES) 11 (SP2 and later), 12
NOTE: Windows operating systems require the Microsoft .NET framework version 4.5.2 to be installed
to run the Rapid Recovery Agent service. Operating systems listed above that are marked with * also
require the ASP .NET 4.5.x role or feature. When installing or upgrading the Rapid Recovery Agent
software, the installer checks for these components, and installs or activates them automatically if
required.
Additional operating systems are supported for agentless protection only. For more information, see Rapid Snap
for Virtual agentless protection.
If any operating system listed specifies a service pack (for example, Windows 7 SP1), then the OS with the
specified service pack is the minimum requirement. If an operating system is listed without a service pack (for
example, Windows 8), then the base operating system is supported. Any subsequent SP for a listed OS is also
supported, unless explicitly excluded.
The Rapid Recovery Agent software supports Windows Server Core edition installations for Windows Server
2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016. For Windows Server 2008
R2 Core only, you must have SP1 or later. Windows Server 2008 Core edition is not supported.
The Rapid Recovery Agent software supports the Linux distributions included in this list. Most of the released
kernel versions have been tested. File systems supported include ext2, ext3, ext4, and xfs. BTRFS is also
supported (only on certain Linux operating systems with kernel version 4.2. or later). For more information, see
the Rapid Recovery release 6.1 operating system installation and compatibility matrix.
Agents installed on Microsoft Hyper-V Server 2012 operate in the Core edition mode of Windows Server 2012.
NOTE: Native backup of cluster shared volumes is supported on Windows 2008 R2 (SP2 and later)
protected machines only.
Architecture
32-bit or 64-bit
Memory
4GB or higher
Dell Data Protection | Rapid Recovery 6.1
29
Requirement
Details
Processor
Single processor or higher
Microsoft Exchange
Server Support
Microsoft Exchange Server 2007 SP1 Rollup 5 or later, Exchange Server 2010, Exchange Server 2013, or
Exchange Server 2016
Microsoft SQL
Server Support
Microsoft SQL Server 2008 or higher
Microsoft SharePoint Microsoft SharePoint 2007, 2010, 2013, 2016
Storage
Direct attached storage, storage area network or network attached storage
Network
1 gigabit Ethernet (GbE) minimum
NOTE: Dell recommends a 10GbE network backbone for robust environments.
Dell does not recommend protecting machines over a wide-area network (WAN). If you have multiple networked
sites, Dell recommends installing a Core at each site. To share information, you can replicate between the Cores
located at different sites. Replication between Cores is WAN-optimized. The data transmitted is compressed,
deduplicated, and encrypted during transfer.
Network hardware
Use network cables with the appropriate rating to obtain the expected bandwidth.
NOTE: Dell recommends testing your network performance regularly and adjusting your hardware
accordingly.
Rapid Recovery Local Mount Utility software requirements
The Local Mount Utility (LMU) is included with Rapid Recovery. You can obtain the LMU installer from the Downloads page from either
the Core Console or the Dell Data Protection | Rapid Recovery License Portal.
Table 16. Local Mount Utility software requirements
Requirement
Details
Operating system
The Rapid Recovery Local Mount Utility software supports 32-bit and 64-bit Windows operating systems,
including the following:
•
•
•
•
•
•
•
Microsoft Windows Vista SP2
Microsoft Windows 7 SP1
Microsoft Windows 8, 8.1*
Microsoft Windows 10
Microsoft Windows Server 2008 SP2, 2008 R2 SP1 (all editions except Windows Server 2008 Core and
Windows Server 2008 R2 Core)
Microsoft Windows Server 2012, 2012 R2*
Microsoft Windows Server 2016*
NOTE: Windows operating systems require the Microsoft .NET framework version 4.5.2 to be installed
to run the Local Mount Utility service. Operating systems listed above that are marked with * also
require the ASP .NET 4.5.x role or feature. When installing or upgrading the LMU, the installer checks
for these components, and installs or activates them automatically if required.
If any operating system listed specifies a service pack (for example, Windows 7 SP1), then the OS with the
specified service pack is the minimum requirement. If an operating system is listed without a service pack (for
30
Dell Data Protection | Rapid Recovery 6.1
Requirement
Details
example, Windows 8), then the base operating system is supported. Any subsequent SP for a listed OS is also
supported, unless explicitly excluded.
The LMU software supports Windows Server Core edition installations for Windows Server 2012, Windows Server
2012 R2, and Windows Server 2016. Windows Server 2008 Core edition and Windows Server 2008 R2 Core
edition are not supported.
Architecture
32-bit or 64-bit
Memory
4GB or higher
Processor
Single processor or higher
Network
1 gigabit Ethernet (GbE) minimum
NOTE: Dell recommends a 10GbE network backbone for robust environments.
Network hardware
Use network cables with the appropriate rating to obtain the expected bandwidth.
NOTE: Dell recommends testing your network performance regularly and adjusting your hardware
accordingly.
Rapid Snap for Virtual agentless protection
The Rapid Snap for Virtual feature of Rapid Recovery lets you protect virtual machines (VMs) on specific hypervisor platforms without
installing the Rapid Recovery Agent on each guest machine.
When using this feature on the Hyper-V hypervisor platform, you only install Agent on the Hyper-V host. When using this feature on
VMware ESXi, the ESXi host uses native APIs to extend protection to its guest machines.
Since the Agent software is not required to be installed on every VM, this feature is known in the industry as agentless protection. On
Hyper-V, we also refer to this as host-based protection.
Rapid Snap for Virtual offers several benefits, and also some restrictions. As an example, you cannot capture snapshots of dynamic
volumes (such as spanned, striped, mirrored, or RAID volumes) at the volume level. You can, however, capture snapshots on dynamic
volumes at the disk level. Ensure that you understand both the benefits and restrictions before using this feature. For more information,
see the topic “Understanding Rapid Snap for Virtual” in the Dell Data Protection | Rapid Recovery User Guide.
When using agentless or host-based protection, your VMs have the same minimum requirements for base operating system, RAM,
storage, and network infrastructure as machines protected with the Rapid Recovery Agent software. For details, see the topic Rapid
Recovery Agent software requirements.
Agentless support for other operating systems
Rapid Recovery release 6.x uses Microsoft .NET 4.5.2, which is not supported by Windows XP SP3, Windows Vista (prior to SP2),
Windows Server 2003, and Windows Server 2008. If you protected machines with these operating systems in an earlier Core version
(such as AppAssure Core 5.4.3), the corresponding version of AppAssure Agent (which used an earlier version of .NET) was supported.
You can continue to protect these machines in a Rapid Recovery Core, using the earlier Agent version.
However, protected machines with these operating systems cannot be upgraded to Rapid Recovery Agent release 6.x.
Dell Data Protection | Rapid Recovery 6.1
31
Nonetheless, machines with these Windows operating systems can be protected in a Rapid Recovery release 6.x Core using one of the
following methods:
•
Protect virtual machines on a VMware ESXi host using agentless protection.
•
Install and run an earlier compatible version of Agent on a physical or virtual machine you want to protect. For release 6.0.2, the only
supported compatible Agent version for these OS is AppAssure Agent 5.4.3.
VMware ESXi environments are compatible with some operating systems that Dell does not support. For example, Windows XP SP3,
Windows Vista (prior to SP2), Windows Server 2003, and Windows Server 2008 have all reached end of life with Microsoft.
During testing, the full range of Rapid Recovery features (backup, restore, replication, and export) functioned properly with these specific
operating systems.
Nonetheless, use these operating systems at your own risk. Dell Support will not be able to assist you with issues for operating systems
that have reached end of life, or that are listed as unsupported for Rapid Recovery Agent.
Rapid Snap for Virtual (agentless protection) support limitations
For a list of supported operating systems, see Rapid Recovery release 6.1 operating system installation and compatibility matrix. Any known
limitations are included in these matrices, or as notes to the software requirements tables for the Core or the Agent, respectively. If a
defect precludes the use of specific features temporarily, this information is typically reported in the release notes for any specific release.
Dell strongly encourages users to review system requirements and release notes prior to installing any software version.
Dell does not fully test with unsupported operating systems. If using agentless protection to protect virtual machines with an OS not
supported by the Rapid Recovery Agent software, do so at your own risk. Users are cautioned that some restrictions or limitations may
apply. These restrictions may include:
•
An inability to perform virtual export (one-time or continual)
•
An inability to save to an archive or restore from an archive
•
An inability to restore to a system volume using bare metal restore
For example, if agentlessly protecting a machine with Windows 95, attempts at virtual export to Hyper-V will fail. This failure is due to
restrictions in Hyper-V support of that older operating system.
To report specific difficulties, you can contact your Dell Support representative. Reporting such difficulties lets Dell potentially include
specific incompatibilities in knowledge base articles or future editions of release notes.
Hypervisor requirements
A hypervisor creates and runs virtual machines (guests) on a host machine. Each guest has its own operating system.
Using the virtual export feature of Rapid Recovery, you can perform a one-time virtual export, or define requirements for continual virtual
export known as virtual standby. This process can be performed from any protected machine, physical or virtual. If a protected machine
goes down, you can boot up the virtual machine to restore operations, and then perform recovery.
Rapid Recovery lets you perform virtual export to VM hosts described in the following table.
Table 17. Hypervisor requirements supporting virtual export
Requirement
Details
Virtual machine host
VMware
•
•
32
VMware Workstation 7.0, 8.0, 9.0, 10, 11, 12
VMware vSphere on ESXi 5.0, 5.1, 5.5, 6.0
Dell Data Protection | Rapid Recovery 6.1
Requirement
Details
NOTE: Dell recommends running on the most recent supported VMware version. Future
major releases of our software are not expected to support ESXi 5.0 and 5.1.
Microsoft Hyper-V
NOTE: For virtual export to any Hyper-V host, .NET 4.5.2 and .NET 2.0 are required on the
Hyper-V host.
•
•
First generation
• Hyper-V running on Microsoft Server versions 2008 SP2, 2008 R2 SP1, 2012, 2012 R2, 2016
• Hyper-V running on Microsoft Windows 8, 8.1 with Hyper-V, Windows 10
Second generation
• Hyper-V running on Microsoft Server 2012 R2, 2016
• Hyper-V running on Microsoft Windows 8.1, Windows 10
NOTE: Only protected machines with the following Unified Extensible Firmware Interface
(UEFI) operating systems support virtual export to Hyper-V second-generation hosts:
• Windows 8 (UEFI)
• Windows 8.1 (UEFI)
• Windows Server 2012 (UEFI)
• Windows Server 2012 R2 (UEFI)
• Windows Server 2016 (UEFI)
Hyper-V export to second-generation VM can fail if the Hyper-V host does not have enough
RAM allocated to perform the export.
Oracle VirtualBox
•
Guest (exported)
operating system
VirtualBox 4.2.18 and higher
Volumes under 2TB. For protected volumes under 2TB, the VM (guest) can use the same supported
operating systems described in the topic Rapid Recovery Agent software requirements.
Volumes over 2TB. If you want to perform virtual export on a system for which the protected volumes
exceed 2TB, use Windows 2012 R2, Windows Server 2016, VMware ESXi 5.5, or VMware ESXi 6.0. Earlier
operating systems are not supported based on an inability of the host to connect to the virtual hard disk
(VHD).
Both Hyper-V generation 1 and generation 2 VMs are supported.
NOTE: Not all operating systems are supported on all hypervisors.
Storage
The storage reserved on the host must be equal to or larger than the storage in the guest VMs.
Architecture
32-bit or 64-bit
Rapid Recovery lets you protect VM hosts without installing the Rapid Recovery Agent software. This is known as agentless protection.
For more information, including exclusions for agentless protection, see the Dell Data Protection | Rapid Recovery User Guide topic
"Understanding Rapid Snap for Virtual."
Agentless protection is supported as described in the following table.
Table 18. Hypervisor requirements supporting agentless or host-based protection
Requirement
Details
Virtual machine host
VMware
Dell Data Protection | Rapid Recovery 6.1
33
Requirement
Details
•
•
VMware vSphere on ESXi 5.0 (build 623860 or later), 5.1, 5.5, 6.0.
You should also install the latest VMware Tools on each guest.
NOTE: Dell strongly recommends running on the most recent supported VMware version.
Future major releases of our software are not expected to support ESXi 5.0 and 5.1.
Microsoft Hyper-V
•
•
•
•
•
Windows Server 2012 R2
Windows Server 2016
Windows 8 x64
Windows 8.1 x64
Windows 10 x64
Operating system
For volume-level protection, volumes on guest VMs must have GPT or MBR partition tables. If other partition
tables are found, protection occurs at the disk level, not at the volume level.
Storage
The storage reserved on the host must be equal to or larger than the storage in the guest VMs.
Architecture
32-bit or 64-bit
DVM repository requirements
When you create a Deduplication Volume Manager (DVM) repository, you can specify its location on a local storage volume or on a storage
volume on a Common Internet File System (CIFS) shared location. If creating the repository locally on the Core server, you must allocate
resources accordingly.
DVM repositories must be stored on primary storage devices. Archival storage devices such as Data Domain are not supported due to
performance limitations. Similarly, repositories should not be stored on NAS filers that tier to the cloud, as these devices tend to have
performance limitations when used as primary storage.
Dell recommends locating your repository on direct attached storage (DAS), storage area network (SAN), or network attached storage
(NAS) devices. These are listed in order of preference. If installing on a NAS, Dell recommends limiting the repository size to 6TB. Any
storage device must meet the minimum input/output requirements. For these requirements, and for additional guidance for sizing your
hardware, software, memory, storage, and network requirements, see the Dell Data Protection | Rapid Recovery Sizing Guide referenced
below.
When creating a DVM repository, you are required to specify the repository size on a volume. Each DVM repository supports up to 4096
repository extents (additional storage volumes).
Dell does not support installing a Rapid Recovery Core or a repository for a Core on a cluster shared volume (CSV).
You can install multiple DVM repositories on any volume on a supported physical or virtual host. The installer lets you determine the size of
a DVM repository.
NOTE: You can generate an on-demand or scheduled report to monitor the size and health of your repository. For more
information on generating a Repository report, see the topic Generating a report from the Core Console in the Dell Data
Protection | Rapid Recovery User Guide.
Always create your repository in a dedicated folder or directory, not the root folder on a volume. For example, if installing on a local path,
use D:\Repository\ instead of D:\. The best practice is to create separate directories for data and metadata. For example, D:
\Repository\Data and D:\Repository\Metadata.
34
Dell Data Protection | Rapid Recovery 6.1
For more information on using Rapid Recovery, see the Dell Data Protection | Rapid Recovery User Guide. For more information on
managing Dell Data Protection | Rapid Recovery licenses, see the Dell Data Protection | Rapid Recovery License Portal User Guide. For
more information on sizing your hardware, software, memory, storage, and network requirements, see the Dell Data Protection | Rapid
Recovery Sizing Guide referenced in knowledge base article 185962, “Sizing Rapid Recovery Deployments.”
License requirements
Before you can install Rapid Recovery components, you must register at the Dell Data Protection | Rapid Recovery License Portal, create
an account, and obtain a license key or file, which is required to download the Rapid Recovery Core and Rapid Recovery Agent software
and to configure and protect machines. To register the Core with the license portal, the server must have internet connectivity, and be
able to check in with the license portal on a regular basis.
For more information about the Dell Data Protection | Rapid Recovery License Portal, obtaining a license key, and registering for an
account, see the Dell Data Protection | Rapid Recovery License Portal User Guide.
Product licensing
To use and manage any version of Rapid Recovery, AppAssure, or Dell DL series backup and recovery appliance software, you need two
items:
1
An account on the Dell Data Protection | Rapid Recovery License Portal.
License portal accounts are free. If you are a new user, register at https://licenseportal.com. When you register, use the email
address that is on file with your Dell sales representative. If upgrading from a trial version, use the email address associated with the
trial version. If you need to use a different email address, contact your Dell sales representative for assistance.
NOTE: This license portal was previously known as the Dell AppAssure License Portal. If you already have a license
portal account that you have used for AppAssure, use that account information. Previous license portal users do not
need to register a new account for Rapid Recovery.
For more details about the license portal, please see the Dell Data Protection | Rapid Recovery License Portal User Guide.
2
A software license. Use of Rapid Recovery requires a license. You can use a trial license, which has a limited lifetime; or you can use a
long-term (non-trial) license. After a trial license expires, the Rapid Recovery Core stops taking snapshots until you obtain and
register a valid long-term license.
If you registered for a trial version of Rapid Recovery, the installer is configured with a trial license which you can use immediately.
This temporary license is valid for 14 days, and can be extended one time by the group administrator to a 28-day license.
If you purchased a Dell DL backup and recovery appliance, your appliance is configured with a 30-day temporary license that is
activated automatically the first time you start the Core on the appliance.
After you purchase software or a Dell DL appliance, you receive by email a long-term (non-trial) license file or license number. If
specified on the sales order, the license is sent to the end user email address. Otherwise, the long-term license is sent to the contact
email address on the sales order.
To enable a trial software license:
When you register for a trial version, a trial license is written into the Rapid Recovery Core software installer. Simply log in to your license
portal account and download the Rapid Recovery Core software. Carefully review the Rapid Recovery system requirements, and install a
Rapid Recovery Core. You can begin protecting machines and backing up immediately.
To enable a purchased commercial software license (without a trial license):
If you purchased a software license and did not start with a trial license, then you are prompted for the license from the Core Console after
you install the Rapid Recovery Core. Enter the license number, or browse and locate the license file provided to you by email in your sales
order. For more information, see the topic “Updating or changing a license” in the Dell Data Protection | Rapid Recovery User Guide.
Dell Data Protection | Rapid Recovery 6.1
35
To enable a trial DL appliance license:
Each Dell DL series appliance contains a 30-day license that is activated automatically the first time you start the Core on the appliance.
To upgrade a trial license:
For uninterrupted backups, upgrade to a long-term license before the trial period expires. Once a trial license expires, the Rapid Recovery
Core stops taking snapshots. To resume backups interrupted by the lack of a license, obtain a long-term license and enter the license
information into the Core Console.
To request a license upgrade, contact your Dell Sales representative by completing the Contact Sales web form at https://
software.dell.com/register/57955. Once you have upgraded or purchased your long-term Rapid Recovery license through your Sales
representative, you receive an email that includes your new license key or file. Enter this license information in the Core Console. For more
information, see the topic “Updating or changing a license” in the Dell Data Protection | Rapid Recovery User Guide.
To add a license to a Dell DL series backup and recovery appliance, see the topic “Adding a license” in the Dell Data Protection | Rapid
Recovery User Guide.
Getting started with Rapid Recovery
The following topics provide information you can use to begin protecting your data with Rapid Recovery.
•
Rapid Recovery Core and Agent compatibility
•
Upgrade and installation instructions
•
Additional resources
Rapid Recovery Core and Agent compatibility
The following table provides a visual guide, by Agent version, of compatibility and support between AppAssure and Rapid Recovery Agents
and Cores.
Table 19. Compatibility between AppAssure and Rapid Recovery Agents and Cores
Agent
AppAssure 5.4.3 Core
Rapid Recovery 6.0.1 Core
Rapid Recovery 6.0.2 Core
Rapid Recovery 6.1.0 Core
Supported
Supported
Supported
Not supported
6.0.1 Agent
Not compatible
Supported
Supported
Supported
6.0.2 Agent
Not compatible
Not compatible
Supported
Supported
6.1.0 Agent
Not compatible
Not compatible
Not compatible
Supported
5.4.3
Agent1
1
EFI partitions on protected machines must be upgraded to Rapid Recovery Agent release 6.0.x or later to successfully restore data,
perform bare metal restore, or perform virtual export.
Upgrade and installation instructions
Dell recommends users carefully read and understand the Dell Data Protection | Rapid Recovery Installation and Upgrade Guide before
installing or upgrading. Specifically, when upgrading, read all topics in the chapter “Upgrading to Rapid Recovery.” For new installations,
read all topics in the chapter “Installing Rapid Recovery.”
36
Dell Data Protection | Rapid Recovery 6.1
Additionally, Dell requires users to carefully review the release notes for each release, and the Rapid Recovery system requirements for
that release, prior to upgrading. This process helps to identify and preclude potential issues. Since the release notes are updated last of all
the product documents for each release, it is your best source for updated system requirements.
If upgrading from AppAssure Core release 5.4.3, or Rapid Recovery Core release 6.0.1, then run the new Core installer software on your
Core. If using replication, always upgrade the target Core before the source Core.
To protect machines using the Agent software, if upgrading from AppAssure Core release 5.4.3, or Rapid Recovery Core release 6.0.1, run
the new Rapid Recovery Agent installer on each machine you want to protect. For more information, see the subtopic Protection.
You can also use the Rapid Snap for Virtual feature to protect VMware virtual machines on an ESXi host without the Agent software.
Important restrictions apply. For more information on benefits or restrictions for agentless protection, see the topic “Understanding
agentless protection” in the Dell Data Protection | Rapid Recovery User Guide.
Dell Software policy is to support two previous releases of software products. If you want to upgrade a version older than two releases,
best practice is to first upgrade to the last release (Rapid Recovery Core release 6.0.1), or the one prior (AppAssure Core release 5.4.3).
You can then run the 6.0.2 installer for the Rapid Recovery Core or Agent component, respectively.
NOTE: If running a localized Core in a language other than English, upgrade directly from AppAssure release 5.4.3 to Rapid
Recovery Core release 6.0.2.
For more information, see the Dell Data Protection | Rapid Recovery Installation and Upgrade Guide.
When upgrading a protected Linux machine from AppAssure Agent to Rapid Recovery Agent version 6.0.x, you must first uninstall
AppAssure Agent. For more information and specific instructions, see the Dell Data Protection | Rapid Recovery Installation and Upgrade
Guide.
To download the Rapid Recovery Core software, you will need to register at the Dell Data Protection | Rapid Recovery License Portal.
Upon successful registration, you can then download the software, carefully review the Rapid Recovery system requirements, and install a
Rapid Recovery Core.
Licensing
Trial versions of Rapid Recovery Core may include a temporary license key. A license key is required to perform uninterrupted backups,
replication, or data restoration. For more information, see the following resources:
•
Basic information about license keys is available in the Product licensing section of these release notes.
•
For information about managing licenses from the Rapid Recovery Core, see the topic “Managing licenses” in the Dell Data Protection
| Rapid Recovery User Guide.
•
For complete details on licensing, see the Dell Data Protection | Rapid Recovery License Portal User Guide.
Protection
To protect any physical or virtual machine (except VMs on VMware vSphere), you must install the Rapid Recovery Agent software. You
can download Rapid Recovery Agent from the license portal to install on each machine you want to protect. You can also deploy Agent to
the machines you want to protect from a properly configured Rapid Recovery Core.
If using a VMware vSphere host for your Core and protected machines, in many cases, you have the option to protect your machines
without installing Rapid Recovery Agent. If using agentless protection, some limitations apply (especially for SQL Server or Exchange
servers). For more information about these limitations, see the topic “Understanding agentless protection” in the Dell Data Protection |
Rapid Recovery User Guide.
Add your machines to protection on the Rapid Recovery Core by using the Protect Machine or Protect Multiple Machines wizard.
Dell Data Protection | Rapid Recovery 6.1
37
NOTE: Before protecting a cluster, you must first create a repository. For more information, see the topic “Creating a DVM
repository” in the in the Dell Data Protection | Rapid Recovery User Guide. Although a repository is also required to protect a
machine, you have the option to create a repository during the workflow for protecting a machine.
Additional resources
Additional information is available from the following:
•
Technical documentation
•
Videos and tutorials
•
Knowledge base
•
Technical support forum
•
Training and certification
•
Dell Data Protection | Rapid Recovery License Portal
Globalization
This section contains information about installing and operating this product in non-English configurations, such as those needed by
customers outside of North America. This section does not replace the materials about supported platforms and configurations found
elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the
same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to
support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia,
Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).
The release is localized to the following languages: Chinese (Simplified), French, German, Japanese, Korean, Portuguese (Brazil), Spanish.
This release has the following known capabilities or limitations:
•
Rapid Recovery release 6.0.1 and later requires Microsoft .NET 4.5.2. AppAssure used an earlier .NET version. There is no downgrade
option available. If you upgrade from AppAssure to Rapid Recovery and then subsequently decide to use a prior version of AppAssure,
you must perform a new installation of AppAssure Core and Agent.
•
Logs and KB articles for Rapid Recovery release 6.1 are in English only.
About Dell
Dell listens to customers and delivers worldwide innovative technology, business solutions, and services they trust and value. For more
information, visit http://software.dell.com.
Contacting Dell
For sales or other inquiries, visit http://software.dell.com/company/contact-us.aspx or call + 1-949-754-8000.
Technical support resources
Technical support is available to customers who have purchased Dell software with a valid maintenance contract and to customers who
have trial versions. To access the Support Portal, go to https://support.software.dell.com.
38
Dell Data Protection | Rapid Recovery 6.1
The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. In
addition, the Support Portal provides direct access to product support engineers through an online Service Request system.
The Support Portal enables you to:
•
Create, update, and manage Service Requests (cases).
•
View Knowledge Base articles.
•
Obtain product notifications.
•
Download software. For trial software, go to http://software.dell.com/trials.
•
Engage in community discussions.
© 2016 Dell Inc. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of
their respective owners. Amazon, Amazon Web Services (AWS), Amazon Simple Storage Service (S3) are trademarks of Amazon.com, Inc. or its affiliates.
CentOS, Red Hat, and Red Hat Enterprise Linux are registered trademarks or trademarks of Red Hat, Inc. in the U.S. and other countries. Chrome and
Google are trademarks or registered trademarks of Google Inc., used with permission. Debian is a registered trademark owned by Software in the Public
Interest, Inc. Kaseya and the Kaseya logo are registered marks of Kaseya Limited in the United States and/or other countries worldwide. Linux® is the
registered trademark of Linus Torvalds in the U.S. and other countries. Microsoft, Active Directory, Azure, Excel, Hyper-V, Outlook, SharePoint, SQL Server,
Visual Studio, Windows, Windows Server, Windows Server Essentials, Windows SharePoint Services, Windows Vista, and Windows XP are either registered
trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. MongoDB is a trademark of MongoDB, Inc. The
OpenStack™ Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation,
in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by
the OpenStack Foundation, or the OpenStack community. Oracle and VirtualBox are trademarks or registered trademarks of Oracle and/or its affiliates in
the United States and other countries. Rackspace and Fanatical Support are either registered service marks/ trademarks or service marks/ trademarks of
Rackspace US, Inc. in the United States and/or other countries. SLES and SUSE are registered trademarks of SUSE LLC in the United States and other
countries. Ubuntu is a registered trademark of Canonical Ltd. VMware, vSphere, ESX, and ESXi are registered trademarks or trademarks of VMware, Inc. in
the United States and/or other jurisdictions. XenServer is a registered trademark of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be
registered in the United States Patent and Trademark Office and in other countries.
Dell Data Protection | Rapid Recovery 6.1
39
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising