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 release 6.4 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.
| 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 Server 2012 |
Yes4 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes2 |
|
Windows Server 2012 R2 |
Yes4 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes2 |
|
Windows Server 2016 |
Yes4 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes2 |
|
Windows Server 2019 |
Yes4 |
Yes5 |
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. 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.
3 Microsoft discontinues support for Windows Server 2008 R2 on January 14, 2020. After this date, Rapid Recovery continues limited support for Windows Server 2008 R2 (SP1 only) in release 6.5. Customers are advised to migrate to newer supported versions to continue backing up data using Rapid Recovery.
4 Rapid 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.
5Rapid Recovery does not support protection of ReFS volumes running Windows Server 2019. For more information, see the topic "Support for Windows Server 2019" in Rapid Recovery Release Notes.
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.
| OS Version or distribution | Agent | Agentless | Live DVD | VM Export to Azure |
|---|---|---|---|---|
|
Red Hat Enterprise Linux (RHEL) 6.4 - 6.10 |
Yes |
Yes |
Yes |
Yes |
|
RHEL 7.0 - 7.8 |
Yes |
Yes |
Yes |
Yes |
|
RHEL 8.0 - 8.2 |
Yes |
Yes |
Yes |
Yes |
|
CentOS Linux 6.4 - 6.10 |
Yes |
Yes |
Yes |
Yes |
|
CentOS Linux 7.0 - 7.8 |
Yes |
Yes |
Yes |
Yes |
|
CentOS Linux 8.0-8.2 |
Yes |
Yes |
Yes |
Yes |
|
Debian Linux 9 |
Yes |
Yes |
Yes |
Yes |
|
Debian Linux 10 |
Yes |
Yes |
Yes |
Yes |
|
Oracle Linux 6.4 - 6.10 |
Yes |
Yes |
Yes |
Yes |
|
Oracle Linux 7.0 - 7.8 |
Yes |
Yes |
Yes |
Yes |
|
Oracle Linux 8.0-8.2 |
Yes |
Yes |
Yes |
Yes |
|
Ubuntu Linux 16.04 LTS |
Yes1 |
Yes1 |
Yes1 |
Yes |
|
Ubuntu Linux 18.04 LTS |
Yes1 |
Yes1 |
Yes1 |
Yes |
|
Ubuntu Linux 19.04, 19.10 |
Limited2 |
Limited2 |
Limited2 |
Limited2 |
|
Ubuntu Linux 20.04 LTS |
Yes |
Yes |
Yes |
Yes |
|
SUSE Linux Enterprise Server (SLES) 11 SP4 (or later SP) |
Yes1 |
Yes1 |
Yes |
Yes |
|
SLES 12 SP3 |
Yes1 |
Yes1 |
Yes1 |
Yes1 |
|
SLES 12 SP4 |
Yes |
Yes |
Yes |
Yes |
|
SLES 15 SP1 |
Yes3 |
Yes3 |
Yes3 |
Yes3 |
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.
3 This OS distribution (and SUSE Linux Desktop) fully supported when using listed service packs; versions using earlier SPs are in limited support only.
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.
| 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):
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. 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, 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. | ||
|
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:
| ||
|
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
| ||
|
Network hardware |
Use network cables with the appropriate rating to obtain the expected bandwidth.
|
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.
| 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:
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 Microsoft discontinues support for Windows Server 2008 R2 on January 14, 2020. After this date, Rapid Recovery continues limited support for Windows Server 2008 R2 (SP1 only) in release 6.5. Customers are advised to migrate to newer supported versions to continue backing up data using Rapid Recovery. 4 Since this OS has reached end of life, only limited support for Agent in this release. Agentless protection is also supported. 5 ReFS volumes not supported for protection on 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. 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 versions 2008 R2 , 2012, 2012 R2, and 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. 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:
For more information, see the Rapid Recovery release 6.5 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 , 2019
| ||
| Oracle relational database support |
Rapid Recovery Agent supports the following versions of Oracle relational database management systems (RDBMS):
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
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: This matrix is provided to educate users on compatibility. Quest does not support operating systems that have reached end of life.