Supported Platforms, Applications and Workloads

Note

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

Veeam Backup & Replication supports the following virtualization platforms:

VMware vSphere
Microsoft Hyper-V
Azure Local (formerly Azure Stack HCI)
Proxmox VE
Nutanix AHV

VMware vSphere Platform

VMware vSphere Virtual Infrastructure

Veeam Backup & Replication supports the following VMware vSphere platforms.

Specification	Requirement
Platform	vSphere 8.0 (up to 8.0 U3) vSphere 7.x VMware Cloud Foundation (VCF) 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. Google Cloud VMware Engine (GCVE) For more information on GCVE support, see this Veeam KB article. IBM Cloud for VMware Solutions For more information on IBM Cloud for VMware Solutions support, see this Veeam KB article. Microsoft Azure VMware Solution (AVS) For more information on AVS support, see this Veeam KB article. Oracle Cloud VMware Solution For more information on Oracle Cloud VMware Solutions support, see this Veeam KB article. VMware Cloud on AWS For more information on VMware Cloud on AWS support, see this Veeam KB article. VMware Cloud on Dell
Hypervisor	ESXi 8.0 (up to 8.0 U3) ESXi 7.x Free ESXi is not supported. Veeam Backup & Replication leverages vSphere and vStorage APIs that are disabled by VMware in free ESXi.
Management Server (optional)	vCenter Server 8.0 (optional) (up to 8.0 U3) vCenter Server 7.x (optional)

Specification

Requirement

Platform

vSphere 8.0 (up to 8.0 U3)
vSphere 7.x
VMware Cloud Foundation (VCF)

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.

Google Cloud VMware Engine (GCVE)

For more information on GCVE support, see this Veeam KB article.

IBM Cloud for VMware Solutions

For more information on IBM Cloud for VMware Solutions support, see this Veeam KB article.

Microsoft Azure VMware Solution (AVS)

For more information on AVS support, see this Veeam KB article.

Oracle Cloud VMware Solution

For more information on Oracle Cloud VMware Solutions support, see this Veeam KB article.

VMware Cloud on AWS

For more information on VMware Cloud on AWS support, see this Veeam KB article.

VMware Cloud on Dell

Hypervisor

ESXi 8.0 (up to 8.0 U3)
ESXi 7.x

Free ESXi is not supported. Veeam Backup & Replication leverages vSphere and vStorage APIs that are disabled by VMware in free ESXi.

Management Server
(optional)

vCenter Server 8.0 (optional) (up to 8.0 U3)
vCenter Server 7.x (optional)

Veeam Continuous Data Protection (CDP)

The following infrastructure requirements apply only when you protect VMs with Continuous Data Protection (CDP):

VMware vSphere edition must be VMware vSphere Essentials Kits editions or higher.

vCenter Server is required. Standalone ESXi hosts are not supported.
Minimum ESXi version required is 7.0.
Minimum 16GB RAM is required for source and target ESXi hosts.

All hosts in a cluster must be of the same major version. For example, 7.x or 8.x (7.0.0, or 7.0.2, or a combination of 7.0.0 and 7.0.2 is supported).
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 (8 and 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).

VMware vSphere VMs

Specification	Requirement
Virtual Hardware	All types and versions of virtual hardware are supported, including 62 TB VMDK. Virtual machines with virtual NVDIMM devices, with virtual disks engaged in SCSI bus sharing or residing on PMem datastores are not supported for VM backup, because VMware does not support snapshotting such VMs. To protect such VMs, use Veeam Agent backup. RDM virtual disks in physical mode, independent disks, and disks connected through in-guest iSCSI initiator are not supported for VM backup, and are skipped from processing automatically. If backup of these disks is required, use Veeam Agent backup. 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.
OS	All operating systems supported by VMware. Guest processing is supported for OS versions released before the Veeam Backup & Replication build release date. Guest processing (which includes application-aware processing and indexing) is supported for the following Microsoft Windows operating systems except Nano Server: Windows 2012 R2 SP1 or later Windows 10 22H2 for GA channel or later Windows 10 1507 for LTSB/LTSC channels or later Windows 11 22H2 or later. Guest processing (which includes application-aware processing and indexing) is supported for 64-bit versions of the following Linux operating systems: Debian 11.0 to 12.2 Oracle Linux 7 (UEK3) to 9 (UEK R7) Oracle Linux 7 to 9 (RHCK) RHEL 8.4 to 9.6 SLES 12 SP5 or later, 15 SP3 or later Ubuntu: 16.04 LTS, 18.04 LTS, 20.04 LTS, 22.04 LTS, 24.04 LTS
Software	For Linux operating systems, GLIBC 2.12 or later. GLIBC is used for the following operations: application-aware processing, file-level restore to Linux guest OS, installing persistent agent components, and adding VM as a managed server. VMware Tools (optional, recommended). VMware Tools are required for the following operations: application-aware processing, file-level restore from Microsoft Windows guest OS, and SureBackup testing functions. Open VM Tools (OVT, optional). Open VM Tools are a set of services and modules used by VMware for interaction with VMs running Linux or other VMware supported Unix-like guest operating systems. All latest OS service packs and patches (required for application-aware processing).

Specification

Requirement

Virtual Hardware

All types and versions of virtual hardware are supported, including 62 TB VMDK.
Virtual machines with virtual NVDIMM devices, with virtual disks engaged in SCSI bus sharing or residing on PMem datastores are not supported for VM backup, because VMware does not support snapshotting such VMs. To protect such VMs, use Veeam Agent backup.
RDM virtual disks in physical mode, independent disks, and disks connected through in-guest iSCSI initiator are not supported for VM backup, and are skipped from processing automatically. If backup of these disks is required, use Veeam Agent backup.

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.

All operating systems supported by VMware. Guest processing is supported for OS versions released before the Veeam Backup & Replication build release date.

Guest processing (which includes application-aware processing and indexing) is supported for the following Microsoft Windows operating systems except Nano Server:

Windows 2012 R2 SP1 or later
Windows 10 22H2 for GA channel or later
Windows 10 1507 for LTSB/LTSC channels or later
Windows 11 22H2 or later.

Guest processing (which includes application-aware processing and indexing) is supported for 64-bit versions of the following Linux operating systems:

Debian 11.0 to 12.2
Oracle Linux 7 (UEK3) to 9 (UEK R7)
Oracle Linux 7 to 9 (RHCK)
RHEL 8.4 to 9.6
SLES 12 SP5 or later, 15 SP3 or later
Ubuntu: 16.04 LTS, 18.04 LTS, 20.04 LTS, 22.04 LTS, 24.04 LTS

Software

For Linux operating systems, GLIBC 2.12 or later. GLIBC is used for the following operations: application-aware processing, file-level restore to Linux guest OS, installing persistent agent components, and adding VM as a managed server.
VMware Tools (optional, recommended). VMware Tools are required for the following operations: application-aware processing, file-level restore from Microsoft Windows guest OS, and SureBackup testing functions.
Open VM Tools (OVT, optional). Open VM Tools are a set of services and modules used by VMware for interaction with VMs running Linux or other VMware supported Unix-like guest operating systems.
All latest OS service packs and patches (required for application-aware processing).

Guest OS File Restore

File-level restore is supported for the following file systems, including Microsoft Windows Logical Disk Manager (LDM) dynamic disks and Linux Logical Volume Manager (LVM):

OS	Supported File Systems
Microsoft Windows	FAT, FAT32 NTFS ReFS Windows file-level restore to original location is supported for the following Microsoft Windows operating systems except Nano Server: Windows 2012 R2 SP1 or later Windows 10 22H2 for GA channel or later Windows 10 1507 for LTSB/LTSC channels or later Windows 11 22H2 or later.
Linux	ext2, ext3, ext4 ReiserFS JFS XFS Btrfs NTFS DRBD (Distributed Replicated Block Devices) are not supported.
BSD	UFS, UFS2
Mac	HFS, HFS+ (volumes up to 2 TB)
OpenText OES (formerly Micro Focus OES)	NSS 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: Open Enterprise Server (OES) versions 2015(SP1), 2018(SP1-SP3). Versions 2023 and 24.1 are supported with limitations. For more information, see this Veeam KB article. SUSE Linux Enterprise Server 11 SP1-SP4 with OES11(SP1-SP3) NetWare 6.5 (only restore to a new location is supported)
Solaris	UFS ZFS (except any pool versions of Oracle Solaris) 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.

VMware Cloud Director

Specification	Requirement
VMware Cloud Director	VMware Cloud Director 10.4 to 10.6

Hyper-V Platform

Hyper-V Virtual Infrastructure

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

Specification	Requirement
Platform	Microsoft Windows Server 2025 Microsoft Windows Server 2022 Microsoft Windows Server 2019 Microsoft Windows Server 2016 Azure Stack HCI OS For the supported versions, see this Veeam KB article. Windows 111 Windows 101
Hypervisor	Windows Server Hyper-V 2025 Windows Server Hyper-V 2022 Windows Server Hyper-V 2019 Windows Server Hyper-V 2016 Azure Local (formerly 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 later (optional, enables networkless guest processing) Microsoft System Center Virtual Machine Manager 2025 Microsoft System Center Virtual Machine Manager 2022 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

Specification

Requirement

Platform

Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016
Azure Stack HCI OS

For the supported versions, see this Veeam KB article.

Windows 111
Windows 101

Hypervisor

Windows Server Hyper-V 2025
Windows Server Hyper-V 2022
Windows Server Hyper-V 2019
Windows Server Hyper-V 2016
Azure Local (formerly 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 later (optional, enables networkless guest processing)
Microsoft System Center Virtual Machine Manager 2025
Microsoft System Center Virtual Machine Manager 2022
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

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.

Hyper-V VMs

Specification	Requirement
Hardware	Supported virtual hardware versions are 5.0 to 12.0 (valid for Hyper-V 2016 to 2025). 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 VM 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 Veeam Agent 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. 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).

Specification

Requirement

Hardware

Supported virtual hardware versions are 5.0 to 12.0 (valid for Hyper-V 2016 to 2025).
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 VM 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 Veeam Agent 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.

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.

Guest processing (which includes application-aware processing and indexing) is supported for 64-bit versions of the following Linux operating systems:

Debian 11.0 to 12.2
Oracle Linux 7 (UEK3) to 9 (UEK R7)
Oracle Linux 7 to 9 (RHCK)
RHEL 8.4 to 9.6
SLES 12 SP5 or later, 15 SP3 or later
Ubuntu: 18.04 LTS, 20.04 LTS, 22.04 LTS, 24.04 LTS

Guest OS File Restore

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	FAT, FAT32 NTFS ReFS Windows file-level restore to original location is supported for the following Microsoft Windows operating systems except Nano Server: Windows 2012 R2 SP1 or later Windows 10 22H2 for GA channel or later Windows 10 1507 for LTSB/LTSC channels or later Windows 11 22H2 or later.
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.

Proxmox VE Platform

Veeam Plug-in for Proxmox VE is a solution developed for protection and disaster recovery tasks for Proxmox Virtual Environment (Proxmox VE). For more information on Veeam Plug-in for Proxmox VE features and system requirements, see the Veeam Plug-in for Proxmox VE User Guide.

Nutanix AHV Platform

Veeam Plug-in for Nutanix AHV is a solution developed for protection and disaster recovery tasks for the Nutanix AHV environment. For more information on Veeam Plug-in for Nutanix AHV features and system requirements, see the Veeam Plug-in for Nutanix AHV User Guide.

Supported Applications

You can create transactionally-consistent backups or replicas of VMs that run the following applications.

Application	Requirement
Microsoft Active Directory	Veeam Backup & Replication supports backup of domain controllers for the following operating systems: Microsoft Windows Server 2025 Microsoft Windows Server 2022 Microsoft Windows Server 2019 Microsoft Windows Server 2016 Microsoft Windows Server 2012 R2 Minimum supported domain and forest functional level is Windows 2012 R2.
Microsoft Exchange	Veeam Backup & Replication supports backup of the following Microsoft Exchange versions: Microsoft Exchange Subscription Edition Microsoft Exchange 2019 Microsoft Exchange 2016
Microsoft SharePoint	Veeam Backup & Replication supports backup of the following versions of Microsoft SharePoint Server (virtualized either on VMware or Hyper-V platform): Microsoft SharePoint Server Subscription Edition Microsoft SharePoint 2019 Microsoft SharePoint 2016 All editions are supported (Subscription, Foundation, Standard, Enterprise). Restore of Microsoft SharePoint data may require an available staging Microsoft SQL Server. To learn how to configure this server, see the Staging SQL Server Settings section of the Veeam Explorers User Guide.
Microsoft SQL Server	Veeam Backup & Replication supports backup of the following Microsoft SQL Server versions: Microsoft SQL Server 2022 (only for Windows) Microsoft SQL Server 2019 (only for Windows) Microsoft SQL Server 2017 (only for Windows) Microsoft SQL Server 2016 SP2 Microsoft SQL Server 2014 SP3 Microsoft SQL Server 2012 SP4 All editions of Microsoft SQL Server except LocalDB are supported. The database whose logs you want to back up must use the Full or Bulk-logged recovery model. In this case, all changes of the Microsoft SQL Server state will be written to transaction logs, and you will be able to replay transaction logs to restore the Microsoft SQL Server. You can use the Microsoft SQL Server Management Studio to switch to one of these models. For more information, see Microsoft Docs. Restore of Microsoft SQL Server data may require an available staging Microsoft SQL Server. To learn how to configure this server, see the Configuring Staging SQL Server section of the Veeam Explorers User Guide.
Oracle on Windows OS	Veeam Backup & Replication supports backup of Oracle Database running on the following Microsoft Windows operating systems: Microsoft Windows Server 2025 Microsoft Windows Server 2022 Microsoft Windows Server 2019 Microsoft Windows Server 2016 Veeam Backup & Replication supports backup of the following Oracle Database versions on Microsoft Windows machines: Oracle Database 21c Oracle Database 19c Oracle Database 18c Oracle Database 12c Release 2 Oracle Database 12c Release 1 Oracle Database 11g Release 2 Starting from version 12.3 (build 12.3.0.310), Veeam Backup & Replication supports the backup of Windows-based VMs with several Oracle homes of different versions.
Oracle on Linux OS	Veeam Backup & Replication supports backup of Oracle Database running on the following Linux distributions: RHEL 8.4 to 9.4 SLES 12 SP5, 15 SP3 or later Oracle Linux 7 (UEK3) to 9 (UEK R7) Oracle Linux 7 to 9 (RHCK) Veeam Backup & Replication supports backup of the following Oracle Database versions on Linux machines: Oracle Database 21c Oracle Database 19c Oracle Database 18c Oracle Database 12c Release 2 Oracle Database 12c Release 1 Oracle Database 11g Release 2 Starting from version 12.1 (build 12.1.0.2131), Veeam Backup & Replication supports the backup of Linux-based VMs with several Oracle homes of different versions.
Oracle Database configuration	Consider the following: Automatic Storage Management (ASM) is supported for Oracle 11g and later; requires ASMlib present. Oracle Real Application Clusters (RAC) are not supported within the image-level backup functionality. Use Veeam Plug-In for Oracle RMAN. For details, see the Veeam Plug-In for Oracle RMAN section of the Veeam Plug-ins for Enterprise Applications User Guide. Oracle Database Express Edition (XE) is supported for Windows-based machines only. [For Microsoft Windows-based Oracle machines] Configurations with different versions of Oracle Database deployed on the same server are not supported. To create Oracle database backups, all Oracle servers that use Data Guard must be added to the backup job. You can use Veeam Plug-In for Oracle RMAN to integrate RMAN with Veeam Backup & Replication repositories. For details, see the Veeam Plug-in for Oracle RMAN section of the Veeam Plug-ins for Enterprise Applications User Guide.
PostgreSQL	Veeam Backup & Replication supports backup of the following PostgreSQL versions on Linux machines: PostgreSQL 17 PostgreSQL 16 PostgreSQL 15 PostgreSQL 14 PostgreSQL 13 Veeam Backup & Replication does not support backup of PostgreSQL clusters.

Note

Consider that 32-bit Oracle running on 64-bit operating systems and Oracle Express Edition (XE) on Linux are not supported.

File Servers

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 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016
Microsoft Windows 11 (versions 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 22H2)
Microsoft Windows 10 LTS (version LTSC 2021)

64-bit versions of the Linux operating systems:

Debian 11.0 to 12.11
Oracle Linux 7 to 10
RHEL 8.6 to 9.6
Rocky Linux 9.4 to 9.6
SLES 12 SP5, 15 SP3
Ubuntu 20.04 LTS, 22.04 LTS, 24.04 LTS

Unstructured Data Backup Support

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

Object storage repositories:

S3 compatible object storage repositories
Amazon S3 object storage
Microsoft Azure Blob storage including Azure Data Lake Gen2 storage (HNS supported)

Managed Microsoft Windows or Linux server
Enterprise NAS systems: NetApp Data ONTAP, Lenovo ThinkSystem DM/DG Series, Dell PowerScale (formerly Isilon), Nutanix Files Storage
NFS file shares
SMB file shares

Requirements and Limitations for File Shares

Consider the following requirements and limitations for file shares:

Only 64-bit versions of operating systems are supported for managed Microsoft Windows or Linux 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. Parallel NFS (pNFS) is not supported.
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 Unstructured Data Backup 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.

Requirements and Limitations for Object Storage

Consider the following limitations for object storage added as a source of unstructured data:

Veeam Backup & Replication does not support backup from and restore to the following types of Azure Blob Storage: Azure Data Box Storage, Azure Stack Edge.
Veeam Backup & Replication does not support backup from and restore to AWS Snowball Edge Storage.
Veeam Backup & Replication does not support backup from and restore to Veeam Data Cloud Vault.

For more information on unstructured data backup, see the Unstructured Data Backup section.

Network

Consider the following requirements and limitations:

Names of port groups/segments/networks must be unique.

[For VMware vSphere] VMware NSX-T 2.3 or later is supported with N-VDS for VMware vSphere and VMware Cloud on AWS/Dell.
[For VMware vSphere] VMware NSX-T 3.0 or later is supported with VDS for VMware vSphere and VMware Cloud on AWS/Dell.
[For VMware vSphere] VMware NSX-V is supported (see details on the support of vSphere and VMware Cloud version in VMware vSphere Virtual Infrastructure).