Microsoft Hyper-V
Hyper-V Virtual Infrastructure
Veeam Backup & Replication provides support for the following versions of the Microsoft Hyper-V platform.
Specification | Requirement |
|---|---|
Platform |
For the supported versions, see this Veeam KB article.
|
Hypervisor |
Server Core installations are fully supported. Microsoft Nano Server with Hyper-V role installed cannot be added to the backup infrastructure as a managed server and no role can be assigned to it. However, you can back up and replicate such servers, but application-aware processing is not supported for them. Note that you must keep your servers up-to-date. |
Management Server (optional) |
|
1 Windows 10/11 is supported only as a target for Instant Recovery and as a host on which a virtual lab for SureBackup jobs can be created.
Specification | Requirement |
|---|---|
Hardware |
|
OS | All operating systems supported by Hyper-V. Guest processing is supported for OS versions released before the Veeam Backup & Replication build release date.
Note: You can back up VMs of Hyper-V clusters in rolling upgrade. However, Veeam Backup & Replication does not use the Resilient Changed Tracking mechanism in such scenario. To perform backup with RCT enabled, make sure your Microsoft Hyper-V environment meets these requirements. It is recommended to complete the rolling upgrade within four weeks. For more information, see Microsoft Docs. |
Software | Hyper-V integration components (optional, required for application-aware processing). |
Consider the following:
- [For Microsoft Windows 2003 and Nano Server] Application-aware processing is not supported due to the absence of VSS framework.
- [For Hyper-V 2016 and later] Application-aware processing for Microsoft Windows VMs with volumes larger than 64 TB is not supported, because Veeam Backup & Replication uses the Microsoft Software Shadow Copy Provider to create a volume shadow copy during the backup or replication. For more information, see this Microsoft KB article.
- [For Hyper-V 2016 and later] Veeam Backup & Replication cannot interact with the guest OS of a shielded VM and get information about its OS, IP address and so on. For this reason, the following operations are not supported for shielded VMs:
- Application-aware image processing
- Restore of VM guest OS files to the original location
- Restore of application items to the original location
- [For Hyper-V 2016 and later] Shielded VMs can run only on trusted hosts guarded with the Host Guardian Service. Consider that when selecting a target host for VM replication or VM restore. If the target host is not guarded with the same Host Guardian Service as the source host, you will not be able to power on the replicated or restored VM.
- The two previous limitations also apply to Generation 1 of Microsoft Hyper-V VMs that use Key Storage Drive. For more information about Key Storage Drive, see Microsoft Docs.
File-level restore is supported for the following file systems, including Microsoft Windows LDM dynamic disks and Linux LVM:
OS | Supported File Systems |
|---|---|
Microsoft Windows |
Windows file-level restore to original location is supported for the following Microsoft Windows operating systems except Nano Server:
|
Linux |
DRBD (Distributed Replicated Block Devices) are not supported. |
BSD | UFS, UFS2 |
Mac | HFS, HFS+ (volumes up to 2 TB) |
Solaris |
The helper appliance uses module ZFSonLinux version 0.7.0. For this reason, Veeam Backup & Replication supports only those versions of pools and features that are available in ZFSonLinux version 0.7.0. |
For other requirements and limitations of guest OS file restore, see Requirements and Limitations.