Quest has been named as an ASP "Ten Best Web Support Sites" award winner. Learn more.

Rapid Recovery 6.0.2 - Installation and Upgrade Guide

*** Legend Introduction to Dell Data Protection | Rapid Recovery Rapid Recovery system requirements Installing Rapid Recovery
Understanding Rapid Recovery components Installing the Rapid Recovery Core Installing the Rapid Recovery Agent software Installing the Rapid Recovery Central Management Console Automatically installing updates Uninstalling the Rapid Recovery Core Uninstalling the Rapid Recovery Agent software Uninstalling the AppAssure Agent software from a Linux machine Uninstalling the Rapid Recovery Central Management Console
Upgrading to Rapid Recovery

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. Requirements for the Local Mount Utility are described in the following table.

Table 1. 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*
 
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 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 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 2012 and 2012 R2. 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.

Was this topic helpful?

[Select Rating]



Rapid Snap for Virtual agentless protection

The Rapid Snap for Virtual feature of Rapid Recovery lets you protect virtual machines (VMs) on a VMware ESXi host without installing the Rapid Recovery Agent software. This feature, Rapid Snap for Virtual, is also called agentless protection.

Agentless protection 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. (Agentless protection does let you capture snapshots on dynamic volumes at the disk level.) Before using agentless protection, ensure that you understand both the benefits and restrictions. For more information, see the topic "Understanding agentless protection" in the Dell Data Protection | Rapid Recovery User Guide.

When using agentless 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.

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


Was this topic helpful?

[Select Rating]



Hypervisor requirements

A hypervisor creates and runs virtual machines (guests) on a host machine. Each guest has its own operating system.

Using the virtual standby feature of Rapid Recovery, you can perform a one-time virtual export, or define requirements for continual virtual export. This process can be performed from any protected machine, physical or virtual. Exporting your data to a virtual standby machine provides you with a high availability copy of the data. If a protected machine goes down, you can boot up the virtual machine to then perform recovery.

Rapid Recovery lets you perform virtual export to VM hosts described in the following table.

Table 1. Hypervisor requirements supporting virtual export
Requirement Details
Virtual machine host VMware
  • VMware Workstation 7.0, 8.0, 9.0, 10, 11
  • VMware vSphere on ESX or ESXi 4.0, 4.1, 5.0, 5.1, 5.5, 6.0
    Note: Dell recommends running on the most recent supported VMware version.

Microsoft Hyper-V

  • Hyper-V running on Microsoft Server 2008 SP2, 2008 R2 SP1, 2012, 2012 R2
  • Hyper-V running on Microsoft Windows 8, 8.1 with Hyper-V, Windows 10
Note: For virtual export to any Hyper-V host, .NET 4.5.2 is required on the Hyper-V host.

Oracle

  • Oracle VirtualBox 4.2.18 and higher
Guest (exported) operating system 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 or VMware ESX(i) 5.5. Earlier OS are not supported based on an inability of the host to connect to the virtual hard disk (VHD).

Both Hyper-V Gen 1 and Gen 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 agentless protection."

Agentless protection is supported as described in the following table.

Table 2. Hypervisor requirements supporting agentless protection. This table lists Hypervisor requirements specific to agentless protection, including virtual machine host, guest OS, storage, and architecture. The second column specifies details for each requirement.
Requirement Details
Virtual machine host VMware
  • VMware vSphere on ESX or 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.
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

Was this topic helpful?

[Select Rating]



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.

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


Was this topic helpful?

[Select Rating]



Related Documents