Platform Support

Platform

• Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
• Microsoft Windows Server 20221
• Microsoft Windows Server 2019
• Microsoft Windows Server 2016
• Microsoft Windows Server 2012 R2
• Microsoft Windows Server 2012
• Microsoft Windows Server 2008 R2 SP1
• Azure Stack HCI OS. For the supported versions, see this Veeam KB article.
• Windows 112
• Windows 102

Hypervisor

• Windows Server Semi-Annual Channel (from version 1803 to version 20H2)

• Windows Server Hyper-V 20221
• Windows Server Hyper-V 2019
• Windows Server Hyper-V 2016
• Windows Server Hyper-V 2012 R2
• Windows Server Hyper-V 2012
• Windows Server Hyper-V 2008 R2 SP1
• Azure Stack HCI
• Microsoft Hyper-V Server (free hypervisor) is supported

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)

• Microsoft PowerShell Engine 2.0 or higher (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

Hardware

• Supported virtual hardware versions are 5.0 to 9.2, and 10.01 (valid for Hyper-V 2016 to 20221).
• Both Generation 1 and 2 virtual machines are supported, including 64 TB VHDX disks.
• Pass-through virtual disks and guest disks connected through in-guest FC or iSCSI initiators are not supported for host-based backup. VMs with pass-through disks cannot be snapshotted, which prevents snapshot-based backup. In-guest connected disks are skipped from processing automatically. If backup of these VMs/disks is required, use agent-based backup.
• [For Hyper-V Server 1803 or later] Backup of VMs with VMPmemController is not supported.
• [For Hyper-V 2016 and later] Veeam Backup & Replication does not support processing of VMs with shared VHDX disks. You must change the disk format to VHD Set (VHDS).
• [For Hyper-V 2016 and later] VMs with pass-through virtual disks cannot be processed due to Hyper-V 2016 checkpoints limitation.
• [For Hyper-V 2012 R2] Veeam Backup & Replication backs up shared VHDX disks in a crash-consistent state.
• [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.

OS

All operating systems supported by Hyper-V.

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).

Microsoft Windows

• FAT, FAT32
• NTFS
• ReFS (ReFS is supported only if Veeam Backup & Replication is installed on Microsoft Windows Server 2012 or later).

Windows file-level restore to original location is supported for Microsoft Windows 2008/Windows Vista or later except Nano Server.

Linux

• ext2, ext3, ext4
• ReiserFS
• JFS
• XFS
• Btrfs

DRBD (Distributed Replicated Block Devices) are not supported.

BSD

UFS, UFS2

Mac

HFS, HFS+ (volumes up to 2 TB)

Solaris

• UFS
• ZFS (except any pool versions of Oracle 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.