Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - 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

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 Hyper-V 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.
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 and later includes the Rapid Snap for Virtual feature. With the Rapid Recovery Agent installed on each node, you can protect and restore supported VMs hosted on Hyper-V cluster-shared volumes (CSVs) installed on Windows Server 2012 R2 and Windows Server 2016.

In addition, Rapid Recovery release 6.1 and later supports virtual export to Hyper-V CSVs installed on Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016. For information about supported hypervisors, see Hypervisor requirements.

Rapid Recovery only supports protection and restore of CSV volumes running on Windows Server 2008 R2.

The following table depicts current Rapid Recovery support for cluster-shared volumes.

Table 1. Rapid Recovery support for cluster-shared volumes

Operating System

Protect1 and Restore2 VMs on a Hyper-V CSV

Virtual Export to 
Hyper-V CSV

Protect1 and Restore3 of CSV

CSV Operating System

Rapid Recovery Version

Rapid Recovery Version

Rapid Recovery Version

6.0.x

6.1.x

6.0.x

6.1.x

6.0.x

6.1.x

Windows Server 2008 R2

No

No

Yes

Yes

Yes

Yes

Windows Server 2012

No

No

Yes

Yes

No

No

Windows Server 2012 R2

No

Yes

Yes

Yes

No

No

Windows Server 2016

No

Yes

No

Yes

No

No

1 Protect includes protection, replication, rollup, mount, and archiving.

2 Restore includes file-level restore, volume-level restore, bare metal restore, and virtual export.

3 Restore includes file-level restore, volume-level restore, and bare metal restore.

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 Quest 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 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 the topic "Understanding Rapid Snap for Virtual" in the Rapid Recovery User Guide.

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

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.

Table 2. Rapid Recovery components and features compatible with Windows operating systems

Windows OS

Core/ Central Management Console

Agent

Agent-less

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

Windows Vista SP2

No

Yes

Yes

Yes

Yes

Yes

Yes1

No

Windows 7

No

No

Yes

No

No

No

Yes

Yes2

Windows 7 SP1

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows 8

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows 8.1

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows 10

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows Server 2003

No

No

Yes

No

No

No

Yes1

No

Windows Server 2008

No

No

Yes

No

No

No

Yes1

Yes2

Windows Server 2008 SP2

Yes

Yes

Yes

Yes

Yes

Yes

Yes1

Yes2

Windows Server 2008 R2

No

No

Yes

No

No

No

Yes

Yes2

Windows Server 2008 R2 SP1

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows Server 2012

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows Server 2012 R2

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

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 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 3. Compatible Rapid Recovery components and features by Linux operating system

Windows OS

Core/ Central Management Console

Agent

Agentless

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

Yes

Yes

Yes

CentOS Linux 6.3 - 6.8

Yes

Yes

Yes

CentOS Linux 7.0 - 7.3

Yes

Yes

Yes

Debian Linux 7, 8

Yes

Yes

Yes

Oracle Linux 6.3 - 6.8

Yes

Yes

Yes

Oracle Linux 7.0 - 7.3

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 (SLES) 11 SP2 or later

Yes

Yes

Yes

SLES 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 with service pack 4 or later, and versions 15.10 or later. SLES versions 12 and 12 SP1 have older kernel versions, and so Rapid Recovery does not support their implementations of BTRFS.

Related Documents