Rapid Recovery supports taking snapshots of all dynamic and basic volumes. Rapid Recoveryy also supports exporting simple dynamic volumes that are on a single physical disk. As their name implies, simple dynamic volumes are not striped, mirrored, spanned, or RAID volumes.
The behavior for virtual export of dynamic disks differs, based on whether the volume you want to export is protected by the Rapid Recovery Agent software, or is a VM using agentless protection. This is because non-simple or complex dynamic volumes have arbitrary disk geometries that cannot be fully interpreted by Rapid Recovery Agent.
When you try to export a complex dynamic disk from a machine with the Rapid Recovery Agent software, a notification appears in the user interface to alert you that exports are limited and restricted to simple dynamic volumes. If you attempt to export anything other than a simple dynamic volume usingRapid Recovery Agent, the export job fails.
In contrast, dynamic volumes for VMs you protect agentlessly are supported for protection, virtual export, restoring data, and BMR, and for repository storage, with some important restrictions. For example:
Caution: When exporting a dynamic volume that spans multiple disks, you must export the dynamic disks with the original system volumes to preserve the disk types. |
Repository storage: Additionally, Rapid Recoveryy supports the creation of repositories on complex dynamic volumes (striped, mirrored, spanned, or RAID). The file system of the machine hosting the repository must be NTFS or ReFS.
To protect your cluster properly, you must have installed the Rapid Recovery Agent software on each of the machines or nodes in the cluster. Rapid Recovery supports the application versions and cluster configurations listed in the following table.
Application | Application Version and Related Cluster Configuration | Windows Failover Cluster |
---|---|---|
Microsoft Exchange Server | 2007 Single Copy Cluster (SCC)
2007 Cluster Continuous Replication (CCR) |
2008 R2 |
2010 Database Availability Group (DAG) | 2008 R2 | |
2013, 2016 DAG | 2008 R2 SP1, 2012, 2012 R2 | |
Microsoft SQL Server | 2005 | 2008 R2 |
2008, 2008 R2 SCC | 2008 R2, 2012, 2012 R2 | |
2012, 2014 SCC | 2008 R2, 2012, 2012 R2 | |
2012, 2014, 2016, 2017 Availability Groups | 2012, 2012 R2, 2016 |
|
NOTE: If using SQL Server 2012 or higher with always-on Availability Groups, you must have .NET Framework 3.5 SP1 enabled on the protected server. |
|
NOTE: As of Rapid Recovery 6.2, Windows 2008 is no longer supported. However, protection of a Windows 2008 cluster is supported if it has a release 6.1.x Rapid Recovery Agent installed. |
The supported disk types include:
The supported mount types include:
For Agent-based support, Rapid Recovery only supports direct protection and restore of cluster-shared volumes (CSVs) running on Windows Server 2008 R2.
Rapid Recovery 6.1 and later offers agentless support of virtual machines residing on Hyper-V CSVs (not of the CSVs themselves). Any feature listed as supported below requires Rapid Recovery Agent to be installed on each node of the cluster. You can then agentlessly protect and restore supported VMs hosted on Hyper-V clusters installed on Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016.
In addition, Rapid Recovery release 6.1 and later supports virtual export to Hyper-V CSVs installed on Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016. For information about supported hypervisors, see Hypervisor requirements.
The following table depicts current Rapid Recovery support for VMs residing on cluster-shared volumes.
Operating System | Protect1 and Restore2 VMs on a Hyper-V CSV | Virtual Export to Hyper-V CSV | Protect1 and Restore3 of CSV | ||||||
---|---|---|---|---|---|---|---|---|---|
CSV Operating System | Rapid RecoveryVersion | Rapid Recovery Version | Rapid Recovery Version | ||||||
6.0.x | 6.1.x | 6.2.x | 6.0.x | 6.1.x | 6.2.x | 6.0.x | 6.1.x | 6.2.x | |
Windows Server 2008 R2 | No | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
Windows Server 2012 | No | Yes | Yes | Yes | Yes | Yes | No | No | No |
Windows Server 2012 R2 | No | Yes | Yes | Yes | Yes | Yes | No | No | No |
Windows Server 2016 | No | Yes | Yes | No | Yes | Yes | No | No | No |
1 Protect includes protection, replication, rollup, mount, and archiving.
2 Restore includes file-level restore, volume-level restore, bare metal restore, and virtual export.
3 Restore includes file-level restore, volume-level restore, and bare metal restore.
Install the Rapid Recovery Core on a dedicated Windows 64-bit server.
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 support contract can manage two or more Cores from the QorePortal.
For each physical machine you want to protect in a Rapid Recovery Core, install the Rapid Recovery Agent software version appropriate to that machine's operating system. You can also protect virtual machines (VMs) on your Core after installing using the Agent software. Optionally, you can use the Rapid Snap for Virtual feature to protect VMs agentlessly. This approach has some limitations. For more information, see the topic "Understanding Rapid Snap for Virtual" in the Rapid Recovery User Guide.
Before installing Rapid Recovery, 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: Quest does not support running the Rapid Recovery Core on Windows Core operating systems, which offer limited server roles. This includes all editions of Windows Server 2008 Core, Windows Server 2008 R2 Core, Windows Server 2012 Core, Windows Server 2012 R2 Core, and Windows Server 2016 Core. |
|
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. (This recommendation does not apply to Quest DL series backup and recovery appliances.) |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center