Chat now with support
Chat with Support

Rapid Recovery 6.2 - Installation and Upgrade Guide

Rapid Recovery overview and system requirements Installing Rapid Recovery Upgrading to Rapid Recovery About us

Rapid Recovery overview and system requirements

This section includes an introduction to Rapid Recovery and where you can find its system requirements.

Topics include:

Introduction to Rapid Recovery

Rapid Recovery is a backup, replication, and recovery solution that offers near-zero recovery time objectives and recovery point objectives. Rapid Recovery offers data protection, disaster recovery, data migration and data management. You have the flexibility of performing bare-metal restore (to similar or dissimilar hardware), and you can restore backups to physical or virtual machines, regardless of origin. Rapid Recovery can also archive to the cloud, to a DL series backup and recovery appliance, or to a supported system of your choice. With Rapid Recovery, you can replicate to one or more targets for added redundancy and security.

Rapid Recovery offers:

Flexibility. You can perform universal recovery to multiple platforms, including restoring from physical to virtual, virtual to physical, virtual to virtual, and physical to physical.
Cloud integration. You can export a VM, archive and replicate to the cloud, and perform bare metal restore from archives in the cloud. Compatible cloud services include Microsoft Azure, Amazon Web Services (AWS), any OpenStack-based provider (including Rackspace), and Google Cloud. US government-specific platforms include AWS GovCloud (US) and Azure Government.
Intelligent deduplication. You can reduce storage requirements by storing data once, and referencing it thereafter (once per repository or encryption domain).
Instant recovery. Our Live Recovery feature allows you to access critical data first, while remaining restore operations complete in parallel.
File-level recovery. You can recover data at the file level on-premises, from a remote location, or from the cloud.
File-level search. Using criteria you specify, you can search a range of recovery points for one or more files. From the search results, you can then select and restore the files you want to the local Core machine directly from the Core Console.
Virtual support. Rapid Recovery supports one-time virtual export, letting you generate a bootable VM from a recovery point; and virtual standby, in which the bootable VM you generate is continually updated after each backup. You can even perform virtual export to Microsoft Hyper-V cluster-shared volumes.
Rapid Snap for Virtual support. Enhanced support for virtualization includes agentless protection for vCenter/ESXi VMs and for Hyper-V VMs. Rapid Snap for Virtual includes protection and autodiscovery for VMware ESXi 5.5 and higher with no agent software installed. Host-based protection supports installing Rapid Recovery Agent on a Microsoft Hyper-V host only, letting you agentlessly protect all its guest VMs.
Application support. Rapid Recovery Agent is built with application support for Microsoft Exchange, SQL Server, and Oracle. When you protect these application servers in your Core, the backup snapshots are automatically application-aware; open transactions and rolling transaction logs are completed and caches are flushed to disk before creating snapshots. Specific application features are supported, including SQL attachability (for SQL Server) and database integrity DBVERIFY checks (for Oracle). Application awareness also extends to agentless protection for SQL Server and Exchange Server.

See the following resources for more information about Rapid Recovery.

The Rapid Recovery product support website at

Where to find Rapid Recovery system requirements

As of Rapid Recovery release 6.2, system requirements are documented in the Rapid Recovery System Requirements Guide. Use this document as your single authoritative source for system requirements, which are always release-specific.

System requirements and all other documentation is found at the technical documentation website at

NOTE: The default view of the technical documentation website shows documentation for the most recent generally available version of the Rapid Recovery software. Using the filters at the top of the page, you can view documentation for a different software release or for a Quest DL series backup and recovery appliance. You can also filter the view by guide category.

Installing Rapid Recovery

Install software as a user with administrative privileges. This recommendation applies to all Rapid Recovery software and is not repeated.

Before you install Rapid Recovery, consider which components are necessary for your implementation, as not all components are required. For more information about these components, see Understanding Rapid Recovery components and related products.

Minimum software requirements

At minimum, plan to install the following for your Rapid Recovery environment:

Rapid Recovery Core. You must install Core on a dedicated Windows server that is properly sized for your environment. The server can be a physical or virtual machine, including a Quest DL series backup and recovery appliance. For guidance on sizing your hardware, software, memory, storage, and network requirements, see knowledge base article 185962, “Sizing Rapid Recovery Deployments".
Hypervisor tools. If your environment includes virtual machines (VMs) hosted on VMware vCenter/ESXi or Hyper-V hypervisors, you can protect VM guests agentlessly using the Rapid Snap for Virtual feature. In such cases, Quest strongly recommends installing VMware Tools or Hyper-V Integration Services utilities on VMs you want to protect. If you want application-consistent agentless backups, this step is required. Otherwise, your backups on VMs running SQL Server or Exchange Server will be crash-consistent only. For more information about the difference between these two states, see "Understanding crash-consistent and application-consistent backups" in the Rapid Recovery User Guide.
Rapid Recovery Agent. You must install the Rapid Recovery Agent software on each physical machine you want to protect in your Core. To protect Hyper-V guests agentlessly, install the Rapid Recovery Agent software on the Hyper-V host. To protect nodes in a Hyper-V cluster, install the Agent software on each node. Finally, install Agent on all VMs you want to protect using standard protection instead of Rapid Snap for Virtual agentless protection.
Microsoft .NET Framework and ASP .NET role or feature. Windows operating systems running Rapid Recovery Core or Agent release 6.2 require the Microsoft .NET Framework version 4.6.2. For Core, some operating systems require the corresponding ASP .NET 4.6.2 role or feature. When installing or upgrading Rapid Recovery, the installer checks the system for required .NET components; if needed, the user is prompted to install or activate the components, which requires a reboot of the machine.

Other components may be required for additional functionality.

General installation approach

The steps you must follow to install Rapid Recovery are as follows:

Step 1: Obtain a software license for Rapid Recovery Core. Some users start with a trial version of Rapid Recovery Core. To continue using the Core after the initial trial period, or to use non-trial versions of the Core, a software license is required. If using a trial version and you want to purchase a software license, complete the form at to be contacted by a Sales representative.
Step 2: Ensure you have an account on the Rapid Recovery License Portal. This portal is used to register and manage software licenses and license groups. Existing AppAssure or Rapid Recovery customers can continue to use their existing license portal accounts. New customers must register on the Rapid Recovery License Portal at, activate their software licenses, download the license files from the license portal, and from the Rapid Recovery Core Console, upload license files. For detailed steps, see the Rapid Recovery Release Notes topic "Licensing Rapid Recovery software and appliances." For information about managing licenses from the Rapid Recovery Core, including uploading license files to associate them with the Core, see the topic Managing licenses. For information about managing license subscriptions and license groups on the license portal, see the Rapid Recovery License Portal User Guide.
Step 3: Review and ensure that the system requirements have been met for the servers and machines on which you plan to install Rapid Recovery components. For more information, see the Rapid Recovery System Requirements Guide.
Step 4: Install the Rapid Recovery Core software on each Windows machine you plan to use as a Core. For more information, see Installing the Rapid Recovery Core.
Step 5: The Core stores backup data in a repository. Before you use the Core to protect machines, if not yet defined, you must specify a storage location and configure a primary repository. You can create a DVM or tiering (secondary) repository as a separate process. You can also create a DVM repository as part of the workflow when using the Protect Machine or Protect Multiple Machines wizards. For detailed information, see “Understanding repositories” in the Rapid Recovery User Guide
Step 6: Install the Rapid Recovery Agent software on all physical Windows or Linux machines you plan to protect. Also install Agent on all Hyper-V hosts; on Hyper-V cluster nodes; and on VMs you want to protect without using agentless protection. For more information, see Installing the Rapid Recovery Agent software on Windows machines and About installing the Agent software on Linux machines.
Step 7: If using Rapid Snap for Virtual to provide agentless protection, install the appropriate hypervisor tool on each VM. For more information, see the topic "Understanding Rapid Snap for Virtual" and subtopics "Benefits of installing hypervisor tools for agentless protection" and "Understanding crash-consistent and application-consistent backups" in the Rapid Recovery User Guide.
Step 8: Consider using the Data Protection Portal. If you have a valid Quest Data Protection Support maintenance agreement, you are entitled to use the Data Protection Portal. This portal is automatically integrated with Rapid Recovery as of release 6.2, and replaces the Rapid Recovery Central Management Console in this release. This feature, particularly useful for managed service providers, lets you manage multiple Cores; access a dashboard where you can monitor tasks and events, view repository status, and check system health; generate reports; and perform a growing list of other functions from a single web-based user interface.

Optionally, you may want to perform other configuration tasks, such as setting encryption keys, configuring event notification, or replicating recovery points from a source Core to a target Core. Each of these configuration tasks is included in the Quick Start Guide feature of Rapid Recovery Core. You can read more information about the Quick Start Guide or performing these tasks independently in the Rapid Recovery User Guide. That document also contains information about tasks such as configuring an SMTP server for notification messages, changing the data retention policy, or configuring SQL attachability.

To learn about using scripts or sending commands to manage your Core from the command line, see the Rapid Recovery Commands and Scripting Reference Guide. If you want to use other Rapid Recovery components such as Mailbox Restore for Exchange or DocRetriever for SharePoint, see the Mailbox Restore for Exchange User Guide or DocRetriever for SharePoint User Guide, respectively. If you want to replicate your on-premises installation of Rapid Recovery Core using Microsoft's Azure platform, see the Rapid Recovery Replication Target for Microsoft Azure Setup Guide.

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents