Veeam Backup & Replication provides support for the following versions of the Microsoft Hyper-V platform.
- Microsoft Windows Server 2019
- Microsoft Windows Server 2016
- Microsoft Windows Server Semi-Annual Channel (including version 1903)
- Microsoft Windows Server 2012 R2
- Microsoft Windows Server 2012
- Microsoft Windows Server 2008 R2 SP1
- Windows Server Hyper-V 2019
- Windows Server Hyper-V 2016
- Windows Server Semi-Annual Channel (including version 1903)
- Windows Server Hyper-V 2012 R2
- Windows Server Hyper-V 2012
- Windows Server Hyper-V 2008 R2 SP1
- Microsoft Hyper-V Server (free hypervisor) is supported
Depending on your Windows Server version, some additional hot fixes not included in the Windows Update must be installed. For more information, see this Veeam KB article.
Management Server (optional)
- Microsoft PowerShell Engine 2.0 (optional, enables networkless guest processing)
- Microsoft System Center Virtual Machine Manager 2019
- Microsoft System Center Virtual Machine Manager 1807
- Microsoft System Center Virtual Machine Manager 1801
- Microsoft System Center Virtual Machine Manager 2016
- Microsoft System Center Virtual Machine Manager 2012 R2
- Microsoft System Center Virtual Machine Manager 2012 SP1
- Microsoft System Center Virtual Machine Manager 2008 R2 SP1
- Supported virtual hardware versions are 5.0–9.0 (valid for Hyper-V 2016–2019).
- Both Generation 1 and 2 virtual machines are supported, including 64 TB VHDX disks.
- Pass-through virtual disks and guest disks connected via in-guest FC or iSCSI are skipped from processing.
- [For Hyper-V 2016–2019] VMs with pass-through virtual disks cannot be processed due to Hyper-V 2016 checkpoints limitation.
- All operating systems supported by Hyper-V*.
- Application-aware processing is supported for Microsoft Windows 2003 SP2 and later except Nano Server, due to the absence of VSS framework.
- 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.
- Microsoft Windows file-level restore option is supported on NTFS, FAT, FAT32 and ReFS file systems (ReFS is supported only if Veeam Backup & Replication is installed on Microsoft Windows Server 2012 or later)
To restore files from non-Microsoft Windows guests (Linux, Solaris, or BSD), use the multi-OS File-Level Restore wizard.
Hyper-V integration components (required for application-aware processing).
* 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.
** [For Hyper-V 2012 R2 and earlier] Backup and replication of VMs whose data resides on a Hyper-V host volume of 64 TB and larger is not supported.
Supported File Systems
- FAT, FAT32
- ReFS (ReFS is supported only if Veeam Backup & Replication is installed on Microsoft Windows Server 2012 or later).
- ext2, ext3, ext4
DRBD (Distributed Replicated Block Devices) are not supported.
HFS, HFS+ (volumes up to 2 TB)
- ZFS (except any pool versions of Oracle Solaris)
The FLR 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.
Consider the following:
- You cannot restore pipes and other file system objects. File-level restore supports recovery of files and folders only.
- The multi-OS File-Level Restore wizard works not only with basic disks, but also Linux LVM (Logical Volume Manager) and ZFS pools. Encrypted LVM volumes are not supported.
Domain names of all managed servers added to the Veeam backup infrastructure and machines you want to back up must be resolvable into IPv4 addresses.