Rapid Recovery 6.2.1 - System Requirements Guide

Rapid Recovery release 6.2.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. 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 3: Rapid Recovery components and features compatible with Windows operating systems.
Windows OS Core Agent Agent-less LMU MR DR URC Restore VM Export to Azure
Windows 7 SP1 No No Limited No No No Limited Limited1
Windows 8 No No Limited Yes2 Yes2 Yes2 Limited Limited1
Windows 8.1 No Limited Yes Yes Yes Yes Yes Yes1
Windows 10 Yes Yes Yes Yes Yes Yes Yes Yes1
Windows Server 2008 R2 SP1 Yes2 Yes2 Yes Yes2 Yes Yes Yes Yes1
Windows Server 2012 Yes Yes Yes Yes Yes Yes Yes Yes1
Windows Server 2012 R2 Yes Yes Yes Yes Yes Yes Yes Yes1
Windows Server 2016 Yes Yes Yes Yes Yes Yes Yes Yes

Windows installation and support notes:

1 VM export to Azure works only for x64 editions of operating systems listed. EFI is not supported. Azure VMs do not support Generation 2 Hyper-V VM features. For more information about these features, see "Generation 2 Virtual Machine Overview" in the Microsoft Technet article at https://technet.microsoft.com/library/dn282285.aspx.

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

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 4: Compatible Rapid Recovery components and features by Linux operating system
OS or distribution Agent Agentless Live DVD VM Export
to Azure
Standard / Extended End of Life
Red Hat Enterprise Linux 6.3 - 6.9 Yes Yes Yes Yes November 2020 / TBD
Red Hat Enterprise Linux 7.0 - 7.2 Yes Yes Yes Yes June 2024 / TBD
Red Hat Enterprise Linux 7.3 - 7.4 Yes Yes Yes Yes June 2024 / TBD
CentOS Linux 6.3 - 6.9 Yes Yes Yes Yes November 2020
CentOS Linux 7.0 - 7.2 Yes Yes Yes Yes June 2024
CentOS Linux 7.3 - 7.4 Yes Yes Yes Yes June 2024
Debian Linux 7 Limited2 Limited2 Limited2 No May 2018
Debian Linux 8 Yes Yes Yes Yes May 20208
Debian Linux 9 Yes Yes Yes Yes June 2022
Oracle Linux 6.3 - 6.9 Yes Yes Yes Yes May 2021
Oracle Linux 7.0 - 7.4 Yes Yes Yes Yes July 2024
Ubuntu Linux 12.04 LTS Limited2 Limited2 No Yes April 2017
Ubuntu Linux 12.10, 13.04, 13.10 Limited2 Limited2 No Yes October 2014
Ubuntu Linux 14.04 LTS Yes1 Yes1 Yes1 Yes April 2019
Ubuntu Linux 14.10, 15.04, 15.10 Limited2 Limited2 Limited2 Yes October 2016
Ubuntu Linux 16.04 LTS Yes1 Yes1 Yes1 Yes April 2021
Ubuntu Linux 16.10 Yes1 Yes1 Yes1 Yes October 2017
Ubuntu Linux 17.04 LTS Yes1 Yes1 Yes1 Yes April 2018
Ubuntu Linux 17.10 Limited1, 2 Limited1, 2 Limited1, 2 Yes October 2018
Ubuntu Linux 18.04 LTS Yes1 Yes1 Yes1 Yes April 2023
SUSE Linux Enterprise Server (SLES) 11 SP2 (or later SP) Yes Yes Yes Yes March 2019 / March 2022

SLES 12, 12 SP1 (or later SP)

Yes1 Yes1 Yes1 Yes October 2024 / October 2027

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 OS distribution has reached end of life, and is therefore no longer tested. Support for this OS is therefore limited.

Rapid Recovery Core requirements

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

Table 5: 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 8.1*
  • Microsoft Windows 10
  • Microsoft Windows Server 2008 R2 SP1* (except Core editions)
  • Microsoft Windows Server 2012, 2012 R2* (except Core editions)
  • Microsoft Windows Server 2016 (except Core editions)

Windows operating systems require the Microsoft .NET Framework version 4.6.2 to be installed to run the Rapid Recovery Core service. Additionally, any OS marked with * requires the ASP .NET 4.6.2. role or feature. When installing or upgrading the Core, the installer checks for these components based on the OS of the Core server, and installs or activates them automatically if required. Installing or upgrading .NET software typically requires a system reboot.

The Rapid Recovery Core supports all x64 editions of the Windows OS listed, unless otherwise indicated. The Rapid Recovery Core does not support Windows Server core editions.

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.

For optimal performance, it is recommended that you install the Rapid Recovery Core on more recent operating systems such as Windows 8.1 (or later) and Windows Server 2012 (or later).

Architecture 64-bit only
Memory

8GB RAM or more.

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 and choice of repository technology type. Rapid Recovery supports two primary technology types:

DVM repositories.

Rapid Recovery supports primary storage in a classic 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.
  • Requires a configuration of RAID 6 with 4 usable drives or better for a change rate per hour of up to 10GB. More drives are required 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 input/output requirements.

Tiering repositories. Rapid Recovery releases 6.1 and 6.2 support relocation of recovery points from your DVM repository to secondary storage in a tiering repository.

NOTE: This feature is deprecated. Tiering repositories will not be supported in Rapid Recovery7.0 or later releases.

See Quest knowledge base article 185962, “Sizing Rapid Recovery Deployments” for additional guidance in 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

Requirements for the Rapid Recovery Agent software are described in the following table.

NOTE: Rapid Recovery Agent cannot be deployed to a machine with a Linux operating system installed using the Add-on for Kaseya. If using that add-on, you must install the Agent on a Linux machine manually. For more information, see the Rapid Recovery 6.2 User Guide.

Table 6: Rapid Recovery Agent software requirements
Requirement Details
Operating system The Rapid Recovery Agent software supports 32-bit and 64-bit Windows and Linux operating systems, including the following:
  • Microsoft Windows 8.11, *
  • Microsoft Windows 10
  • Microsoft Windows Server 2008 R2 SP1 (all editions except Windows Server 2008 Core). Follow guidance in Microsoft KB 3033929.
  • Microsoft Windows Server 2012, 2012 R2*
  • Microsoft Windows Server 2016*
  • Red Hat Enterprise Linux (RHEL) 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4
  • CentOS Linux 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4
  • Oracle Linux 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 7.0, 7.1, 7.2, 7.3, 7.4
  • Debian Linux 7, 8, 9
  • Ubuntu Linux 12.04 LTS, 12.10, 13.04, 13.10, 14.04 LTS, 14.10, 15.04, 15.10, 16.04 LTS, 16.10, 17.04, 18.04 LTS2, 3
  • SUSE Linux Enterprise Server (SLES) 11 (SP2 and later), 12 (SP1 and later)

1 Only limited support for Agent as of this release in DVM repositories. Agentless protection is also supported.
2 BTRFS is supported on kernels 3.7 and later.
3 Since Ubuntu Linux versions 12.04 LTS, 12.10, 13.04, 13.10, 14.10, 15.04, 15.10 have reached end of life and are no longer tested, support is limited.
* Any OS marked with * requires the ASP .NET 4.6.2 role or feature.

 

NOTE: Windows operating systems require the Microsoft .NET Framework version 4.6.2 to be installed to run the Rapid Recovery Agent 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 Rapid Recovery Agent software, the installer checks for these components, and installs or activates them automatically if required. Installing or upgrading .NET software typically requires a system reboot.

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

If any operating system listed specifies a service pack (for example, Windows 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 Rapid Recovery Agent software supports Windows Server Core edition installations for Windows Server 2008 R2 , Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016. For Windows Server 2008 R2 Core only, you must have SP1 or later.

The Rapid Recovery Agent software supports the Linux distributions included in this list. Most of the released kernel versions have been tested. File systems supported include ext2, ext3, ext4, and xfs. BTRFS is also supported (only on SLES 12, SLES 12 SP1, and SLES 12 SP2 with kernel version 3.7 or later). For more information, see the Rapid Recovery release 6.2.1 operating system installation and compatibility matrix.

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

NOTE: Native backup of cluster shared volumes is supported on Windows 2008 R2 (SP1 and later) protected machines only.

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

Single processor or higher

Microsoft Exchange Server support

Microsoft Exchange Server 2007 SP1 Rollup 5 or later, Exchange Server 2010, Exchange Server 2013, or Exchange Server 2016.

NOTE: End of life for Exchange Server 2007 was April 11, 2017. This application will not be supported in future releases. Users are advised to move to a current version of Exchange Server.

Microsoft SQL Server support Microsoft SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017 are supported on Windows machines only (no Linux support).

NOTE: End of life for SQL Server 2008 and 2008 R2 is July 9, 2019. Users are advised to move to a current version of SQL Server that is supported by both Microsoft and Quest in advance of that date.

Microsoft SharePoint Server support

Microsoft SharePoint 2007, 2010, 2013, 2016

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

Oracle relational database support Oracle 12c database using Rapid Recovery6.2.1 or later on 64-bit servers running Windows Server 2012 R2 or Windows Server 2016.

Oracle support includes application awareness. You can perform database integrity checks against our volume images using DBVERIFY (a native Oracle utility). Protection of Oracle12c databases is limited to using Volume Snapshot Service (VSS) in the ARCHIVELOG mode.

For more information, see "About protecting Oracle database servers" in the . Rapid Recovery 6.2 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.

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 QorePortal (at https://dataprotection.quest.com/settings/downloads), or theRapid Recovery License Portal (at https://licenseportal.com/Downloads).

Table 7: Local Mount Utility software requirements
Requirement Details
Operating system The Rapid Recovery Local Mount Utility software supports 32-bit and 64-bit Windows operating systems, including the following:
  • Microsoft Windows 8.1*
  • Microsoft Windows 10
  • Microsoft Windows Server 2008 R2 SP1 (all editions except Windows Server 2008 R2 Core)
  • Microsoft Windows Server 2012, 2012 R2*
  • Microsoft Windows Server 2016*
 

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.

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

Single processor or higher

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.
Related Documents