Platform Support

Make sure platforms that you plan to use for various operations are supported.

Note

The information on this page is valid as of the date of the last page update.

Veeam Backup & Replication provides support for the following versions of the Microsoft Hyper-V platform.

Virtual Infrastructure

Specification

Requirement

Platform

  • Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
  • 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 111
  • Windows 101

Hypervisor

  • Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
  • Windows Server Hyper-V 20222
  • 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.

Depending on your Windows Server version, some additional hotfixes 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 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

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.

2 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article.

VMs

Specification

Requirement

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

1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article.

Mind 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. Bear it in mind 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.
  • Guest processing (which includes application-aware processing and indexing) is supported for 64-bit versions of the following Linux operating systems:
  • CentOS 7 to 8.51
  • CentOS Stream
  • Debian 9.0 to 11.01
  • Fedora 30 to 351
  • openSUSE Leap 15.2 and 15.31, Tumbleweed
  • Oracle Linux 6 (UEK3) to 8.3 (UEK R6 U21)
  • Oracle Linux 6 to 8.51 (RHCK)
  • RHEL 6.0 to 8.71
  • SLES 11 SP4, 12 SP1–SP5, 15 SP0–SP31
  • Ubuntu: 14.04 LTS, 16.04 LTS, 18.04 LTS, 19.10, 20.04 LTS, 21.041, and 21.101

1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article.

Guest OS File Recovery 

OS

Supported File Systems

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.

 

For other requirements and limitations of guest OS file restore, see Requirements and Limitations.

File Servers

Veeam Backup & Replication supports backup of files and folders from the file servers managed by the following operating systems:

1 This version requires Veeam Backup & Replication 11a P20220302 (build 11.0.1.1261 P20220302). For more information, see this Veeam KB article.

NAS Backup Support

Veeam Backup & Replication supports backup of file shares from the following sources:

Consider the following requirements and limitations:

In NFS settings of the source file share, you must explicitly specify what servers will have access to the file share.

  • SMB file share must run on SMB version 1.x, 2.x or 3.x.
  • To support the VSS for SMB File Shares feature, make sure that requirements listed in this Veeam KB article are met.
  • To correctly back up SACL (Ownership) files and folders from the SMB file share and restore them:
  1. When you are specifying access settings for the SMB file share, select the This share requires access credentials check box.
  2. Make sure that the account you use to access the file share is either added to the Backup Operators group or has the SeBackupPrivilege and SeRestorePrivilege privileges in Windows Server on the file share.

For more information on NAS backup, see NAS Backup Support.

Network

Consider the following requirements and limitations: