Make sure platforms that you plan to use for various operations are supported.
The information on this page is valid as of the date of the last page update.
Veeam Backup & Replication supports the following VMware vSphere platforms.
For more information on GCVE support, see this Veeam KB article.
For more information on IBM Cloud for VMware Solutions support, see this Veeam KB article.
For more information on AVS support, see this Veeam KB article.
For more information on Oracle Cloud VMware Solutions support, see this Veeam KB article.
For more information on VMware Cloud on AWS support, see this Veeam KB article.
For more information on VMware Cloud on Dell support, see this Veeam KB article.
This platform is supported as individual VMware software components. VMware components listed on this page can be part of VCF. For the information on the correspondence of VMware components to the VCF version, see this VMware KB article.
Free ESXi is not supported. Veeam Backup & Replication leverages vSphere and vStorage APIs that are disabled by VMware in free ESXi.
1 This version requires Veeam Backup & Replication 12 P20230412 (build 126.96.36.1990 P20230412). For more information, see this Veeam KB article.
The following infrastructure requirements apply only when you protect VMs with Continuous Data Protection (CDP):
- VMware vSphere edition must be VMware vSphere Standard Edition or higher. VMware vSphere Essentials Kits editions are not supported.
- vCenter Server is required. Standalone ESXi hosts are not supported.
- Minimum ESXi version required is 6.5 U2.
- Minimum 16GB RAM is required for source and target ESXi hosts.
- Continuous Data Protection for VMware Cloud Director supports target ESXi hosts version 7.0 or later. Target hosts of version 6.5 and 6.7 are not supported.
- All hosts in a cluster must be of the same major version: 7.x or 6.x (6.5, or 6.7, or a combination of 6.5 and 6.7 is supported). In turn, all clusters managed by the same vCenter Server must also be of the same major version.
- You can replicate data between vCenter Servers of different versions. However, if you replicate data within one vCenter Server, and this vCenter Server includes hosts of different versions (6.5 and 6.7), your CDP policy may fail. In this case, go to the vSphere Client and delete the Veeam CDP Replication VM storage policy applied to each VM included in the CDP policy. For more information on how to delete a VM storage policy, see VMware Docs. Then, in the Veeam Backup & Replication console, relaunch the CDP policy.
- The maximum number of disks per ESXi host is 500.
- Backup server, VMware CDP proxies, vCenter Server and ESXi hosts must be able to resolve each other DNS names.
- VMware Cloud on AWS is not supported.
For more information on Veeam CDP, its requirements and limitations, see Continuous Data Protection (CDP).
Network shares and mount points targeted to 3rd party storage devices are also skipped as these volumes/disks are not visible in the VM configuration file.
RDM virtual disks in virtual mode are supported to create backups based on VMware Changed Block Tracking technology, although there are some restrictions on the virtual disk restore operation. To learn more about them, see Restoring Virtual Disks.
Note that persistent agent components can be installed only on 64-bit versions of these Linux operating systems.
VMware Cloud Director
VMware Cloud Director 10.1.x to 10.4.x
Note that if your backup server is based on Microsoft Windows Server 2012 R2 or an earlier version, VMware Cloud Director servers cannot be added or used.
Supported File Systems
Windows file-level restore to original location is supported for Microsoft Windows 2008/Windows Vista or later except Nano Server.
DRBD (Distributed Replicated Block Devices) are not supported.
HFS, HFS+ (volumes up to 2 TB)
Micro Focus OES
AD-enabled NSS volumes on Open Enterprise Server 2015 are supported. Besides restore of standard file and folder permissions, restore of NSS trustee rights on files and folders is supported.
File-level restore is supported for the following OSes:
The helper appliance uses module ZFSonLinux version 2.1.5. For this reason, Veeam Backup & Replication supports only those versions of pools and features that are available in ZFSonLinux version 2.1.5.
For other requirements and limitations of guest OS file restore, see Requirements and Limitations.
Veeam Backup & Replication supports backup of files and folders from the file servers managed by the following operating systems:
- 64-bit versions of the Microsoft Windows operating systems:
- Microsoft Windows Server 2022
- Microsoft Windows Server 2019
- Microsoft Windows Server 2016
- Microsoft Windows Server 2012 R2
- Microsoft Windows Server 2012
- Microsoft Windows 11 (versions 21H2, 22H2)
- Microsoft Windows 10 (from version 1909 to version 22H2)
- Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)
- 64-bit versions of the Linux operating systems:
- CentOS 7.x
- Debian 10.0 to 11.0
- Oracle Linux 7 (UEK3) to 9 (UEK R7)
- Oracle Linux 7 to 9 (RHCK)
- RHEL 7.0 to 9.1
- SLES 12 SP4 or later, 15 SP1 or later
- Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS
Veeam Backup & Replication supports backup of file shares from the following sources:
- Microsoft Windows- or Linux-managed server
- Enterprise NAS systems: NetApp Data ONTAP, Lenovo ThinkSystem DM Series, Dell PowerScale (formerly Isilon), Nutanix Files Storage
- NFS file shares
- SMB file shares
Consider the following requirements and limitations:
- Only 64-bit versions of operating systems are supported for Microsoft Windows- or Linux-managed server file share.
- Backup of file shares on Linux hosts added with single use credentials is not supported.
- NFS file share must run NFS protocol version 3 or 4.1.
- Network shares and files on them targeted to 3rd party storage devices may have difficulties being restored, or may not be restored at all. Such shares/files often rely upon specific software/OS filters to be recalled from the alternate storage location, which is not available when performing a file share data recovery. See your software vendor documentation to learn how to back up such files.
- Anonymous or AD/Kerberos authentication is not supported for access to file shares through NFS.
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:
- When you are specifying access settings for the SMB file share, select the This share requires access credentials check box.
- 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.
Consider the following requirements and limitations:
- Names of port groups/segments/networks must be unique.
- Virtual Lab does not support NSX-T.
- VMware NSX-T 2.3 or later is supported with N-VDS for VMware vSphere and VMware Cloud on AWS/Dell.
- VMware NSX-T 3.0 or later is supported with VDS for VMware vSphere and VMware Cloud on AWS/Dell.
- VMware NSX-V is supported (see details on the support of vSphere and VMware Cloud version above).