Chat now with support
Chat with Support

Rapid Recovery 6.7 - System Requirements

Rapid Recovery Core installation requirements

Servers should not have any other applications, roles, or features installed that are not related to Rapid Recovery. For example, do not use the Core server as a high-traffic web server; and do not run Active Directory as a domain controller on the Core server. If possible, do not run server applications such as Exchange Server, Oracle, SharePoint Server, or SQL Server 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. Licensed Rapid Recovery users with an active maintenance agreement can manage two or more Cores from the QorePortal, which can be accessed at https://qoreportal.quest.com/.

Before installing or upgrading Rapid Recovery Core on your Core server, 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.”

Caution: Microsoft offers Server Core editions of their Windows Server products, which have a smaller footprint and limited server roles. Quest does not support running Rapid Recovery Core on these minimal installations of the Windows Server operating systems. Quest only supports Rapid Recovery Core on the standard (or "Desktop Experience") versions of supported Windows Server operating systems.

 

NOTE: Quest does not recommend installing Rapid Recovery Core on an all-in-one server suite such as Microsoft Small Business Server or Microsoft Windows Server Essentials.

 

Caution: Quest does not recommend running the Rapid Recovery Core on the same physical machine that serves as a hypervisor host.

Rapid Recovery 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. Rapid Recovery Core does not support Windows Server core editions.

NOTE: This matrix is provided to educate users on compatibility. Quest does not support operating systems that have reached end of life.

 

Table 2: Rapid Recovery components and features compatible with Windows operating systems.
OS Version Core Agent Agentless LMU MR DR URC Restore URC Driver Injection VM Export to Azure

Windows 8

No

No

Limited

No1

Yes1

Yes1

Limited

Limited

Limited2

Windows 8.1

No

Limited

Yes

No

No

No

Limited

Limited

Limited2

Windows 10

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows 11

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows Server 2012

Yes3

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows Server 2012 R2

Yes3

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows Server 2016

Yes3

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes2

Windows Server 2019

Yes3

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Windows Server 2022

Yes3

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Windows installation and support notes:

1 Follow guidance in Microsoft KB 3033929. Install hotfix per Microsoft KB 2921916. Silent installation of Core is not supported.

2 VM export to Azure works only for x64 editions of operating systems listed.

3Rapid Recovery Core cannot be installed on Windows Core operating systems, which offer limited server roles and have no GUI. This includes all Server Core editions for all currently supported Windows Server operating systems.


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
OS Version or distribution Agent Agentless Live DVD VM Export
to Azure

AlmaLinux 8.3 - 8.6

Yes

Yes

Yes

Yes

CentOS Linux 6.4 - 6.10

Limited2

Limited2

Limited2

Limited2

CentOS Linux 7.0 - 7.9

Yes

Yes

Yes

Yes

CentOS Linux 8.0 - 8.5

Yes

Yes

Yes

Yes

Debian Linux 9

Yes

Yes

Yes

Yes

Debian Linux 10

Yes

Yes

Yes

Yes

Debian Linux 11

Yes

Yes

Yes

Yes

Oracle Linux 6.4 - 6.10

Yes

Yes

Yes

Yes

Oracle Linux 7.0 - 7.9

Yes

Yes

Yes

Yes

Oracle Linux 8.0 - 8.6

Yes

Yes

Yes

Yes

Red Hat Enterprise Linux (RHEL)  6.4 - 6.10

Limited2

Limited2

Limited2

Limited2

RHEL 7.0 - 7.9

Yes

Yes

Yes

Yes

RHEL 8.0 - 8.6

Yes

Yes

Yes

Yes

Rocky Linux 8.3 - 8.6

Yes

Yes

Yes

Yes

SLES 12 SP33

Limited2

Limited2

Limited2

Limited2

SLES 12 SP43

Yes

Yes

Yes

Yes

SLES 12 SP5 (No BMR)3

Yes

Yes

Yes

Yes

SLES 15 SP1, SP23

Yes

Yes

Yes

Yes

SLES 15 SP3, SP4 (No BMR)

Yes

Yes

Yes

Yes

SUSE Linux Enterprise Server (SLES) 11 SP43

Limiteds2

Limited2

Limited2

Limited 2

Ubuntu Linux 16.04 LTS

Limited2

Limited2

Limited2

Limited2

Ubuntu Linux 18.04 LTS

Yes

Yes

Yes

Yes

Ubuntu Linux 19.04, 19.10

Limited2

Limited2

Limited2

Limited2

Ubuntu Linux 20.04 LTS

Yes

Yes

Yes

Yes

Ubuntu Linux 20.10

Yes

Yes

Yes

Yes

Ubuntu Linux 21.04, 21.10

Yes

Yes

Yes

Yes

Ubuntu Linux 22.04 (No BMR)

Limited4

Limited4

Limited4

Limited4

Linux installation and support notes:

1 B-tree file system (BTRFS) is supported only on operating systems with kernel version 3.7 or later. The earliest versions of compliant operating systems include Ubuntu 14.04, Debian 8, CentOS/Oracle Linux/RHEL 7, and SLES 12.
2 This operating system distribution has reached end of life, and is therefore no longer tested. Support for this operating system is therefore limited.
3 This operating system distribution (and SUSE Linux Desktop) fully supported when using listed service packs; versions using earlier SPs are in limited support only.
4 This operating system distribution was tested only for platform detection, not for functionality.

For more information on Linux versions supported by Rapid Recovery, including kernel versions, file systems and restrictions, see Rapid Recovery Agent software requirements

Rapid Recovery Core requirements

Requirements for the Rapid Recovery Core are described in the following table.

Table 4: Rapid Recovery Core requirements
Requirement Details

Operating system

Rapid Recovery Core does not run on 32-bit Windows systems or any Linux distribution. Rapid Recovery Core requires one of the following 64-bit Windows operating systems (OS):
  • Microsoft Windows 10 , 11
  • Microsoft Windows Server versions 2012, 2012 R2, 2016, 2019, 2022

1 The Rapid Recovery Core supports all x64 editions of the Windows Server OS versions listed. However, the Rapid Recovery Core does not support Windows Server core editions

2 Quest provides only limited support for OS versions after their manufacturers end extended support.

 

General Notes:

Windows operating systems require the Microsoft .NET Framework version 4.6.2 to be installed to run the Rapid Recovery Core service.

For optimal performance, it is recommended that you install the Rapid Recovery Core on more recent operating systems.

Architecture

64-bit only

Memory

8GB RAM or more. This is a requirement of Rapid Recovery Core.

Quest highly recommends using Error Checking & Correction (ECC) memory, to ensure optimum performance of Rapid servers.

Processor

Quad-core or higher

Storage

The amount of storage required differs based on your needs. Storage requirements typically increase over time and should be revisited at least annually.

Rapid Recovery supports primary storage in a DVM repository. Characteristics and requirements include the following:

  • DVM repositories can be extended by adding new storage locations.
  • Each volume you define as a storage location must have a minimum of 1GB of free space available on it. Quest recommends minimum storage of 100GB per storage volume.
  • For your repository storage, Quest strongly recommends a configuration of RAID 6 with 4 usable drives or better, for a change rate per hour of up to 10GB. Use more drives for additional capacity or higher change rates.
  • Suggested random input/output per second (IOPS) of 300 or better (based on 4 usable drives each capable of 75 IOPS measured at 32KB with 75% reads with 60 random I/O).
  • There are no specific I/O controller requirements. However, speed is the most important factor for DVM repository storage.
  • Quest recommends locating your DVM repository on direct attached storage (DAS), storage area network (SAN), or network attached storage (NAS) devices (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 IOPS requirements.
 

See Quest knowledge base article 185962, “Sizing Rapid Recovery Deployments,” for additional guidance for sizing your hardware, software, memory, storage, and network requirements.

Network

1 gigabit Ethernet (GbE) minimum

NOTE: Quest recommends a 10GbE network backbone for robust environments. .

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 Recovery Agent software requirements

For each physical machine you want to protect in a Rapid Recovery Core, install the Rapid Recovery Agent software. The Agent software must be compatible with that machine's OS and file system, as detailed in the following matrix.

You can also protect virtual machines (VMs) on your Core. You can use Agent-based protection by installing Rapid Recovery Agent on each VM, as appropriate. Or you can protect VMs on supported hypervisor hosts using Rapid Snap for Virtual agentless protection. There are tradeoffs between using Agent-based and agentless protection. When configured properly, fewer licenses are consumed from your license pool when using Rapid Snap for Virtual. However, you may prefer using Agent-based protection for VMs (for example, when protecting Oracle servers, dynamic volumes, or if you need Live Recovery). For more information, see the topic "Understanding Rapid Snap for Virtual" in the Rapid Recovery User Guide.

Requirements for the Rapid Recovery Agent software are described in the following table. Review carefully for each release, as requirements change. Snapshot data for each protected machine must be saved to a DVM repository only. Tiering is not supported in this release.

You cannot use the Rapid Recovery Add-on for Kaseya to deploy Rapid Recovery Agent to a Linux machine you want to protect in your Core. If using the Add-on, manually install Rapid Recovery Agent on each Linux machine. For more information on installing Agent, see the Rapid Recovery Installation and Upgrade Guide.

Table 5: Rapid Recovery Agent software requirements
Requirement Details
Operating system Windows operating systems require the Microsoft .NET Framework version 4.6.2 to be installed to run the Rapid Recovery Agent service. The Rapid Recovery Agent software supports 32-bit and 64-bit Windows and Linux operating systems, including the following:
  • Microsoft Windows version 10, 111
  • Microsoft Windows Server versions 2012, 2012 R2, 20161, 20191,5,, 2022.
  • AlmaLinux 8.3 - 8.64
  • CentOS Linux 6.4 - 6.103, 7.0 - 7.9, 8.0 - 8.5
  • Debian Linux 9, 10, 11
  • Oracle Linux 6.4 - 6.103, 7.0 - 7.8, 8.0 - 8.6
  • Red Hat Enterprise Linux (RHEL) 6.4- 6.103, 7.0- 7.8, 8.0-8.6
  • SUSE Linux Enterprise Server (SLES) 11 (SP4 and later)6, 12 (SP3 and later)6, 15 (SP1 and later)6
  • Ubuntu Linux 16.04 LTS3, 18.04 LTS, 19.043, 19.103, 20.04 LTS, 20.10, 21.044, 21.10, 22.04

1 Requires the ASP .NET 4.6.2. role or feature. When installing or upgrading the Rapid Recovery Agent software, the installer checks for the ASP .NET 4.6.2. role or feature. If required, the installer installs or activates this component and then reboots.
2 Follow guidance in Microsoft KB 3033929. For silent installation, see Microsoft KB 2921916.
3 This operating system has reached end of life, and is therefore no longer tested. Support for this operating system is therefore limited.
4 This operating system distribution was tested only for platform detection, not for functionality.
5 ReFS volumes supported for protection only on most recent update of Windows Server 2019.
6 SUSE Linux Enterprise with the listed service packs are fully supported. Older versions are on limited support. SUSE Linux Enterprise Desktop is supported at the same version level.

 

Additional operating systems are supported for agentless protection only. For more information, see Rapid Snap for Virtual agentless protection.

The Rapid Recovery Agent software supports Windows Server Core edition installations for Windows Server version 2012, 2012 R2, 2016, 2019, and 2022.

The Rapid Recovery Agent software supports the Linux distributions included in this list. Additionally, note the following:

Linux kernel. Rapid Recovery supports Linux kernel versions 2.6.32 and later.

FIle systems and restrictions. Supported file systems include ext2, ext3, ext4, xfs, and BTRFS. The following restrictions apply:

  • ext2 is supported only on kernel version 3.6.0 or later.
  • BTRFS is supported on Linux operating systems with kernel 3.7 or later. This minimum kernel version is included beginning with Ubuntu 14.04, Debian 8, CentOS/Oracle Linux/RHEL 7, and SLES 12. If the kernel on earlier versions of these OS is upgraded to 3.7 or later, BTRFS is supported.

For more information, see the Rapid Recovery operating system installation and compatibility matrix.

Agents installed on Microsoft Hyper-V Server versions 2012, 2012 R2, 2016 and 2019 operate in the Core edition mode of the relevant Windows Server OS.

Architecture 32-bit or 64-bit
Memory 4GB or higher

Processor

Single processor or higher

Microsoft Exchange Server support

Rapid Recovery supports Microsoft Exchange Server versions 2013, 2016, and 2019.

Microsoft SQL Server support

The following Microsoft SQL Server versions are supported on Windows machines only (no Linux support): 2012, 2014, 2016, 2017, and 2019.

Microsoft SharePoint Server support

Microsoft SharePoint versions 2016 and 2019

NOTE: Support for "SharePoint" refers to fully licensed versions of Microsoft SharePoint Server for the versions listed above.

Oracle relational database support

Rapid Recovery Agent supports the following versions of Oracle relational database management systems (RDBMS):

  • Oracle 18c RDBMS u[']/[sing Rapid Recovery 6.4.0 or later on 64-bit servers running Windows Server 2016 only.
  • Oracle 12c RDBMS using Rapid Recovery 6.2 or later on 64-bit servers running Windows Server 2016.

Protection of Oracle12c and 18c databases is limited to using Volume Snapshot Service (VSS) in the ARCHIVELOG mode. Agentless protection is not supported.

Oracle Agent-based support includes application awareness. You can perform database integrity checks against our volume images using DBVERIFY (a native Oracle utility). For more information, see "About protecting Oracle database servers" in the Rapid Recovery User Guide.

Storage Direct attached storage, storage area network or network attached storage
Network

1 gigabit Ethernet (GbE) minimum

NOTE: Quest recommends a 10GbE network backbone for robust environments.

Quest does not recommend protecting machines over a wide-area network (WAN). If you have multiple networked sites, Quest recommends installing a Core at each site. To share information, you can replicate between the Cores located at different sites. Replication between Cores is WAN-optimized. The data transmitted is compressed, deduplicated, and encrypted during transfer.

Network hardware

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

NOTE: Quest recommends testing your network performance regularly (at least once annually) and adjusting your hardware accordingly.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating