Rapid Recovery 6.3 - System Requirements Guide

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 (VMs), regardless of origin. Rapid Recovery lets you create backup archives to a wide range of supported systems including archiving to the cloud. 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).
• Live Recovery. With our Live Recovery feature, you have instant access to critical data first, while remaining restore operations complete in parallel. You can use Live Recovery to restore data from a recovery point of any non-system volume of a Windows machine, physical or virtual. The machine must be protected by Rapid Recovery Agent. Live Recovery is not supported for agentlessly protected machines, Linux machines, or cluster-shared volumes.
• 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 Rapid Recovery Core Console.
• Virtual machine export. Rapid Recovery supports one-time virtual export, letting you generate a VM from a recovery point; and virtual standby, in which the VM you generate is continually updated after each backup. Compatible VM hypervisors include vCenter/ESXi, VMware Workstation, Hyper-V, VirtualBox, and Azure. 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 software agent installed. Host-based protection supports installing Rapid Recovery Agenton a Microsoft Hyper-V host only, letting you agentlessly protect all its guest VMs.
• Application support. Rapid Recovery is built with application support. When you protect SQL Server or Microsoft Exchange machines (whether using Rapid Recovery Agent or agentless protection), the backup snapshots captured 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 checks (for SQL Server) and database checksum and mountability checks (for Exchange Server). If you protect Oracle 12c servers with Rapid Recovery Agent, you can also perform DBVERIFY database integrity checks.

See the following resources for more information about Rapid Recovery.

• The Rapid Recovery product support website at https://support.quest.com/rapid-recovery/.
• The documentation website at https://support.quest.com/rapid-recovery/technical-documents/.

For running Rapid Recovery, Quest requires a minimum network infrastructure of 1 gigabit Ethernet (GbE) for efficient performance. Quest recommends 10GbE networks for robust environments. 10GbE networks are also recommended when protecting servers featuring large volumes (5TB or higher).

If multiple network interface cards (NICs) are available on the Core machine that support NIC teaming (grouping several physical NICs into a single logical NIC), and if the switches on the network allow it, then using NIC teaming on the Core may provide extra performance. In such cases, teaming up spare network cards that support NIC teaming on any protected machines, when possible, may also increase overall performance.

If the Core uses iSCSI or Network Attached Storage (NAS), Quest recommends using separate NIC cards for storage and network traffic, respectively.

Use network cables with the appropriate rating to obtain the expected bandwidth. Quest recommends testing your network performance regularly and adjusting your hardware accordingly.

These suggestions are based on typical networking needs of a network infrastructure to support all business operations, in addition to the backup, replication, and recovery capabilities Rapid Recovery provides.

The General Data Protection Regulation (GDPR) is legislation crafted to strengthen and unify data protection for all individuals within the European Union (EU). It also addresses the export of personal data outside the EU, which makes it relevant to software manufacture in the US and other countries. It updates rules governing the handling of individuals' personal data. GDPR is being widely adopted throughout the software industry.

To comply with the GDPR, the collection of any personally identifiable information (PII) by Rapid Recovery has been carefully considered. Data collection has been streamlined, and the information collected and how it is used is clearly documented.

When installing the Rapid Recovery Core or running the Rapid Recovery Info Gathering Tool, you are provided a description of the information Rapid Recovery collects and our purposes for collecting the information.

If you accept the stated use of personal data, you can then associate a license (running in standard "phone-home" mode) with your Core. If you choose to decline the use of personal data described in the privacy policy, you must request a special "non-phone-home" license. After you receive that license and associate it with your Core, your PII will not be used, and certain functions (auto update, and enabling integration between the Core and the QorePortal) are disabled.

Regardless of the privacy option you selected during installation, from the Core General setting Agree to use of personal data, you can change this setting. To switch between phone-home and non-phone-home modes in either direction, you must have access to the appropriate license.

For more information about the GDPR, see the EU General Data Protection Regulation website at https://eugdpr.org/the-regulation/. For more information about managing your privacy, see the following topics in the Rapid Recovery 6.3 User Guide:

• Certain business rules apply when changing between phone-home and non-phone-home mode using the Agree to use of personal data general setting. For more information, see the topic "Configuring Core general settings."
• To see what information Rapid Recovery collects, in which circumstances, and why the information is collected, see "How Rapid Recovery uses personal information."
• To see what functions you cannot perform when using a non-phone-home license, see the topic "Non-phone-home license restrictions."
• To download a phone-home license, log into the Rapid Recovery License Portal. From the navigation menu, click Licensing, and from the drop-down menu on the top right, select License Key.
• To learn how to obtain a license in non-phone-home mode, see the topic "Obtaining and using non-phone-home licenses."