Chat now with support
Chat with Support

Rapid Recovery 6.2 - System Requirements Guide

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 Rapid Recovery Core Console, the Data Protection Portal (at, or the Rapid Recovery License Portal (at

Table 7. Local Mount Utility software requirements



Operating system

The Rapid Recovery Local Mount Utility software supports 32-bit and 64-bit Windows operating systems, including the following:

NOTE: Windows operating systems require the Microsoft .NET Framework version 4.6.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.6.2 role or feature. When installing or upgrading the LMU, the installer checks for these components, and installs or activates them automatically if required. Installing or upgrading .NET software typically requires a system reboot.

If any operating system listed specifies a service pack (for example, Windows Server 2008 R2 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.1), 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 R2 Core edition is not supported.


32-bit or 64-bit


4GB or higher


Single processor or higher


1 gigabit Ethernet (GbE) minimum

Network hardware

Use network cables with the appropriate rating to obtain the expected bandwidth.

NOTE: Quest 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 software 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 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 protection of SQL Server machines

Rapid Recovery supports agentless protection for all supported SQL Server versions, with the exclusion of SQL Server 2017. Agentless support for SQL Server 2017 is planned for a future release.

Protecting older operating systems with older Agent versions or Agentlessly

Quest does not support software that has reached end of life (EOL). Agent-based protection in release 6.2 requires the OS of the protected machine to support Microsoft .NET Framework version 4.6.2 and SHA-2.

To protect machines in a 6.2 Core running older operating systems, consider running an older supported version of Rapid Recovery Agent. For example, Rapid Recovery Agent releases 6.1.3 and 6.0.2 run Microsoft .NET Framework version 4.5.2, which supports some older Microsoft operating systems. You can protect machines running these versions of Agent in a Rapid Recovery 6.2 Core. For details on versions supported, see Quest Support policy.

Protected machines with these operating systems cannot be upgraded to Rapid Recovery Agent release 6.2.

Another option is to protect machines agentlessly on Hyper-V or VMware ESXi. For more information, see Hypervisor requirements.

You can protect VMware ESXi virtual machines running operating systems that do not support .NET Framework version 4.5.2, such as Windows XP SP3, Windows Vista (prior to SP2), Windows Server 2003, and Windows Server 2008.

You can also protect VMware ESXi virtual machines running operating systems that do not support .NET Framework version 4.6.2, such as Windows 7 SP1, Windows 8, Windows Server 2008 SP2.

For machines running unsupported operating systems, proceed with agentless protection at your own risk. While Quest Data Protection Support can attempt to answer questions for releases under limited support, any required software corrections or patches can only be applied to current or fully supported software releases, respectively.

Rapid Snap for Virtual (agentless protection) support limitations

For a list of supported operating systems and the Rapid Recovery components supported for each, see Rapid Recovery release 6.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. Quest strongly encourages users to review system requirements and release notes prior to installing any software version.

For a list of features that have recently been deprecated or are now only under limited support, see the latest edition of Rapid Recovery Release Notes.

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

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 Quest Data Protection Support representative. Reporting such difficulties lets Quest 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, which can differ from the OS of the host machine.

Using the virtual export feature of , you can perform a one-time virtual export, or define requirements for continual virtual export (this feature is also called "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.

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

Table 8. Hypervisor requirements supporting virtual export



Virtual machine host


Quest recommends installing VMware Tools on protected VMs on vSphere or ESXi hosts.

Microsoft Hyper-V:

Quest recommends installing Hyper-V Integration Services on VMs you want to protect on Hyper-V hosts.

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 .

Volumes over 2TB. If you want to perform virtual export on a system for which the protected volumes exceed 2TB, use a Hyper-V host running Windows 2012 R2, Windows Server 2016, VMware ESXi 5.5, or VMware ESXi 6.0. Earlier operating systems are not supported.

Both Hyper-V generation 1 and generation 2 VMs are supported.


The storage reserved on the host must be equal to or larger than the storage in the guest VMs.


32-bit or 64-bit

lets you protect VM hosts without installing the software on each guest. This is known as agentless protection. For more information, including exclusions for agentless protection, see the topic "Understanding Rapid Snap for Virtual."

Agentless protection is supported as described in the following table.

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



Virtual machine host


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.


The storage reserved on the host must be equal to or larger than the storage in the guest VMs.


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 when using the CIFS protocol, since CIFS is not designed as a high-I/O storage protocol. 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 about using Rapid Recovery, see the Rapid Recovery User Guide. For more information about managing Rapid Recovery licenses from the Core Console, see the "Managing licenses" topic in the Rapid Recovery User Guide or the Rapid Recovery Installation and Upgrade Guide. For more information about administering license groups or licenses on the license portal, 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.”

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating