Unified Extensible Firmware Interface (UEFI) is a replacement for Basic Input/Output System (BIOS). For Windows systems, UEFI uses the Extensible Firmware Interface (EFI) system partitions that are handled as simple FAT32 volumes.
Protection and recovery capabilities are available in Rapid Recovery for EFI system partitions with the following operating systems:
- Windows: Windows versions 8*, 8.1*, 10, 11; Windows Server versions 2012, 2012 R2, 2016, 2019, 2022.
|
|
NOTE: Operating systems marked * have reached EOL; support is limited. |
- Linux: All supported versions of Linux.
Rapid Recovery also supports the protection and recovery of Resilient File System (ReFS) volumes for Windows 10, Windows 11, Windows Server versions 2012, 2012 R2, 2016, 2019, and 2022.
|
|
NOTE: When using ReFS volumes for Windows Server 2019, use only the latest version of Windows Server 2019 with the most recent Windows updates. Rapid Recovery Core may block volumes that use older versions of Windows Server 2019 from protection. |
Rapid Recovery supports taking snapshots of all dynamic and basic volumes. Rapid Recovery 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:
- Protection: In the case when a dynamic volume spans multiple disks, you must protect those disks together to maintain the integrity of the volume.
- Virtual export: You can export complex dynamic volumes such as striped, mirrored, spanned, or RAID volumes from an ESXi or Hyper-V host using agentless protection. However, the volumes are exported at the disk level, with no volume parsing. For example, if exporting a dynamic volume spanned across two disks, the export will include two distinct disk volumes.
|
|
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. |
- Restoring data: When restoring a dynamic volume that spans multiple disks, you must restore the dynamic disks with the original system volumes to preserve the disk types. If you restore only one disk, you will break the disk configuration.
- Repository storage: Additionally, Rapid Recovery 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, the Rapid Recovery Agent software must be installed on each of the machines or nodes in the cluster. Rapid Recovery supports the application versions and cluster configurations listed in the following table.
Table 1: Supported application versions and cluster configurations
| Microsoft Exchange Server1 |
Exchange 2013, 20162, 2019 |
Windows Server 20122, 2012 R2 |
| Microsoft SQL Server |
SQL Server 2012, 2014 SCC |
Windows Server 20122, 2012 R2 |
| SQL Server 20122, 2014, 20162, 2017, 2019 Availability Groups |
Windows Server 2012, 2012 R2, 20162, 2019 |
1 Microsoft Exchange support includes both standalone and Database Availability Group (DAG) for all versions listed.
2Rapid Recovery does not support cluster shared volumes (CSVs) for all Windows versions. For more information, see Support for Cluster Shared Volumes.
Live migration is a Hyper-V feature of Windows Server which lets users move running VMs from one Hyper-V host to another. Rapid Recovery supports Hyper-V live migration when moving VMs between nodes in a cluster. Live migration between separate hosts (a Hyper-V 2016 feature) is not supported with Rapid Recovery.
If using Rapid Snap for Virtual agentless protection, a supported version of Rapid Recovery Agent must be installed on the Hyper-V host. If using agent-based protection, Rapid Recovery Agent must be installed on each node in a protected Hyper-V cluster, but is not required on the host.
If using Rapid Snap for Virtual agentless protection, a supported version of Rapid Recovery Agent must be installed on the Hyper-V host. If using agent-based protection, Rapid Recovery Agent must be installed on each node in a protected Hyper-V cluster, but is not required on the host.
The supported disk types include:
- GUID partition table (GPT) disks greater than 2 TB
- Master Boot Record (MBR) disks less than 2 TB
The supported mount types include:
- Shared drives that are connected as drive letters (for example, D:)
- Simple dynamic volumes on a single physical disk (not striped, mirrored, or spanned volumes)
- Shared drives that are connected as mount points
|
|
NOTE: Rapid Recovery Core does not support mount types of complex dynamic disks for agentless protection. |
Direct protection and restore of the actual cluster-shared volumes (CSVs) themselves in Rapid Recovery is only possible with Windows Server 2008 R2 SP11, and is deprecated. This feature is not expected to be supported in future releases of Rapid Recovery.
Currently supported versions of Rapid Recovery offer agentless support only 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 versions 2008 R2 SP11, 2012, 2012 R2, 2016, and 2019.
In addition, Rapid Recovery Core supports virtual export to Hyper-V CSVs installed on currently supported Windows operating systems, including Windows Server versions 2008 R2 SP11, 2012, 2012 R2, 2016, and 2019. For information about supported hypervisors, see Hypervisor requirements.
The following table depicts current Rapid Recovery support for cluster-shared volumes.
| Operating System |
Protect2 and Restore3 VMs on a Hyper-V CSV |
|
Virtual Export to Hyper-V CSV |
|
Protect2 and Restore4 CSV Directly |
|
| CSV Operating System |
Rapid Recovery Version |
Rapid Recovery Version |
Rapid Recovery Version |
|
6.5 |
6.6 |
6.7 |
6.8 |
6.5 |
6.6 |
6.7 |
6.8 |
6.5 |
6.6 |
6.7 |
6.8 |
| Windows Server 2008 R2 SP11 |
No |
No |
No |
No |
No |
No |
No |
No |
No |
No |
No |
No |
| Windows Server 2012 |
Limited5 |
Limited5 |
Limited5 |
Limited5 |
Yes |
Yes |
Yes |
Yes |
No |
No |
No |
No |
| Windows Server 2012 R2 |
Limited5 |
Limited5 |
Limited5 |
Limited5 |
Yes |
Yes |
Yes |
Yes |
No |
No |
No |
No |
| Windows Server 2016 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
No |
No |
No |
| Windows Server 2019 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
No |
No |
No |
| Windows Server 2022 |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
No |
No |
No |
No |
|
Notes:
1 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.8. Customers are advised to migrate to newer supported versions to continue backing up data using Rapid Recovery.
2 Protect includes protection, replication, rollup, mount, and archiving.
3 Restore includes file-level restore, volume-level restore, bare metal restore, and virtual export.
4 Restore includes file-level restore, volume-level restore, and bare metal restore.
5 These Windows Server versions have reached standard end of life. Support for these OS is therefore limited. |
