Chat now with support
Chat with Support

Rapid Recovery 6.1.3 - Installation and Upgrade Guide

Introduction to Rapid Recovery Rapid Recovery system requirements Installing Rapid Recovery
Understanding Rapid Recovery components About 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 About the Local Mount Utility
Upgrading to Rapid Recovery About us

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 7. Hypervisor requirements supporting virtual export

Requirement

Details

Virtual machine host

VMware:

NOTE: Secure Boot is a new ESXi 6.5 feature. Rapid Recovery support for this feature is planned for the near future. At this time, Rapid Recovery does not support virtual export to vCenter/ESXi 6.5 if the source machine uses the Secure Boot option.

Microsoft Hyper-V:

Oracle VirtualBox:

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

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 on each guest. This is known as agentless protection. For more information, including exclusions for agentless protection, see the Rapid Recovery User Guide topic "Understanding Rapid Snap for Virtual."

Agentless protection is supported as described in the following table.

Table 8. Hypervisor requirements supporting agentless or host-based protection

Requirement

Details

Virtual machine host

VMware:

Microsoft Hyper-V:

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.

Quest 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, Quest 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 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).

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

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 Rapid Recovery User Guide. For more information on managing Rapid Recovery licenses, see the Rapid Recovery License Portal User Guide. For more information on sizing your hardware, software, memory, storage, and network requirements, see the 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 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 Rapid Recovery License Portal, obtaining a license key, and registering for an account, see the Rapid Recovery License Portal User Guide.

Quest Support policy

For customers with a valid support agreement, Quest provides call-in or email support for the current major and minor release, when patched to the latest maintenance release. That release is known as N. Quest also fully supports N - 1 and N - 2. Intermediate versions receive limited support.

Quest describes its product lifecycle (PLC) support policy on its Support website (visit https://support.quest.com/rapid-recovery/, click Policies & PLC, and then expand Software Product Support Lifecycle Policy). To understand full support, limited support, and discontinued support, consult the policy referenced above.

Related Documents