Veeam Backup & Replication 13 Release Notes

This document provides last-minute information about Veeam Backup & Replication 13, specifically its early release as the Veeam Software Appliance. It includes details on system requirements, known issues, installation and upgrade procedures, as well as important information regarding technical support, documentation, online resources, and more.

The early release of Veeam Software Appliance v13 is available for download at veeam.com/backup-replication-download.html starting from September 3rd, 2025.

See next:

System Requirements
Known Issues and Limitations
Installing Veeam Software Appliance
Migrating to Veeam Software Appliance
Licensing
Technical Documentation References
Technical Support
Contacting Veeam Software

System Requirements

Workloads

VMware vSphere

Platforms

VMware vSphere
VMware Cloud Director
VMware Cloud on AWS
VMware Cloud on Dell
Microsoft Azure VMware Solution
Google Cloud VMware Engine
IBM Cloud for VMware Solutions
Oracle Cloud VMware Solution
VMware Cloud Foundation (VCF)

Hosts

ESXi 9.0
ESXi 8.0
ESXi 7.x

Software

vCenter Server or vCenter Server Appliance 9.0
vCenter Server or vCenter Server Appliance 8.0
vCenter Server or vCenter Server Appliance 7.x
Cloud Director 10.4 to 10.6

Standalone ESXi hosts are fully supported, so vCenter Server and Cloud Director are optional. However, whenever they are present, we highly recommend that you register both with Veeam so that VMs can continue to be tracked as they move across the infrastructure.

Veeam CDP

The following infrastructure requirements only apply when Veeam CDP replication is used:

Cisco HyperFlex 5.0 (2a) and later can be used as a source or target only with VMware vSphere 7.0 U2 and later. With the previous versions of VMware vSphere, Cisco HyperFlex is not supported.
Minimum 16 GB RAM for source and target ESXi hosts.
vCenter Server is required (standalone ESXi hosts are not supported).
Backup server, CDP proxies, vCenter Server, and ESXi hosts must be able to resolve each other’s DNS names.
VMware Cloud on AWS is not supported.

Virtual Hardware

All types and versions of virtual hardware are supported.
Virtual machines with virtual NVDIMM devices, with virtual disks engaged in SCSI bus sharing or residing on PMem datastores are not supported for host-based backup. Use the agent-based backup to protect such VMs.
RDM virtual disks in physical mode, independent disks, and disks connected via in-guest iSCSI initiator are not supported for host-based backup. Such disks are skipped from processing automatically. If backing up these disks is required, please use agent-based backup.

Guest Operating Systems

All operating systems supported by the VMware vSphere version as of the build release date.
Microsoft VSS integration is supported for Microsoft Windows Server 2016 and later.
VMware Tools (optional, recommended)
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
Windows	FAT, FAT32, NTFS, ReFS
Linux	ext2, ext3, ext4, ReiserFS, JFS, XFS, Btrfs
BSD	UFS, UFS2
Mac	HFS, HFS+
OES	NSS
Solaris	UFS, ZFS (except pool versions of Oracle Solaris)

Microsoft Hyper-V

Platforms

Microsoft Windows Server Hyper-V
Microsoft Hyper-V Server (free hypervisor)
Microsoft Azure Local (former Microsoft Azure Stack HCI 24H2 and later)

Hosts

Hyper-V 2025
Hyper-V 2022
Hyper-V 2019
Hyper-V 2016
Azure Stack HCI

Microsoft Windows 11 Hyper-V (versions 22H2, 23H2, 24H2) and Windows 10 Hyper-V (22H2) are supported only as target hosts for Instant Recovery; host-based backup of their VMs is not supported. However, you can protect them with agent-based backup.

Software

Microsoft Windows PowerShell 5.1 (optional, enables network-less guest processing)

Standalone Hyper-V hosts and clusters are fully supported, so SCVMM is optional. Registering Hyper-V clusters may provide better scalability in large environments.

Virtual Hardware

Supported virtual hardware versions are 5.0 to 12.0
Both Generation 1 and 2 virtual machines are supported.
Pass-through virtual disks and guest disks connected via in-guest FC or iSCSI initiators are not supported for host-based backup. Such disks are skipped from processing automatically. If backing up these disks is required, please use agent-based backup.

Guest Operating Systems

All operating systems supported by the Hyper-V version in use.
Microsoft VSS integration is supported for Microsoft Windows 2016 and later.
Hyper-V integration components (optional, recommended)
File-level restore is supported for the following file systems, including Microsoft Windows LDM dynamic disks and Linux LVM:

OS	Supported File Systems
Windows	FAT, FAT32, NTFS, ReFS
Linux	ext2, ext3, ext4, ReiserFS, JFS, XFS, Btrfs
BSD	UFS, UFS2
Mac	HFS, HFS+
Solaris	UFS, ZFS (except pool versions of Oracle Solaris)

Nutanix AHV

Virtualization Platform

Prism Central version pc.2022.6 (or later)
Nutanix AOS versions 6.8.1.6 - 7.3

Virtual Hardware

All types and versions of virtual hardware are supported

Operating System

All operating systems supported by the underlying Nutanix AHV version deployed (see AHV Guest OS compatibility matrix)

Proxmox VE

Virtualization Platform

Proxmox VE versions 8.2, 8.3, or 8.4 installed using the official ISO image provided by Proxmox
Both standalone and clustered Proxmox VE configurations are supported (all cluster nodes must be registered with Veeam).
Both Enterprise and No-Subscription repositories are supported. However, support for the No-Subscription repository is experimental.

Virtual Hardware

All types and versions of virtual hardware are supported, except Open vSwitch networking.
VMs residing in Proxmox VE storage of any type except for the BTRFS and custom storage types.

Guest Operating Systems

All operating systems supported by the Proxmox VE version in use.
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
Windows	FAT, FAT32, NTFS, ReFS
Linux	ext2, ext3, ext4, ReiserFS, JFS, XFS, Btrfs
BSD	UFS, UFS2
Mac	HFS, HFS+
OES	NSS
Solaris	UFS, ZFS (except pool versions of Oracle Solaris)

Unstructured Data

Object storage

The following object storage sources are supported:

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

File shares

The following file share sources are supported:

SMB version 1.x, 2.x or 3.x.
NFS protocol version 3 or 4.1.

File servers

The following Microsoft Windows operating systems are supported:

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 22H2
Microsoft Windows 10 LTSC 2021

64-bit versions of the following Linux distributions are supported:

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

Enterprise NAS Systems

NetApp Data ONTAP with ONTAP cluster-mode versions from 9.10 up to 9.16.1
Lenovo ThinkSystem DM/DG Series with ONTAP cluster-mode versions 9.10 to 9.16.1
Dell PowerScale (formerly Isilon) with OneFS versions 8.1.2 to 9.11
Nutanix Files Storage versions 3.8.1.3 to 5.0

Operating systems

To back up physical, virtual, or cloud-based machines machines running Microsoft Windows, Linux, Unix or macOS operating systems, Veeam Backup & Replication allows remote deployment and central administration of Veeam Agents.

Veeam Agent for Microsoft Windows

Hardware

CPU: x64 processor

Memory: 2 GB RAM or more. Memory consumption varies depending on the number and size of processed disks.

Disk Space: 200-700 MB for product installation. Required disk space varies depending on the Veeam Agent usage scenario.

Network: 1 Mbps or faster. High latency and reasonably unstable WAN links are supported.

System firmware: BIOS or UEFI.

Drive encryption: Microsoft BitLocker (optional). BitLocker encrypted volumes must be unlocked at the moment when Veeam Agent for Microsoft Windows starts the backup or restore operation. Only Microsoft BitLocker is supported for drive encryption. Other drive encryption products are not supported.

Operating Systems

64-bit versions of the following operating systems are supported:

Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016
Microsoft Windows 11 (from version 22H2 to version 24H2)
Microsoft Windows 10 General Availability Channel 22H2
Microsoft Windows 10 Long-Term Servicing Channel (versions 2015, 2016, 2019, 2021)
Server Core installations of Microsoft Windows Server OSes can be backed-up only by Veeam Agent backup jobs managed by the Veeam backup server.
Windows Embedded / Windows IoT OSes are supported (except for custom builds that do not have components required for Veeam Agent operation).
Each Veeam Agent computer must have a unique BIOS UUID.

File system

Microsoft Windows FAT, NTFS, ReFS file systems are supported.

The supported file system must reside on a volume that is 64 TB or smaller, because Veeam Agent uses the Microsoft Software Shadow Copy Provider to create a volume shadow copy during the backup. To learn more, see Microsoft documentation.

Disklayout

Microsoft Windows FAT, NTFS, ReFS file systems are supported.

Software

The following required 3rd party software is included in the Veeam Agent for Microsoft Windows Redistributable. During the Veeam Agent deployment process, Veeam Backup & Replication checks whether all prerequisite software is available on the target computer. If some of the required software components are missing, Veeam Backup & Replication will install missing software automatically.

Veeam OpenSSL3 FIPS Provider
ASP.NET Core Runtime 8.0.17 or later
.NET Desktop Runtime 8.0.17 or later

Veeam Agent for Linux

With blksnap kernel module for snapshots

Hardware

IMPORTANT! Check considerations and limitations that apply to the list of supported hardware.

CPU: x64.

Memory: 1 GB RAM or more. Memory consumption varies depending on the backup type and the total amount of backed-up data.

Disk Space: 100-500 MB for product installation. Required disk space varies depending on the Veeam Agent usage scenario.

Network: 10 Mbps or faster network connection to a backup target.

System firmware: BIOS or UEFI.

Disk layout: MBR or GPT.

For virtual machines: Only full virtualization type is supported. Oracle VM virtual machines are supported with limitations. Virtual I/O (VirtIO) devices have experimental support status. Other containers and paravirtualized instances are not supported.

Operating Systems

IMPORTANT! Check considerations and limitations that apply to the list of supported OSes.

Linux kernel version 2.6.32 to version 6.16 is supported.

Veeam Agent supports the 64-bit versions of the following distributions:

Debian 11.0 - 13.0
Ubuntu 16.04, 18.04, 20.04, 22.04 and 24.04
RHEL 8.4 - 9.6 and 10.0
Oracle Linux 7 - 10.0 (RHCK)
Oracle Linux 7 (starting from UEK R4) - Oracle Linux 8 (up to UEK R6)
Oracle Linux 8 (UEK R7) - for information on installation, see this Veeam KB article.
Oracle Linux 9 (UEK R7 up to 5.15.0-311.185.9.el9uek.x86_64)
Oracle Linux 9 (UEK R8) - for information on installing Veeam Agent on Oracle Linux 9 with UEK R8, see this Veeam KB article.
Oracle Linux 10 (UEK R8)
SLES 12 SP5, 15 SP3 - 15 SP7
SLES for SAP 12 SP5, 15 SP3 - 15 SP7
Rocky Linux 8.10, 9.3 - 9.6 and 10.0
AlmaLinux 8.10, 9.3 - 9.6 and 10.0
Amazon Linux 2 (starting from kernel version 5.10) and Amazon Linux 2023 - these distribution are supported for cloud machines only and have an experimental support status.

File system

IMPORTANT! Check considerations and limitations that apply to the list of supported file systems.

Veeam Agent for Linux supports consistent snapshot-based data backup for the following file systems:

BTRFS (for OSes that run Linux kernel 3.16 or later)
Ext 2/3/4
F2FS
FAT16
FAT32
HFS
HFS+
JFS
NTFS
ReiserFS
XFS

The supported file system (except for BTRFS) can reside on a simple volume or LVM2 volume; volumes protected with encryption software such as dm-crypt are supported. BTRFS is supported only if it resides directly on a physical device with no additional abstraction layers (such as LVM, software RAID, dm-crypt and so on) below or above it.

Other file systems, file systems that are not located on logical volumes, as well as network file systems like NFS or SMB shares can be backed up using the snapshot-less mode only. For details, see the Snapshot-Less File-Level Backup section in the Veeam Agent for Linux User Guide.

Software

IMPORTANT! Check considerations and limitations that apply to the list of required components.

Protected computer must have the following components installed:

Only for installing Veeam Agent using dkms packages:

linux-headers (for Debian-based systems)
linux-headers-amd64 (for Debian 13)
kernel-headers (for RHEL-based systems)
kernel-devel (for RHEL-based systems)
kernel-uek-devel (for Oracle Linux systems with UEK)
dkms
gcc
make
perl

For general operations, backup and restore:

libudev (for managing devices during backup and restore)
libacl (for backup and restore of ACLs)
libattr (for backup and restore of extended file attributes)
lvm2 (for LVM snapshots and other LVM-related operations)
libfuse2 (FUSE libraries for Debian-based and SLES-based systems)
fuse-libs (FUSE libraries for RedHat-based systems)
libncurses5 (for rendering TUI on RHEL 7 and SLES 12)
libncurses6 (for rendering TUI on RHEL 8 - 10 and SLES 15)
dmidecode (for managing Veeam Agent with Veeam Backup & Replication)
libmysqlclient (for processing MySQL database systems)
libpq5 (for processing PostgreSQL database systems)
python3 (for installing Veeam Agent on some distributions and other operations)
btrfs-progs (for backup of BTRFS file systems)
wget (for downloading recovery ISO)
tar (for file system indexing, log export and rotation)
gzip (for file system indexing, log export and rotation)

For creating custom Veeam Recovery Media:

efibootmgr (for UEFI-based systems)
isolinux (for Debian-based systems)
syslinux (for RHEL-based systems)
mksquashfs
unsquashfs
xorriso (for custom Veeam Recovery Media with EFI support)

Utilizing built-in OS LVM snapshots

Hardware

CPU: x64 and IBM POWER9 or POWER10.

Memory: 1 GB RAM or more. Memory consumption varies depending on the backup type and the total amount of backed-up data.

Disk Space: 100-500 MB for product installation. Required disk space varies depending on the Veeam Agent usage scenario.

Network: 10 Mbps or faster network connection to a backup target.

System firmware: BIOS or UEFI.

Disk layout: MBR or GPT.

Operating Systems

IMPORTANT! Check considerations and limitations that apply to the list of supported OSes.

Nosnap Veeam Agent for Linux supports the 64-bit versions of the following distributions:

Debian 11.0 – 13.0
Ubuntu 16.04, 18.04, 20.04, 22.04, and 24.04
RHEL 8.4 – 9.6 and 10.0
Oracle Linux 7 – 10.0 (RHCK)
Oracle Linux 7 (starting from UEK R4) – Oracle Linux 9 (up to 5.15.0-311.185.9.el9uek.x86_64)
Oracle Linux 10 (UEK R8)
SLES 12 SP5, 15 SP3 – 15 SP7
SLES for SAP 12 SP5, 15 SP3 – 15 SP7
Rocky Linux 8.10, 9.3 – 9.6 and 10.0
AlmaLinux 8.10, 9.3 – 9.6 and 10.0

Nosnap Veeam Agent for Linux on Power supports little endian versions of the following Linux distributions for IBM Power:

SLES 15 SP3 – 15 SP7
SLES for SAP 12 SP5, 15 SP3 – 15 SP7
RHEL 8.4, 8.6, 8.8, 8.10, 9.0, 9.2, 9.4, 9.6 and 10.0
RHEL for SAP 8.4, 8.6, 8.8, 8.10, 9.0, 9.2, 9.4, 9.6 and 10.0

File system

IMPORTANT! Check considerations and limitations that apply to the list of supported file systems.

Nosnap Veeam Agent for Linux supports consistent snapshot-based data backup for the following file systems:

All supported file systems that are built on top of LVM logical volumes.
BTRFS (for OSes that run Linux kernel 3.16 or later) [For nosnap Veeam Agent for Linux] BTRFS is supported only if it resides directly on a physical device with no additional abstraction layers (such as LVM, software RAID, dm-crypt and so on) below or above it.

[For nosnap Veeam Agent for Linux on Power] If BTRFS has additional abstraction layers (such as LVM, software RAID, dm-crypt and so on) above it, only file-level restore operations are supported. Instant Recovery, restore verification (SureBackup), bare metal recovery and volume-level restore are not supported.

Supported file systems that are not located on logical volumes, other file systems and network file systems like NFS or SMB shares can be backed up using the snapshot-less mode only. For details, see the Snapshot-Less File-Level Backup section in the Veeam Agent for Linux User Guide.

Software

IMPORTANT! Check considerations and limitations that apply to the list of supported components.

Protected computer must have the following components installed:

For general operations, backup and restore:

libacl (for backup and restore of ACLs)
libattr (for backup and restore of extended file attributes)
lvm2 (for LVM snapshots and other LVM-related operations)
libfuse2 (FUSE libraries for Debian-based and SLES-based systems)
fuse-libs (FUSE libraries for RedHat-based systems)
dmidecode (for managing Veeam Agent with Veeam Backup & Replication, not required for Veeam Agent for Linux on Power)
btrfs-progs (for backup of BTRFS file system)
wget (for downloading recovery ISO)
tar (for file system indexing, log export and rotation)
gzip (for file system indexing, log export and rotation)

For creating custom Veeam Recovery Media (not required for Veeam Agent for Linux on Power):

efibootmgr (for UEFI-based systems)
isolinux (for Debian-based systems)
syslinux (for RedHat-based systems)
mksquashfs
unsquashfs
xorriso (for custom Veeam Recovery Media with EFI support)

Veeam Agent for Mac

Hardware

CPU: x64 or ARM Apple-branded hardware.

Memory: 2 GB RAM or more. Memory consumption varies depending on the total amount of backed-up data.

Disk Space: 450 MB free disk space for product installation.

Network: 10 Mbps or faster network connection to a backup target.

System firmware:

Operating Systems

15 Sequoia
14 Sonoma
13 Ventura
12 Monterey
11 Big Sur

File system

Veeam Agent supports consistent data backup with snapshot for the APFS file system.

The following file systems can be backed up in the snapshot-less mode:

HFS+
MS-DOS (FAT)
exFAT
NTFS
FAT32
SMB

Consider the following:

Software RAID is not supported.
Total size of all file systems included in a backup must not exceed 216 TiB.
Size of a file in a backup must not exceed 16 TiB.
Name of a file in a backup must not be larger than 254 bytes.
Keep in mind that characters that you can use in the file name may be encoded in 2 bytes or more.

Veeam Agent for IBM AIX

Hardware

Memory: 1 GB RAM (for standard backup and restore operations) / 4 GB RAM (for bare metal recovery).

Disk Space: 1.5 GB free disk space for product installation.

Network: 10 Mbps or faster network connection to a backup target.

Operating Systems

IBM AIX 7.1 - 7.3 TL3 are supported.

Note:

Only GA versions of the IBM AIX operating system that have been released before the Veeam Agent for IBM AIX 13.0.0 are are supported.
Backup of a Virtual I/O Server (VIOS) is not supported.

File system

All file systems supported by the supported operating systems.

Consider the following:

Total size of all file systems included in a file-level backup must not exceed 216 TiB.
Size of a file in a backup must not exceed 16 TiB.
Name of a file in a backup must not be larger than 254 bytes.
Keep in mind that characters that you can use in the file name may be encoded in 2 bytes or more.
Sparse files are not supported. Veeam Agent backs up and restores sparse files as regular files.
JFS2 snapshots are not supported.
Backup of clustered systems (including IBM PowerHA SystemMirror) is not supported.
Veeam Agent supports backup and restore of NFSv4 Access Control Lists (ACLs). For more information, see Backup of ACLs.

Software

IMPORTANT! The user account used to work with Veeam Agent for IBM AIX installed on the protected computer must have the /bin/bash shell set as the default shell.

The following utilities must be installed on the machine:

mlocate - required for file system indexing. You must use the mlocate utility that is provided with Veeam Agent in the product installation media.
If you upgrade to Veeam Agent for IBM AIX version 12.1 and you have the mlocate utility provided with one of the previous versions of Veeam Agent for IBM AIX installed in - your system, you must replace the existing mlocate utility with the mlocate utility provided with Veeam Agent in the product installation media.
tar - required for file system indexing, exporting and rotating logs. It is installed with the product.
gzip - required for file system indexing, exporting and rotating logs. It must be installed separately.
mkisofs - required for creating Veeam recovery Media.
[For IBM AIX 7.3, 7.2 and 7.1 TL1 or higher] This utility is pre-installed in the OS and does not require separate installation.
[For IBM AIX 7.1 TL0] You must install version 1.13 of the mkisofs utility.
[For IBM AIX 7.1] bos.rte.libc version 7.1.5.0 or later must be installed.

AIX Environment

The LIBPATH AIX environment variable on the Veeam Agent computer must be set to blank (default value). If a different value is specified for this variable, you must make adjustments to the AIX environment for proper operation of Veeam Agent. To learn more, see this Veeam KB article.

Veeam Agent for Oracle Solaris

Hardware

CPU: Oracle SPARC or Intel x86 processor.

Memory: 1 GB RAM (for standard backup and restore operations) / 4 GB RAM (for bare metal recovery).

Disk Space: 250 MB free disk space for product installation.

Network: 10 Mbps or faster network connection to a backup target.

Operating Systems

Oracle Solaris 10 1/13, 11.3 and 11.4 operating systems on machines based on the SPARC or Intel x86 architecture are supported.

Note: Only GA versions of the Oracle Solaris OS that have been released before the Veeam Agent for Oracle Solaris version 13.0.0 are supported.

File system

All file systems supported by the supported operating systems.

Consider the following:

Total size of all file systems included in a file-level backup must not exceed 216 TiB.
Size of a file in a backup must not exceed 16 TiB.
Name of a file in a backup must not be larger than 254 bytes. Keep in mind that characters that you can use in the file name may be encoded in 2 bytes or more.
Sparse files are not supported. Veeam Agent backs up and restores sparse files as regular files.
Backup of clustered systems is not supported.
Veeam Agent supports backup and restore of NFSv4 Access Control Lists (ACLs). For more information, see Backup of ACLs.

Software

IMPORTANT! The user account used to work with Veeam Agent for Oracle Solaris installed on the protected computer must have the /bin/bash shell set as the default shell.

For file system indexing, the following utilities are required: tar, mlocate and gzip.

mlocate (version 0.26-1 or later) – required for file system indexing. If your system does not have the mlocate utility, you can install it from the product installation media.
tar - required for file system indexing, exporting and rotating logs. It is installed with the product.
gzip – required for file system indexing, exporting and rotating logs. It must be installed separately.
xorriso – required for creating Veeam Recovery Media.

Oracle Solaris minimal install (Core System Support Software Group) requires adding the following packages: SUMWtoo, SUNWzoneu and SUNWzoner.

OpenSSH is required for Veeam Agent installation. On Oracle Solaris 10 1/13 and 11.3, OpenSSH must be installed manually. For more information, see this Veeam KB article.

Applications

Application-aware image processing and Veeam Explorers

Application-aware processing is a Veeam technology that allows Veeam Backup & Replication to prepare applications running in the guest OS for backup and create a consistent view of application data on the machine. Additionally, application-aware image processing enables transaction log backups to prevent storage space from being overwhelmed on the guest machine and allows for point-in-time recovery using Explorer, helping to avoid significant data loss when restoring from a full or incremental backup without selecting a specific point in time.

The Veeam Explorers Suite extends the functionality of Veeam Backup & Replication, allowing you to restore or export application items from backup or replica files and perform Instant Recovery.

Microsoft SQL Server

Microsoft SQL Server 2022
Microsoft SQL Server 2019
Microsoft SQL Server 2017
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.

Microsoft Active Directory

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

Microsoft Exchange Subscription Edition
Microsoft Exchange 2019
Microsoft Exchange 2016

Microsoft SharePoint

Microsoft Exchange Subscription Edition
Microsoft Exchange 2019
Microsoft Exchange 2016

All editions are supported (Subscription, Foundation, Standard, Enterprise).

The 3rd party RBS providers are not supported.

Oracle

Oracle Database 21c
Oracle Database 19c
Oracle Database 18c
Oracle Database 12c
Oracle Database 11g Release 2

PostgreSQL

PostgreSQL 17
PostgreSQL 16
PostgreSQL 15
PostgreSQL 14
PostgreSQL 13

MongoDB

MongoDB 8.0
MongoDB 7.0
MongoDB 6.0

Veeam Plug-ins for Enterprise Applications

Veeam Plug-ins for Enterprise Applications further enhance Veeam Backup & Replication by enabling transactionally consistent backups of SAP HANA, Oracle, and Microsoft SQL Server databases.

Veeam Plug-in for Microsoft SQL Server

Microsoft SQL Server 2022
Microsoft SQL Server 2019
Microsoft SQL Server 2017
Microsoft SQL Server 2016
Microsoft SQL Server 2014 SP3

Standard, Enterprise, Web, Developer editions of Microsoft SQL Server are supported.

Veeam Plug-in Toolbar requires Microsoft SQL Server Management Studio 21.x.

Veeam Plug-in for Oracle RMAN

Oracle Database 23ai *
Oracle Database 21c
Oracle Database 19c
Oracle Database 18c
Oracle Database 12c
Oracle Database 11g Release 2

Oracle Express Edition (XE) is not supported.

Oracle databases residing in OS-level containerized environments (for example: Docker, Podman) are not supported.

Oracle Database 23ai support is limited to virtual machines in cloud deployments (Oracle Cloud Infrastructure and Oracle Exadata Cloud) and On-Premises Engineered Systems (Oracle Exadata and Oracle Database Appliance).

Veeam Plug-in for SAP HANA

SAP HANA 2.0: SPS 02, SPS 03, SPS 04, SPS 05, SPS 06, SPS 07, SPS 08

Only Backint version 1.0 is supported

Express Edition is not supported.

Veeam Plug-in for SAP on Oracle

Oracle Database: 11gR2, 12c, 18c, 19c
BR*Tools: 7.20 Patch 42 or later

Veeam Plug-in for IBM Db2

IBM Db2 12.1
IBM Db2 11.5
IBM Db2 11.1
IBM Db2 10.5

Editions: Standard, Advanced

Microsoft Entra ID Plug-in for Veeam Backup & Replication

Veeam Backup for Microsoft Entra ID is a solution developed for protection and disaster recovery tasks for Microsoft Entra ID.

Microsoft Entra ID Backup Repository

PostgreSQL 17.x
PostgreSQL 16.x
PostgreSQL 15.x
PostgreSQL 14.x

Backup Infrastructure

Veeam Software Appliance

The Veeam Software Appliance is a pre-packaged, turnkey solution that enables rapid deployment of Veeam Backup & Replication or Veeam Backup Enterprise Manager on a streamlined, hardened Linux operating system, available as a convenient ISO or OVA image.

Hardware

CPU: x86-64 processor (minimum 8 cores recommended).

Memory: 16 GB RAM plus 500 MB RAM for each concurrent job.

Disk Space: minimum two disks 240 GiB each for Operating System and Product Installation.

Network: 1 Gbps or faster for on-site backup and replication, 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported.

Server hardware: Veeam offers “Veeam Ready - Appliance” certification for hardware vendors. This certification guarantees verified, certified compatibility and provides best customer experience due to additional requirements around direct technical collaboration between vendors. We also recognize that some customers are required to use the hardware they already have. As a current compatibility guidance, we expect the majority of systems on the RHEL HCL list to be compatible with Veeam Software Appliance.

Software

ESXi 7.0 U2 (7.0.2) or later for OVA deployments.

Veeam Infrastructure Appliance

Veeam Infrastructure Appliance is a purpose-built, minimalistic Linux distribution developed and maintained by Veeam to streamline the deployment and management of Veeam infrastructure components. Delivered as a bootable ISO, Veeam Infrastructure Appliance is pre-hardened following industry security best practices and contains only the essential services and components required to operate specific Veeam roles, such as a Hardened Repository or Proxy Server.

Hardware

CPU: x86-64 processor (minimum 4 cores recommended).

Memory: 8 GB RAM.

Disk Space: minimum two disks 120 GiB each for Operating System and Product Installation.

Network: 1 Gbps or faster for on-site backup and replication, 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported.

Software

ESXi 7.0 U2 (7.0.2) or later for OVA deployments.

Veeam Web UI

Client Software

Firefox, Google Chrome, or Microsoft Edge. The browser must have JavaScript and WebSocket protocol enabled.
Microsoft Excel to view reports exported to Microsoft Excel format.

Veeam Backup & Replication Console

Hardware

CPU: x86-64 processor.

Memory: 8 GB RAM

Disk Space: 500 MB for product installation and 4.5 GB for Microsoft .NET Framework 4.7.2 installation.

Network: 1 Mbps connection to the backup server. High latency and low bandwidth affect the user interface responsiveness.

64-bit versions of the following Microsoft Windows operating systems are supported:

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 22H2
Microsoft Windows 10 LTSC 2021

Software

Microsoft .NET Framework 4.7.2 (included in the setup)
Microsoft Windows Desktop Runtime 8.0 (included in the setup)
Microsoft Windows PowerShell 7.5.1 (included in the setup)
Microsoft SQL Server System CLR Types (both for SQL Server and PostgreSQL, included in the setup)
Microsoft Universal C Runtime (included in the setup)
Microsoft Edge WebView2 Runtime (included in the setup)
Windows Installer 4.5

Remote PowerShell Console

Operating Systems

Rocky 9.2
RHEL 9.2

Software

PowerShell 7.5.1

Backup Proxy Server (VMware, Hyper-V, Agents, Unstructured Data Backup)

Backup proxies can be deployed in several ways, depending on the environment and workload:

VMware and General-Purpose Proxies: These can be deployed using the Veeam Infrastructure Appliance image by selecting the Infrastructure Appliance option. This method enables certificate-based authentication, secure industry-standard communication protocols, and automated updates centrally managed through the Veeam Backup & Replication server.
Note that when using the Veeam Infrastructure Appliance for a backup proxy, ensure that you add the hardware requirements for the Backup Proxy Server to the appliance’s system requirements. This ensures that the assigned role has sufficient CPU and RAM resources.
Hyper-V Off-Host Proxies and Agent-Based Proxies: These must be deployed on supported Windows-based servers and do not support deployment via the Veeam Infrastructure Appliance.

In all cases, you can deploy and manage backup proxies on compatible operating systems according to your requirements.

Hardware

CPU: x86-64 processor (minimum 2 cores or vCPUs). For unstructured data backup, additionally 4 cores (vCPUs) are recommended (2 cores are required) for each concurrent task. Using multi-core processors improves data processing performance and allows more tasks to be processed concurrently.

Memory: 2 GB RAM plus 1 GB for each concurrent task. For unstructured data backup, 4 GB RAM plus 4 GB RAM is required for each concurrent task. The actual size of memory required may be larger and depends on the amount of data to back up, machine configuration, and job settings. Using faster memory improves data processing performance.

Disk Space: 750 MB for Microsoft Windows-based proxies; 400 MB for Linux-based proxies.

Network: 1 Gbps or faster for on-site backup and replication, 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported.

Operating Systems

For VMware vSphere backup proxy, 64-bit versions of the following Microsoft Windows operating systems are supported, including the Core edition:

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 22H2
Microsoft Windows 10 LTSC 2021

64-bit versions of the following Linux distributions are supported:

Veeam Infrastructure Appliance
Debian 11.0 to 13
Oracle Linux 7 to 10
RHEL 8.6 to 9.6
Rocky Linux 9 latest supported minor release, see Rocky Linux Release and Version Guide
SLES 12 SP5 or later, 15 SP3 or later
Ubuntu 20.04 LTS, 22.04 LTS, 24.04 LTS

For the Hyper-V off-host backup proxy server, the following operating systems are supported, including the Core Edition (the Hyper-V role must be enabled on the server):

Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016

For agent-based off-host backup proxy server, 64-bit versions of the following Microsoft Windows operating systems are supported, including the Core edition:

Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016

For general-purpose backup proxy server used for file backup and object storage backup, 64-bit versions of the following Microsoft Windows operating systems are supported, including the Core edition:

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 22H2
Microsoft Windows 10 LTSC 2021
SMB 3.0 file share backup from Microsoft VSS snapshots requires Microsoft Windows Server 2016 or later.

For general-purpose backup proxy server used for file backup and object storage backup, also 64-bit versions of the following Linux distributions are supported:

Veeam Infrastructure Appliance
Debian 11.0 to 12.11
Oracle Linux 7 to 10
RHEL 8.6 to 9.6
Rocky Linux 9 latest supported minor release, see Rocky Linux Release and Version Guide
SLES 12 SP5, 15 SP3
Ubuntu: 20.04 LTS, 22.04 LTS, and 24.04 LTS

CDP Proxy Server

Hardware

CPU: x86-64 processor (minimum 4 cores or vCPUs). Using multi-core processors improves data processing performance and allows for more tasks to be processed concurrently.

Memory: 8 GB RAM. Using more memory allows for longer peak write I/O periods before a CDP policy switches to the disk-based write I/O cache. Using faster memory improves data processing performance.

Disk Space: 300 MB plus disk-based write I/O cache (non-persistent data, at least 50 GB recommended). A larger cache allows for longer network downtime periods before a CDP policy switches to the CBT mode.

Network: 100 Mbps or faster.

Operating Systems

64-bit versions of the following Microsoft Windows operating systems are supported, including the Core edition:

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 22H2
Microsoft Windows 10 LTSC 2021

64-bit versions of the following Linux distributions are supported. Note that bash shell and SSH are required.

Veeam Infrastructure Appliance
Debian 11.0 to 13
Oracle Linux from 8.3 (UEK R6 U2) to 9 (UEK R7)
Oracle Linux 7 to 9 (RHCK)
RHEL 8.6 to 9.6
Rocky Linux 9 latest supported minor release, see Rocky Linux Release and Version Guide
SLES 12 SP5 or later, 15 SP3 or later
Ubuntu 20.04 LTS, 24.04.3 LTS

Nutanix AHV worker, Proxmox VE worker

Workers process backup workload and distribute backup traffic when transferring data to backup repositories. If you deploy a worker using the default configuration, the following compute resources will be allocated:

CPU: 6 vCPU
Memory: 6 GB RAM
Disk Space: 100 GB for product installation and logs

With the default configuration the worker can handle up to 4 concurrent backup and restore tasks. While deploying a new worker or editing the settings of an existing one, you can increase the maximum number of concurrent tasks. However, you must allocate 1 vCPU and 1 GB RAM for each additional task. When configuring the maximum number of concurrent tasks, you must also consider the network traffic throughput in your virtual infrastructure.

Backup Repository Server

A Linux Hardened Repository server can be deployed from the Veeam Infrastructure Appliance image by selecting the corresponding option. This enables certificate-based authentication over secure, industry-leading communication protocols, eliminates the need to open SSH and additional ports, and minimizes the potential attack surface. In addition to this option, you can deploy and manage the following operating systems on your own.

The following requirements also apply to gateway servers for file shares, object storage and deduplication appliance-based repositories, and cache repository servers.

Please note that the hardware requirements for the Backup Repository Server must be added to the Veeam Infrastructure Appliance system requirements to ensure that the assigned role has sufficient CPU and RAM resources.

Hardware

CPU: x86-64 processor.

Memory: 4 GB RAM, plus not less than 1 GB RAM for each concurrently processed machine disk and not less than 4 GB RAM for each concurrently processed unstructured data source (file share or object storage repository). Additionally, 1GB RAM is required for indexing each 200 million objects (files and folders).

Network: 1 Gbps or faster for on-site backup and replication, 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported.

Operating Systems

64-bit versions of the following Microsoft Windows operating systems are supported, including the Core edition:

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 22H2
Microsoft Windows 10 LTSC 2021

64-bit versions of the following Linux distributions are supported:

Veeam Infrastructure Appliance
Debian 11.0 to 12.11
Oracle Linux 7 to 10
RHEL 8.6 to 9.6
Rocky Linux 9 latest supported minor release, see Rocky Linux Release and Version Guide
SLES 12 SP5, 15 SP3
Ubuntu 20.04 LTS, 22.04 LTS, 24.04 LTS

Bash shell and SSH connectivity are required to deploy the management agent (SSH Server can be disabled afterward and is not required to update Veeam components).

For advanced XFS integration, only the following 64-bit Linux distributions are supported:

Debian 11.0 to 12.11
RHEL 8.6 to 9.6
Rocky Linux 9.4 to 9.6
SLES 15 SP3
Ubuntu 20.04 LTS, 22.04 LTS, 24.04 LTS
For other distributions, XFS integration support is experimental, with kernel version 5.4 or later recommended.

Mount Server

A Mount Server can be deployed from the Veeam Infrastructure Appliance image by selecting the corresponding option. This enables certificate-based authentication over secure, industry-leading communication protocols, eliminates the need to open SSH and additional ports, and minimizes the potential attack surface. In addition to this option, you can deploy and manage the following operating systems on your own.

Please note that the hardware requirements for the Mount Server must be combined with the Veeam Infrastructure Appliance system requirements, as well as any other infrastructure roles deployed together, to ensure that the assigned role has sufficient CPU and RAM resources.

Hardware

CPU: x86-64 processor.

Network: 1 Gbps or faster for on-site backup and replication, 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported.

Operating Systems

64-bit versions of the following Microsoft Windows operating systems are supported, including the Core edition:

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 24H2
Microsoft Windows 10 LTSC 2021

64-bit versions of the following Linux distributions are supported:

Veeam Infrastructure Appliance
RHEL 9.6
Rocky Linux 9 latest supported minor release, see Rocky Linux Release and Version Guide

Bash shell and SSH connectivity are required to deploy the management agent when using RHEL or Rocky Linux system (SSH Server can be disabled afterward and is not required to update Veeam components).

Tape Server

Hardware

CPU: x86-64 processor.

Memory: 2 GB RAM plus 500 MB for each concurrent task. Depending on the source of tape jobs, different entities are considered tasks: for machine backup to tape, a task covers a source job or a source chain if tape paralleling is enabled; for file backup to tape, a task covers an entire server or a file share. Restoring VMs directly from tape requires 400MB of RAM per 1TB of the restored virtual disk size. Tape cloning requires 1GB RAM for each concurrent task.

Disk Space: 300 MB, plus 10 GB for temporary data storage for backup and restore operations.

Network: 1 Gbps or faster.

Operating Systems

64-bit versions of the following Microsoft Windows operating systems are supported, including the Core edition:

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 22H2
Microsoft Windows 10 LTSC 2021

64-bit versions of the following Linux distributions are supported:

Debian 11.0 to 12.9
Oracle Linux 7 (UEK3) to 9 (UEK R7)
Oracle Linux 7 to 9 (RHCK)
RHEL 8.6 to 9.6
Rocky Linux 9.4 to 9.6
SLES 12 SP5 or later, 15 SP3 or later
Ubuntu 20.04 LTS, 22.04 LTS, 24.04 LTS

WAN Accelerator Server

A WAN accelerator can be deployed from the Veeam Infrastructure Appliance image by selecting the Infrastructure Appliance option. This enables certificate-based authentication, secure industry-leading communication protocols, and automated updates centrally controlled via the Veeam Backup & Replication server. In addition to this option, you can deploy and manage the following operating systems on your own.

Please note that component hardware requirements must be added to the Veeam Infrastructure Appliance system requirements to ensure that the assigned role has sufficient CPU and RAM resources.

Hardware

CPU: x86-64 processor. Using multi-core processors improves data processing performance and is highly recommended for WAN links faster than 10 Mbps.

Memory: 8 GB RAM. Using faster memory improves data processing performance.

Disk Space: Disk space requirements depend on the WAN Accelerator role:

Source WAN Accelerator requires 20 GB per 1 TB of source data to store digests of data blocks of source VM disks. Disk space consumption is dynamic and changes as unique VMs are added to (or removed from) jobs with WAN Acceleration enabled.

Target WAN Accelerator requires global cache size as defined by the user (fixed amount). Disk space is reserved immediately upon selecting the WAN Accelerator as a target one in any job.

Network: 1 Gbps or faster for on-site backup and replication, 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported.

TIP

Global cache is not leveraged by source WAN Accelerators or WAN accelerators operating in high-bandwidth mode, so it does not need to be allocated and populated in such cases.

Operating Systems

64-bit versions of the following Microsoft Windows operating systems are supported, including the Core edition:

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 22H2
Microsoft Windows 10 LTSC 2021

64-bit versions of the following Linux distributions are supported:

Veeam Infrastructure Appliance
Debian 11.0 to 12.9
Oracle Linux 7 (UEK3) to 9 (UEK R7)
Oracle Linux 7 to 9 (RHCK)
RHEL 8.6 to 9.6
Rocky Linux 9 latest supported minor release, see Rocky Linux Release and Version Guide
SLES 12 SP5 or later, 15 SP3 or later
Ubuntu 20.04 LTS, 22.04 LTS, 24.04 LTS

Backup Targets

Backups can be performed directly to the following storage:

Local (internal) storage of the backup repository server.
Direct Attached Storage (DAS) connected to the backup repository server, including external USB/eSATA drives and raw device mapping (RDM) volumes.
Storage Area Network (SAN). The backup repository server must be connected to the SAN fabric via hardware or virtual HBA, or software iSCSI initiator.
Network Attached Storage (NAS) able to present its capacity as NFS share (protocol versions 3.0 and 4.1 only) or SMB/CIFS share (all protocol versions). Using consumer-grade NAS storage without an enterprise-grade RAID controller with a battery-backed write cache (BBWC) is not recommended for reliability considerations.
Veeam Data Cloud Vault
Amazon S3
Google Cloud Storage
IBM Cloud Object Storage
Microsoft Azure Blob Storage
Wasabi Hot Cloud Storage
11:11 Cloud Object Storage
Any S3-compatible object storage (on-premises appliance or cloud storage provider)
Dell Data Domain (DD OS version 7.9 to 8.3) with the DDBoost license. Both Ethernet and Fibre Channel (FC) connectivity are supported
ExaGrid (firmware version 7.2.0 P08 or later)
Fujitsu CS800 (CS800 software 5.2.0 or later)
HPE StoreOnce (firmware version 3.18.18 or later for Gen3 and 4.2.3 or later for Gen4) with Catalyst license. Both Ethernet and Fibre Channel (FC) connectivity are supported
Infinidat InfiniGuard (InfiniGuard software 5.2.0 or later)
Quantum (DXi software 5.2.0 or later). Supported Quantum DXi systems include DXiV5000, DXi4800, DXi4801, DXi9000, DXi9100, DXi9200, DXiT10

Once backups are created, they can be copied (for redundancy) or offloaded (for long-term retention) to one of the following hot object storage types using the scale-out backup repository Capacity Tier:

Veeam Data Cloud Vault
Amazon S3 (including AWS Snowball Edge)
Google Cloud Storage
IBM Cloud Object Storage
Microsoft Azure Blob Storage (including Microsoft Azure Data Box)
Wasabi Hot Cloud Storage
11:11 Cloud Object Storage
Any S3-compatible object storage (on-premises appliance or cloud storage provider)

Once backups are created on Amazon S3, Microsoft Azure Blob Storage, or S3-compatible object storage systems with the archiving extension of Smart Object Storage API, they can be further archived to one of the following respective cold object storage classes using the scale-out backup repository Archive Tier:

Amazon S3 Glacier Instant Retrieval
Amazon S3 Glacier Flexible Retrieval
Amazon S3 Glacier Deep Archive
Microsoft Azure Archive Tier
Microsoft Azure Cold Tier
S3-compatible object storage with data archiving enabled

Veeam CDP

The following source and target datastores are supported:

NFS on file storage
VMFS on block storage
VMFS on internal ESXi storage
VSAN
VSAN is supported for all hyper-converged infrastructure (HCI) appliances.
VVOL
VVOL is supported for the following vendors: NetApp, HPE Nimble, Pure Storage, and HPE 3PAR. For the list of tested vendor product lines, see this Veeam KB article.

Support for hyper-converged infrastructure (HCI) appliances other than VSAN is pending validation by Veeam. System requirements will be updated based on the testing results.

Tape

Tape Format

The following types of tape libraries (including VTL) and standalone drives are supported:

LTO3-LTO10
IBM 3592 (TS1160 and TS1170)

The tape device must be directly attached to the backup server or to a tape proxy server via SAS, FC, or iSCSI interface.

Drivers

Tape devices without device-specific, vendor-supplied OEM drivers for Windows installed will appear in Windows Device Manager as Unknown or Generic and require enabling native SCSI commands mode.
If multiple drivers are available for your tape device, use the one that allows multiple open handles from a host to a drive to exist simultaneously. Usually, such drivers are referred to as “non-exclusive.”
No other backup server or software must interact with the tape device.

Storage Snapshot Integrations

Storage snapshot integration is supported for pre-installed and additional plug-ins available for download at veeam.com/backup-replication-download.html (under Additional Downloads).

Built-in Storage Systems

Cisco HyperFlex HX-Series

VMware integration only
NFS connectivity only
HyperFlex 5.0(2x) or later (Backup from Storage Snapshots, Full Integration mode)
Basic authentication is not supported for SSO users in HyperFlex

Dell Unity XT, Unity

NFS, Fibre Channel (FC), or iSCSI connectivity for VMware and Veeam Agent integrations
Dell Unity XT/Unity OE versions 5.0 up to 5.5
OE version 5.5 requires TLS 1.2 usage. For more information, see this Veeam KB article.

Dell PowerScale (formerly Isilon)

Filer integration for NAS backup functionality
NFS or SMB (CIFS) connectivity for NAS integration
OneFS versions 8.1.2 to 9.11

Fujitsu ETERNUS HX/AX

NFS or SMB (CIFS) connectivity for NAS integration
ONTAP cluster-mode versions 9.10 to 9.16.1

HPE 3PAR StoreServ

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
3PAR OS versions 3.2.2 to 3.3.2
WSAPI 1.5 and later
iSCSI VLAN tags are supported

HPE Primera

Fibre Channel (FC) or iSCSI (starting from OS version 4.3 or later) connectivity for VMware and Veeam Agent integrations
OS versions 4.x

HPE Alletra 9000

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
OS version 9.3 or later

HPE Alletra MP

Fibre Channel (FC) or iSCSI (starting from OS version 10.3 or later), NVMe-FC and NVMe-TCP connectivity for VMware and Veeam Agent integrations
OS version 10.2 or later

HPE Nimble Storage AF-Series, HF-Series and CS-Series

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
Nimble OS from 5.2 up to 6.1.2

HPE Alletra 5000/6000

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
OS version 6.1

Lenovo ThinkSystem DM/DG Series

NFS or SMB (CIFS) connectivity for NAS integration
ONTAP cluster-mode versions 9.10 to 9.16.1

NetApp FAS/AFF/ASA, FlexArray (V-Series), ONTAP Edge/Select/Cloud VSA

NFS or SMB (CIFS) connectivity for NAS integration
ONTAP cluster-mode versions from 9.10 up to 9.16.1
NetApp ASA r2 systems (ASA A1K, ASA A70, and ASA A90) are not supported.

Nutanix Files

Filer integration for NAS backup functionality
NFS or SMB (CIFS) connectivity for NAS integration
Nutanix File Server 3.8.1.3 to 5.0

Universal Storage API Integrated Systems

IBM FlashSystem (formerly Spectrum Virtualize, includes IBM Storwize and IBM SVC)

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
Spectrum Virtualize from version 8.4 or later
Policy-based replication relationships are not detected
You will not be able to select this feature for backup and snapshot orchestration with secondary storage arrays.
Policy-based high availability (PBHA) configurations are not supported
Volumes covered by PBHA cannot be used for the storage integration feature.

Known Issues and Limitations

Backup infrastructure

Veeam Cloud Connect infrastructure cannot be enabled with this release.
All registered server names must be resolvable into IPv4 or IPv6 addresses.
The roles of Mount Server, CDP Proxy, and WAN Accelerator cannot be assigned to Linux servers where Veeam Agent for Linux (VAL) is installed. For more information, please refer to this Veeam KB article.
SSH private keys generated with DSA are no longer supported. This applies to any feature utilizing SSH private key authentication.
Storage infrastructure is rescanned every 10 minutes. Perform the “Rescan Storage” operation manually after storage infrastructure changes. Otherwise, Veeam may not “see” newly added volumes immediately.
All sensitive information, such as user credentials or encryption keys, is stored in the configuration database encrypted with a machine-specific private key of the backup server. Accordingly, a newly installed backup server cannot decrypt such information if attached to the existing database, so any encrypted information must be supplied manually. To work around this, use the configuration backup and restore functionality for backup server migrations.
The length of the VM virtual disk file and configuration file names must not exceed 128 symbols.
A backup proxy cannot transfer a backup to an SMB-based repository when the share is located on the same server as the proxy. To work around this, create a Windows-based backup repository on the proxy server instead.
Backup jobs containing VMs with non-Latin characters in the name and Quantum DXi, Fujitsu ETERNUS CS800, or Infinidat InfiniGuard as a backup repository fail with an SSH error.
Repositories backed up by Microsoft Windows Server 2025 and Windows 11 24H2 ReFS volumes with deduplication and encryption enabled are not supported.

VMware

RHEL 10 cannot be used as a VMware proxy out of the box due to the missing libcrypt.so.1 library.
Replication of encrypted VMs with datasets is not supported for vSphere v8 or later.
Replica failback operation forces digest recalculation for both source and target VMs. The quick rollback option will be ignored.
Debian and Ubuntu-based Linux backup proxies require that DNS names of vCenter Server and ESXi hosts are resolvable from the proxy server. Otherwise, jobs will fail with the “NFC storage connection is unavailable” error.
Linux-based backup proxies do not support the processing of VMs with virtual disks without ddb.uuid unique IDs in the hot add mode. Normally, such disks may only be created by specific P2V/V2V conversion tools.
DirectSAN backup mode: Multipathing (MPIO) for Linux-based backup proxies leverages only path failovers and not load balancing. These are limitations of the VMware VDDK, and the distributions supported for MPIO in DirectSAN are listed in the Virtual Disk Development Kit release notes corresponding to your vSphere version.
Processing virtual disks with the @ symbol in the disk name is not supported by proxies in VMware VDDK-based transport modes.
A virtual backup proxy server cannot be used to back up, replicate, or copy itself in the virtual appliance (hot add) mode. Jobs configured to do this will automatically failover to the Network processing mode. CBT will be disabled for proxy VMs.
Virtual Windows-based backup proxy must have VMware Tools installed; otherwise, it will be considered as not running and will never be assigned any tasks.
VMware vStorage API for Data Protection has limitations preventing the hot add process depending on VM configuration. For a complete list of hot add limitations, refer to this Veeam KB article. With the default proxy settings, should the hot add operation fail, the job will switch to the network mode for a specific virtual disk.
Hard Disk restore may fail with the “Restore job failed Error: A specified parameter was not correct: unitNumber” error when restoring the disk to an SCSI controller slot above 15. To work around this, add a paravirtual SCSI controller to the target VM by editing VM virtual hardware settings with vSphere Client.
Disk mapping functionality is not supported for IDE, SATA, and NVMe disks in the Hard Disk Restore wizard.
Restoring and replicating VMs between different ESXi versions requires the VMs’ virtual hardware version to be compatible with the target host.
Restoring VM with non-standard virtual disk layout (such as converted from VMware Workstation or VMware Server) as thin may fail. To work around this issue, restore these disks as thick.
Instant recovery of non-VMware Linux machines to VMware is not supported for backups of machines with mkinitrd missing or with mount points outside of /
Virtual disk placement and type cannot be customized during full VM restore when restoring backups produced by version earlier than 6.1.
Replication jobs may fail if the source or target datastore has special symbols in its name.
Networkless interaction with Microsoft Windows guests having UAC enabled requires that the Local Administrator (MACHINE\Administrator) or Domain Administrator (DOMAIN\Administrator) account is provided on the Guest Processing step.
Guest customization settings are not backed up and restored for Cloud Director VMs.
The state of the Standalone VM option of Cloud Director is not preserved with the full VM restore.
Virtual appliance (hot add) processing mode does not support IDE disks. This is by the design of the VMware hot add functionality, which requires SCSI or SATA adaptors (SATA hot add support requires vSphere 6 or later).
Direct NFS Access is not supported for VMs with existing snapshots when VMware quiescence is enabled.
RDM disks in virtual compatibility mode are skipped during Backup from Storage Snapshot.
Pre-freeze and post-thaw scripts for Linux do not perform elevation to root (sudo) when networkless processing (VIX) is used.
The entire VM restore to the original location does not preserve disk IOPs limits, erroneously removing the associated records from the VMX file. However, restoring to another location will keep these parameters.
Encryption storage policy is not supported for the instant recovery to First Class Disk (FCD).

VMware Cloud on AWS

Only the hot add transport mode is supported due to API limitations.
All vPower NFS-based functionality is not supported due to platform limitations.
Networkless guest interaction is not supported due to API limitations.
Re-IP addressing and file-level recovery for replicas are not supported.
Only the cold switch is supported for Quick Migration.
Replica Failback option is not supported.

CDP

In case of any environmental issues, deploying the I/O filter will fail with the “Operation is not allowed in the current state” error returned by the VMware vSphere VIB deployment framework. In most cases, the reason is a DNS issue. Other possible reasons include infrastructure issues such as an expired vCenter EAM certificate.
CDP policy cannot be created or started with the “veecdp@REPLICATION was not found” error in case some storage providers are offline. To fix the issue, refer to VMware KB76633.
I/O filter cannot be attached to VMs with snapshots. Remove all snapshots from VMs to be protected before creating a CDP policy.
Using a vCenter Server as a CDP proxy is not supported and may cause various issues.
Setup programs of specific primary storage integration plug-ins leave the CDP service stopped after the installation. Please verify the service state following the installation and start it manually if needed.
To set a short-term retention period longer than 24 hours, it is necessary to update the I/O filters to the latest version. If you are using Cloud Connect Replication, make sure your provider updates the I/O filter to the latest version before you set a short-term retention period longer than 24 hours.
During package installation via UI, the proper variables are not written to ESXi servers in Advanced System Settings. ESXi server reboot is required to resolve the issue.

Hyper-V

The Hyper-V 2022 and higher hosts force the VM configuration version to be updated from 5.0 to the latest supported by the host.
Restoring VMs, which were backed up from Hyper-V 2016 (or later) hosts in the crash-consistent state, to the Hyper-V 2022 host fails with the “Writer ‘Microsoft Hyper-V VSS Writer’ is failed at ‘VSS_WS_FAILED_AT_POST_RESTORE’” error due to a bug in Hyper-V.
Application-aware processing of VMs with Windows guest OS other than Windows Server 2016 and Windows 10 fails with the “Failed to take in-guest VSS snapshot COM error: Code: 0x80042308” error. This known Hyper-V 2016 compatibility issue is fixed by updating Hyper-V integration components on the affected guests with KB3063109.
Application-aware processing of Active Directory domain controllers running on a guest OS other than Windows Server 2016 fails with the “Failed to create VM recovery checkpoint” error (32770). To resolve this issue, ensure the latest Windows Updates are installed for the guest OS on the affected VMs.
Backing up VMs from the Hyper-V cluster in the rolling upgrade is supported. However, RCT will not be leveraged until the upgrade is completed for all nodes and the cluster functional level is upgraded to Windows Server 2016 or later. Note that the VM virtual hardware version must be upgraded to version 8.0 before RCT can be leveraged on the VM.
Virtual machines with VMPmemController virtual hardware are skipped from processing due to a Hyper-V limitation around checkpointing of such VMs. Additionally, such machines may cause restore operations to the same Hyper-V host to hang on Hyper-V 2016 versions earlier than the 1803 SAC release due to a Microsoft Hyper-V VSS Writer bug.
VMs with pass-through virtual disks cannot be processed due to limitations in Hyper-V 2016 and later checkpoints.
Virtual disks consisting of multiple files (such as from virtual machines originally created on Virtual Server 2005) are not supported for processing.
CPU Type SCVMM parameter is not backed up and restored on Hyper-V VMs.
Off-host backup from deduplicated volume fails if the Data Deduplication feature is disabled on the backup proxy server.
Restoring a VM into the root folder of SMB share fails. To work around the issue, restore the VM into a subfolder instead.
Off-host backup of a VM with Shared Virtual Hard Disks is not supported.
Restoring an Arc-enabled virtual machine will cause inconsistent behavior from Arc Management, if the original machine is still online.
Azure Local (formerly Azure Stack HCI) with Windows Defender Application Control (WDAC) requires a supplemental policy to be installed. Follow https://www.veeam.com/kb4456 for more details.
PowerShell Direct fails for x86 (32-bit) Windows guest operating systems, causing the Test Credentials operation to hang on these systems.
Additional CPU resources may be required on SCVMM servers due to the introduction of new communication components, which may increase resource consumption by system processes.
Hyper-V replication does not preserve the original VHDX schema. As a result, certain Linux distributions based on RHEL, such as Rocky Linux 9.4, may fail to start after replication.

Nutanix AHV

The certificate change on the Backup Server requires manual restart of veeam-platform-service-ahv service. Refer to this user guide page for instructions.
VM Migration: cross-cluster migration will result in loss of protection for a given VM unless it is sourced from a Prism Central category (tag). If included in the protected category, a new backup chain will be created.
Worker updates are applied at the worker start-up. For dark sites this check can be disabled by modifying the appsettings.json file via the Host Management Services -> Host Configuration -> /etc/veeam/platform-service-ahv/appsettings.json
IPv6 is not supported.
Cloud Connect and HPE Cloud Bank Storage repositories are not supported as a target for backup jobs. These repositories can be used for backup copies and support Instant Recovery.
If a standalone repository is migrated to a Scale-Out Repository, the backup jobs will fail. Editing the backup job to update to the new repository will fix the issue.
Only file-level restores are available for backups created by Veeam Plug-In for Nutanix AHV, Proxmox VE, RHV and stored on HPE Cloud Bank Storage.
Nutanix CVM: controller VMs are not eligible for backup.
Job-level encryption is not supported, use repository level encryption instead (refer to the Access Permissions section of the Veeam Backup & Replication User Guide).
Location tags are not supported for Nutanix clusters.
Move backup chain functionality is not supported.
Prism Central category-based jobs will process VMs in descending size order.
Backup Copy Job: Nutanix AHV VMs and job object exclusions are not supported.
Pre/post job scripts are not supported.
.js/.vbs/.wsf scripts are not supported for pre-freeze/post-thaw (snapshot) functionality.
No file exclusion support in guest processing.
ASM-based Oracle deployments running in virtual machines are not supported in guest processing.
Kerberos is not supported in guest processing.
Application item restore: VM name is used as the hostname for database explorer restores instead of the actual hostname.
Backup from replica cluster will not be performed if guest processing (application-aware processing or indexing) is enabled in the backup job.
If backup cannot be performed from a replica cluster, it will be performed from the original cluster.
If there is no replicated snapshot on a replica cluster, backup will be performed from the original cluster.
VMs with Volume Groups attached cannot be backed up from a replica cluster.
If VM disks were added or removed after the last replication, VM backup will be performed from the original cluster.
PD snapshots created using Nutanix AHV Async DR are not supported.
VMs with Volume Groups attached will be backed up by Veeam Plug-In for Nutanix AHV in a crash-inconsistent way.
If you specify a protection domain as the source for a backup job, only Volume Groups attached to VMs will be protected.
Volume Groups with CHAP authentication are not supported.
VeeamZIP retention is not supported.
SMB shares requiring authentication are not supported.
VMs restored to Nutanix AOS 7.0 and above will automatically enable the SCSI Controller and the CPU hot-plug functionality.
VMs with a defined affinity policy not restored to the original cluster will not start until a new affinity policy is defined.
Restore from Nutanix VM snapshot does not allow changing the underlying storage container or attached networks.
Restoring a VM using entire VM restore will retain the VM description.
Amazon S3 Glacier Instant Retrieval repository extents are only supported for instant restore.
Prior to restoring (or Instant Recovery) from other hypervisors or physical servers (agent backup) the Nutanix VirtIO drivers should be installed to ensure storage and network connectivity.
Direct restore from tape is not supported. Backups must be rehydrated from tape to an eligible disk repository.
Instant recovery does not support Volume Group recovery.
Backups created with Veeam Plug-in for Nutanix AHV version 1.0 are not supported in Instant Recovery.
Ordinary backup restore point ID retrieval is not supported in RestAPI (PowerShell is recommended).
Nutanix user, PD and backup snapshot IDs are available via Nutanix AHV RestAPI.
APIs of the previous Veeam Plug-in for Nutanix AHV versions are not supported.
Guest processing settings are not supported in RestAPI.
Nutanix guest quiescence settings are not supported in RestAPI.
Email notification job settings are not supported in RestAPI.

Proxmox VE

The certificate change on the Backup Server requires manual restart of veeam-platform-service-pve service. Refer to this user guide page for instructions.
The cluster credentials update session shows as failed despite the credentials update being successful.
Full VM restore process may change VM disk names without changing bus and bus number.
Only the file-level restore is supported for HPE StoreOnce Cloud Bank.
Workers with concurrent tasks set to 1 may turn off and on sporadically if there are 2 or more VMs in a backup job. We do not recommend setting the number of concurrent tasks to less than 4 (default).
Instant Recovery of Proxmox VMs to VMware limitations: UEFI VMs with MBR are not supported; VMs may have an incorrect number of cores per vCPU assigned; static IP addresses are not restored for Windows VMs.

NAS Backup

The restore of symlinks may fail with the error “Object already exists. Returned on an attempt to create file or directory which already exists on the server” when a Linux proxy is used.
When files are backed up directly from the Windows server, NTFS sparse files are handled as regular files, and thus are inflated during the restore.
When files are backed up directly from Linux servers, the maximum full file path length is limited to 4096.
Symlinks within Linux-based SMB shares are not supported and prevent the backup jobs from executing correctly.
Force removal of SOBR extent (without backup evacuation) requires running the health check on impacted backups twice: after removing the extent and after running the backup job for the first time.

Object Storage Backup

Restoring object storage backups to an object storage system other than the one they were taken from is only supported when the target system correctly implements all API calls from the S3 standard, as leveraging required S3 API calls that are incorrectly or incompletely implemented may lead to unexpected results including the data loss.
For Backup from Object Storage, backup and restore to different object storage systems and software versions are only supported when all API calls from the AWS S3 standard are supported. Not following this requirement can lead to unexpected situations, including data loss.

Agent Management

Active Directory integration and LDAPS connections over port 636 require a domain with a forest functional level of Windows Server 2012 R2 or above.
A rescan of a Windows machine with multiple IP addresses may fail if the first IP address is inaccessible.
File-level recovery in compare mode may request credentials even if the agent was connected using the Deployment Kit.
Paths specified in the “exclude masks” of Windows agent jobs are not applied for Windows agents.
Upgrading Debian with the Linux agent installed may cause backup jobs to fail.
Universal and Domain local groups are not supported as containers for Microsoft Active Directory-based protection groups. Use Global groups instead.
The processing rate for agent backup jobs may show incorrect values (much higher than actual).
Password loss protection is not supported for agents backing up data to an object storage repository.

Microsoft Windows Server Failover Cluster

Workgroup clusters, multi-domain clusters, and mixed OS version clusters are not supported for agent-based backup.
Only failover clusters with shared disks are supported. CSV (Cluster Shared Volume) based disks are not supported for agent-based backup.
SQL Server AlwaysON Clusterless Availability Groups and Availability Groups based on multiple SQL Server Failover Clusters are not supported for agent-based backup.
NetBIOS and DNS names for all failover cluster nodes must be resolvable from the backup server.
Failover clusters with the same NetBIOS names are not supported even when joined in different domains.
Adding a new node into the failover cluster will result in a full backup performed for all shared disks.
Bare Metal Recovery restore is not supported for shared disks. Such disks will be filtered out and not displayed in the corresponding wizard. To restore the content of such disks, use volume-level recovery or disk export functionality.
Instant Recovery automatically skips clustered volumes during recovery.

Direct Restore to Amazon EC2

Direct restore of disks larger than 5TB requires using a proxy appliance; otherwise, restore will fail with the “Object is too large” error.
Restore of AWS-native VMs (originating from AWS) with boot type UEFI can have the wrong boot type and may not boot properly. To restore a machine, use the AmazonDefaultWindowsImage registry key with specifying AMI, which will support the EFI boot type.

Direct Restore to Microsoft Azure

Specific Linux computer configurations may require Azure VM configuration to be adjusted upon the restore to Microsoft Azure. If your VM fails to boot, contact Veeam Support for assistance.
The VM name, VM group name, and VM size are not validated for compatibility with the Microsoft Azure naming policy and storage account type and may cause the restore to fail.

Direct Restore to Google Cloud

Restore from points located in the Archive Tier backed by AWS S3 Glacier is not supported.

Veeam Threat Hunter

Microsoft Windows Defender, ESET (Linux version) and Sophos do not support the Secure Restore option to stop antivirus scanning after the first virus has been found, so the entire volume will always be scanned.
ClamAV returns a warning when attempting to scan archive files larger than 105,906,176 bytes.
ESET (Linux version) does not provide proper scan output log.
Sophos is unable to scan files when the resulting file path after mount operation exceeds 260 characters.
Antivirus software may be unable to scan files on the source VM if they have ‘rw’ permissions restricted to the root user only. In such cases, Veeam Threat Hunter and external antivirus solutions may log “Unable to scan file (Failed to scan object: file open error)” when attempting to scan these files.
Malware autoscan is supported for guest operating systems with BitLocker enabled.
In rare cases, Malware autoscan may be triggered for tape backups and report errors; however, this does not cause further issues.
Deleting restore points before autoscan has processed them can result in a failed Malware Detection session and non-functional Autoscan for the rest of the day. The system should recover at midnight when the Malware Session is restarted. (Bug 1065359)
The mount host that will perform backup scanning requires persistent connection to the signatures update server http://avupdate.veeam.com/av64bit. At the same time, backup server requires persistent connection to the endpoint https://vbr.butler.veeam.com/v1/get-token to authorize signatures update process. If connection is lost for more than 14 days, Veeam Threat Hunter functionality will stop working.
First signatures update on the mount host will take more time in order to build initial threat database.
Veeam Threat Hunter scanner might (and most likely will) be blocked by existing antivirus software on the mount host. Read http://www.veeam.com/kb1999 and configure AV exclusions accordingly.
Updates server endpoint certificate validation might fail in IPv6-only deployments, leading to a lack of feature functionality.

Security & Compliance Analyzer

Validation of the backup services accounts is not applicable to software appliance backup servers and will be removed in future updates. Suppress this validation to avoid false positive triggers.

Role-based access control (RBAC)

It is strongly recommended to reopen the Console if global permissions for a role have been modified. Minor changes may take up to 15 minutes to take effect.
Replicas are visible but unavailable for use.
Repository size may not be displayed for some repositories in backup job wizards.
Unavailable backups may be visible in the Instant Recovery and Entire Recovery wizards.
If an available backup contains a VM that is also included in another unavailable backup, all restore points for that VM may be accessible in the Instant Recovery and Entire Recovery wizards.
Managed hosts can be accessible for restore in the Publish Disk wizard.
Only a single default folder is available as the ‘Copy to’ destination option in Linux file-level restore.
Cloud Director backups appear in the list of backups available for restore to VMware for custom restore operators.
The ‘Restore to’ option is unavailable in Linux file-level restore using the software appliance backup server. It’s not possible to change the default folder in Windows file-level restore.
A custom operator receives an “Access is denied due to the custom role’s scope” message during the Hyper-V Instant Restore wizard.
For agent backups, users with a custom restore operator role will see only one failover cluster node.
Agent jobs configured to use an object storage repository may have incorrect security attributes set for advanced RBAC functionality, and may become visible to a user even when not specified in the custom role settings.
For agent backups, users with a custom backup operator role cannot see child items when specifying the backup scope using the “From jobs” option, or the restore scope when using the “From backups” option. Additionally, users with a custom backup operator role may not see child items when using the “From backups” option in a Backup Copy job.
The custom backup operator role may not display individual Mac machines in the job wizard.

Windows File Level Restore

To perform file-level recovery from a backed-up ReFS volume Windows mount server is required.
File-level restore may fail if a VM you are restoring from lacks free disk space at the time of backup.
Storage Spaces volumes are not supported for file-level recovery. Consider using Instant VM Recovery to recover guest files from such VMs. Note that Microsoft does not support Storage Spaces within a VM.
To restore files from deduplicated volumes, ensure the mount server and backup console are installed on Windows Server with the Data Deduplication feature enabled and the Windows Server version is the same or greater than the version of the VM you are restoring from. Otherwise, the deduplication driver incompatibility will cause file-level recovery errors with false data corruption reports.
CopyTo operation cannot be canceled in the remote mount server case.
File-level restore via VIX or PSDirect does not restore item permissions (ACLs) or item attributes.
File-level restore using gMSA credentials requires a pre-installed Deployment Kit on the target host.
When performing a folder download in Windows file-level restore through the Linux-based backup server Web UI, files from subfolders are not downloaded.

Multi-OS File-Level Restore with Mount Host

The mount host kernel must support the source file system from the backup. Otherwise, the mount operation may result in kernel panic in some cases.
LVM snapshots are not supported.
For restores from the ZFS pool, the mount server kernel must support ZFS and have the zfsutils-linux package installed.
Restore from BTRFS volumes is only possible with the mount host that is not the original host because there cannot be multiple BTRFS volumes with the same UUID attached to the same host.
Restoring to the original Windows host requires the Deployment Kit to be pre-installed on the target host, a configured Mount Server, and the target host must be part of the same domain with Kerberos authentication configured.
XFS devices created in Rocky Linux 10 or RHEL 10 cannot be mounted to the software appliance backup server. This is due to the newer XFS version used in these operating systems, which includes features that are incompatible with the current XFS version on the backup server.
UFS file systems cannot be mounted using FUSE.

Multi-OS File-Level Restore with Helper Appliance

Legacy Logical Volume Manager version 1 (LVM1) volumes are not supported.
Encrypted LVM volumes are not supported.
The helper appliance fails to deploy if the backup contains mirrored Linux LVM partitions.
Spanned, striped, mirrored, and RAID-5 Windows dynamic disks are not supported. To work around the issue, use Windows File Level Restore instead.
Non-standard file system configuration support is limited (for example, configurations where the file system journal is located on another volume, separately from the actual file system, are only supported for the ext3 file system, but not for other file systems).

Guest File System Indexing

File ownership data is not collected for files on non-NTFS volumes and for guest files of Hyper-V VMs.
Indexes cannot be published if there are locales or Unicode characters in the file system path.

Replica Failover

Starting a replicated VM using means other than the product user interface (including vSphere Client, Hyper-V Manager, SCVMM, and PowerShell) disables the advanced replication functionality such as Re-IP and failback.

SureBackup

The automatic virtual lab configuration is not supported for networks with non-private network addresses.
The automatic virtual lab networking configuration process may fail with the “Unable to resolve default network settings” error. To work around the issue, return to the wizard and try again.
The automatic virtual lab networking configuration may sometimes fail when DVS are present in the virtual environment. In such cases, use the advanced configuration mode to manually set up the virtual lab networking.
SureBackup job fails on VM with unsupported or excluded virtual disks that were not explicitly set to be removed from configuration (as a part of disk exclusion settings in the backup job) because the test VM cannot find its disks and cannot start.
Automatic physical mode RDM disk exclusion in the backup job may lead to a situation where the test VM can connect to the RDM disk and make irreversible changes on the disk. To avoid this, always explicitly exclude the physical RDM disk from the backup job, selecting the option to remove the excluded disks from the configuration.
Some antivirus applications are known to cause BSOD on the backup repository server when the SureBackup job is started. To prevent this, exclude backup folders from monitoring.
The SureBackup ‘SQL Server’ role is not supported on Linux-based Veeam Backup & Replication servers.

Backup Copy

Backup copy jobs no longer support selecting workloads from “from infrastructure.”
In the immediate copy mode, the backup copy job processes only the latest backup files chain. To make such jobs copy all existing backups, create BackupCopyMirrorAll (REG_MULTI_SZ) registry value under the HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server. This value should be populated with Backup Copy job names.
The backup copy job with the Cloud Director workload may fail to start the backup over the WAN accelerator to a backup repository with a gateway server.
A synthetic full backup is not created according to the backup copy job schedule for Cloud Director workloads if the primary backup job did not create any restore points for the same date.

Object Storage Repository

Not all Amazon and Azure regions may provide cold object storage tiers used by the SOBR Archive Tier and compute resources required to provision proxy appliances for data archival. Pay attention to this when selecting the cloud region to use.
Using the immutability feature with the existing S3 bucket containing backups created with Veeam Backup & Replication 9.5 Update 4 requires that both Versioning and Object Lock are enabled on the bucket simultaneously before the immutability feature is enabled. Any other approach will lead to backup offload failures and the inability to interact correctly with backups in the bucket.
Data in an object storage bucket/container must be managed solely by Veeam, including retention and data management. Enabling lifecycle rules is not supported and may result in backup and restore failures.
Automatic bucket provisioning is not supported by S3-integrated object storage systems that implement load balancing at the smart entity level. Please consult with your storage vendor to determine whether they recommend enabling this option.

Scale-Out Backup Repository

Rebalancing the Scale-Out Backup Repository with the Performance Tier comprising immutable or object storage repositories is not supported. The first run of SOBR rebalancing may skip Microsoft SQL log backups and the related image-level backups. These backups will be relocated on the next run.
Health check for backups located in a SOBR consisting of Dell Data Domain or HPE StoreOnce extents is not supported.

NetApp ONTAP

Infinite volumes are not supported.
Target units of SVM DR/vFiler DR relationships are not supported and are automatically hidden by the UI.

Storage Integration

Storage integration is not supported for VMs added via standalone ESXi hosts. Backup jobs for such VMs will fail with the error: “Unable to prepare source for task; Object reference not set to an instance of an object.”

Veeam Explorer for Storage Snapshots

Multi-home restore is supported for snapshots created by jobs only, not the ones created during a rescan operation. For other storage snapshots, only disks residing on the same datastore with the VMX file will be available for all restore types.

Tape

Source backup chain upgrade for VM backups will cause Backup to Tape to process the upgraded chain from scratch to ensure the data and metadata consistency on the tape media.
File to Tape job fails to build a list of files to process if the catalog contains files with certain Unicode symbols.
Backup to Tape job will perform a full backup during each run if the source forever forward incremental backup job or backup copy job in the immediate copy mode has a retention of less than 3 restore points or if the source backup copy job in the periodic copy mode has a retention of less than 4 restore points.
SQL, PostgreSQL, and Oracle transaction log backup to tape are not supported.
If you manage several tape libraries with the same Veeam backup server and use barcodes to identify tapes in these libraries, all barcodes must be unique across all tape libraries.
File-to-tape operations from SMB source may fail during reconnects when backing up large amounts of data.
The restore wizard in the UI may freeze or crash if there are millions of objects in the root of a volume, share, or bucket.
Tape job progress may display incorrect information if retries occur within the job or if the initial enumeration takes an extended time, even though data is being processed correctly to tape.

Applications

MongoDB backup fails if there are hidden nodes in the replica set. To work around this issue, alter the Hidden node member priority to 0, or uncheck the node in the list of nodes for backup components installation in the Protection Group wizard.
The Mount server will be used as a gateway server if application plug-in backups are pointed to an object storage repository and the direct connection mode is selected in the repository settings.
The amount of egress traffic to object storage increases significantly with longer Immutability periods and a greater number of Scale-Out Backup Repository extents when an object storage repository is used as a primary or secondary target for application plug-in backups.

Veeam Kasten Integration

Manually exported Veeam Kasten backups fail to import to Veeam Backup & Replication with the “Object reference not set to an instance of an object” error.
Exporting backups fail to a backup server fails when domain credentials are used for the location profile.

Veeam Explorer for Microsoft Exchange

Restoring public folder items from the system “In-Place Hold Items” folder to the original location restores them to the newly created folder with the same name instead of the actual system folder.
When launching an Explorer outside of the console (using a separate application), MFA code is requested only once for saved users.

Veeam Explorer for Oracle

Instant recovery of the entire Oracle Data Guard is not supported. However, you can restore individual databases.
The database restore for Oracle Data Guard with tnsnames.ora and listener.ora located in non-default paths is not supported.
The database export functionality may fail for databases larger than 1TB in size due to the SSH command limit. If you have such databases in your environment, contact Veeam Support to enable the workaround.
The database restore may fail if the backed-up Oracle server version and the target server version have different patch levels.
Oracle Real Application Clusters (RAC) and Oracle Data Guard deployments with snapshot standby option enabled are not supported with OCI-based integration. To work around this issue, use Veeam Plug-in for Oracle RMAN.
Oracle XE on Linux is not supported.
Configuration with multiple Oracle versions on the same machine is not supported.
ASM-based Oracle deployments running in virtual machines with Open-VM-Tools installed are not supported.
Restore operations are not supported on a remote PowerShell console. Workaround: Copy the certificate by running:
cp /etc/veeam/certs/cert.pem /etc/veeam/certs/client/cert.pem chgrp veeam-grp-certs /etc/veeam/certs/client/cert.pem
For restore operations using a private key as credentials, the following algorithms are supported:
ssh-keygen -t ed25519 (works with passphrase) ssh-keygen -t rsa -b 4096 ssh-keygen -t dsa ssh-keygen -t ecdsa -b 521

Veeam Explorer for Microsoft SharePoint

Modified By field of restored documents is updated with the account performing the restore.
Restored Issue list items are assigned new Issue IDs.
Restore of Time Card list is not supported.
Versioning settings of SharePoint lists are not preserved on restore.
Restoring Generic List and Pages Library may fail with the “No content type ‘XXX’ found in web YYY” error.
Importing Picture Library export may result in IDs being changed for some items.
Importing Project Tasks list export does not preserve column order.
Importing SharePoint list export does not preserve Validation Settings.
Some Rating Settings of Discussion list values are not restored.

Veeam Explorer for Microsoft SQL Server

Instant database publishing to the SQL Server cluster requires a free drive letter on all cluster nodes according to the number of clustered disks in the backup. Instant database recovery requires twice the number of free drive letters.
A point-in-time restore with fine-tuning requires all nodes of the same AlwaysOn availability group to be in the same time zone.
Transaction log backup requires that at least one image-level backup of the SQL Server machine is performed. That means that transaction log backup will not function after the full SQL Server machine restore or for newly appearing databases until the next image-level backup is performed.
Transaction log backups are not supported for Windows Server 2008 or earlier VMs on Hyper-V 2012 R2.
SQL Server 2017 and later Graph Tables are not currently supported.

Veeam Explorer for SAP HANA

Restore operations are not supported on a remote PowerShell console.

Veeam Explorer for PostgreSQL

Publish and export operation on community edition is not possible over UI, use PowerShell as workaround.

Veeam Software Appliance

Copy Backup, Export to VBK, VeeamZip and other activties may fail to use local or SMB paths as a destination, use backup repository option as a workaround.
The user name for Veeam Software Appliance is limited to 32 characters long.
When attempting to join a Windows domain, Veeam Software Appliance may fail to join if the domain forest is not at a Windows Server 2016 level or lacks the required encryption types. Veeam Software Appliance supports the following encryption types: aes256-cts-hmac-sha384-192, aes256-cts-hmac-sha1-96, aes128-cts-hmac-sha256-128, and aes128-cts-hmac-sha1-96.
The “Data Collection” option appears on both “Veeam Infrastructure” and “Veeam Infrastructure (with iSCSI & NVMe/TCP)” appliances, but it has no effect or functionality in these cases.

Setup and Update

During the installation of the Veeam Software Appliance or Veeam Infrastructure Appliance the Anaconda setup may occasionally freeze at the “Configuring addons” stage mainly on systems with HDDs. Restarting the installation resolves this issue.
Veeam Software Appliance fails to boot when deployed to a Hyper-V VM with Secure Boot enabled if the VM is not using the “Microsoft UEFI Certificate Authority” Secure Boot template.
Auto-updates from public repository over IPv6 are not supported, as a workaround use IPv4 connection or mirror update repository to a custom one and distribute updates locally over IPv6 afterwards.
Updates and hot-fix installation will automatically perform service restart; please ensure you do not have any scheduled jobs within the planned maintenance window.

Web UI Preview

The initial release of the Web UI provides core management features but does not yet include the full functionality set available in the Remote Console. For the complete experience, the Remote Console can be downloaded directly from the Web UI.
Backups configured with GFS settings cannot be deleted.
Advanced Settings for Backup Copy Jobs cannot be configured.
Cross-platform restores (e.g., VMware to Hyper-V and vice versa) are not supported.
File-level restore to another location is not currently supported.

Remote Console

The “Get Veeam ONE” option in the UI does not open the download page in the browser.
Veeam Backup & Replication does not prompt for a repeat MFA code when re-logging into the remote console or web UI during the cookie grace period of 1 minute.
If a NETBIOS domain name differs from a fully qualified domain name, the AD browser dialog will resolve the NETBIOS domain name incorrectly when new credentials are added. To work around the issue, fix credentials manually.
Job filter functionality includes unmanaged Linux agent jobs under both Server and Workstation workload types.
For group-based authentication, the SAML token issued by the identity provider (IdP) must contain the group name in a claim with the name http://schemas.xmlsoap.org/claims/Group. If the IdP does not support custom claim names for group attributes, group-based authentication will not function.

Enterprise Manager

Backup servers running version 12 are supported only when both the backup server and Enterprise Manager are in the same Active Directory domain.
NETBIOS names of backup servers must be resolvable on the Enterprise Manager server.
Reverse DNS lookup on the Enterprise Manager server must be functional for setting up the self-service recovery delegation scope.
Instant Recovery to another location will fail with the “Failed to prepare change storage” error if the Redirect cache option is used.
Restoring Oracle application items to another server from a Windows-based machine backup fails if the default logging level is enabled in Enterprise Manager. Contact Veeam Support to get the registry key for changing the logging level.
Linux file-level restore to a different location supports only username and password credentials for guest OS authentication. Elevation and private key authentication will be supported in future updates.
UI language selection is not available on the login page and will be implemented in future updates. Alternatively, add a “lang” key with the desired language value (e.g., “de” for German) to the browser’s local storage for the Enterprise Manager web page.
File search in an indexed backup may not work properly if a specific folder is selected in the backup file system view. Workaround: enter the folder path in the location search filter.

Remote PowerShell Console

When using Veeam Explorers for Oracle Powershell module on a remote linux server, we fail to verify client fingerprint. Execute this workaround on a remote linux server with Veeam Explorers for Oracle Powershell installed:

bash

cp /etc/veeam/certs/cert.pem /etc/veeam/certs/client/cert.pem
chgrp veeam-grp-certs /etc/veeam/certs/client/cert.pem

PowerShell

Restores from imported backups residing on an SMB (CIFS) share are not supported through PowerShell.
The Veeam PowerShell module does not load automatically on Linux systems. To load the module, enter “Import-Module /opt/veeam/powershell/Veeam.Backup.PowerShell.dll” in a PowerShell session.
Setting “Monthly” maintenance window options for Veeam Updater is not supported using the “New-VBRMaintenanceWindowOptions” cmdlet.
It is not possible to set proxy settings for Veeam Updater using the “Set-VBRInternetProxyUpdateOptions” cmdlet.

Configuration Backup and Restore

Under certain circumstances, some encrypted backups may get disconnected from the corresponding job and appear as Imported. To work around the issue, use the backup mapping functionality to reconnect the job to the backup files.
Immediately after the configuration restore, Enterprise Manager may show duplicate jobs, and some jobs may be missing. The issue will go away by itself after some time.
Configuration restore fails to download the .bco file from a network share.
The configuration restore wizard does not display backups stored on object storage.

Installing Veeam Software Appliance

To install the Veeam Software Appliance with Veeam Backup & Replication v13 or Veeam Backup Enterprise Manager v13:

Download the latest ISO version since it will have the latest available cumulative patch built in.
Mount the ISO to a VM or physical machine (or use virtual machine template option) and load the GRUB installer. Select the Veeam Backup & Replicaiton or Veeam Backup Enterprise Manager option and press Enter.
Once the installation is complete, proceed with the host configuration in the initialization wizard.
Review and accept the terms of the EULA, licensing policy, required software, and third-party license agreements.
Specify the host configuration settings, such as host name, network, and time server. These settings can be changed later in the web UI.
Specify the host administrator account, set a password for this account, and configure MFA (multi-factor authentication). Optional: configure a security officer account later in the web UI. You will be able to add new users in the web UI at any time. Finalize the host initialization process.
Once the installation and initialization are complete, a link to the Host Management web UI (accessible over port 10443) and a link to the application web UI (accessible over port 443) will be displayed on the splash screen.

Migrating to Veeam Software Appliance

This early release is intended for net new deployments, with upgrade and migration options coming in a future release.

Licensing

License

Veeam Backup & Replication can be licensed per protected workload with Veeam Universal License (VUL). For more information, see Veeam Licensing Policy at veeam.com/licensing-policy.html

The trial license key is sent to you automatically after downloading the product. The trial license is valid for 30 days from that moment and includes Basic technical support.

To obtain a full license key, please refer to veeam.com/buy-veeam-products-pricing.html

Subscription VUL and Perpetual VUL licenses include a maintenance plan with Premium support. To renew or upgrade your maintenance plan, contact Veeam Renewals at veeam.com/renewal.html

Updating the License

The Veeam Backup & Replication server license can be managed centrally by the Enterprise Manager server. If you are using Enterprise Manager, do not update the license on individual backup servers directly, as Enterprise Manager will force its license to all connected backup servers.

To install the new license file to a backup server connected to the Enterprise Manager server:

Open the Configuration > Licensing tab in Enterprise Manager UI, and click Install License.
Browse to the license file (.lic) sent to you after registration to install the license. To learn more, see the Licensing section.
The provided license file will be automatically propagated and applied to all Veeam Backup servers connected to this Enterprise Manager server.

To install the new license file to a standalone backup server that is not managed by the Enterprise Manager server:

Select License from the main menu.
Click the Install license button to browse for the license file (.lic) sent to you after registration to install the license. To learn more, see the Licensing section.

Technical Documentation References

If you have any questions about Veeam Software Appliance, Veeam Infrastructure Appliance, Veeam Backup & Replication or any other Veeam products, you may use the following resources:

Product web page: veeam.com/products/veeam-data-platform.html
User guides: helpcenter.veeam.com/
R&D forums: veeam.com/forums

To view the product help, press the F1 key or select Help > Online Help from the main menu.

Technical Support

We offer email and phone technical support for customers with active maintenance agreements and during the official evaluation period. For a better experience, please provide the following when contacting our technical support:

Version information for the product and all infrastructure components.
Error message and/or accurate description of the problem you are having.
Full debug log bundle. To export the log files, navigate to Veeam Host Management Console select Logs and Services > Logs tab and click create support log bundle to export the full set of log files.

To submit your support ticket or obtain additional information, please visit veeam.com/support.html.

TIP

Before contacting Veeam Customer Support, consider searching for a resolution on Veeam R&D forums at veeam.com/forums.

Contacting Veeam Software

At Veeam Software, we pay close attention to comments from our customers — and make it our mission to listen to your input and build our products with your suggestions in mind. We encourage all customers to join Veeam R&D Forums at veeam.com/forums and share their feedback directly with the R&D team.

Should you have a technical or licensing issue or question, contact our Customer Support organization directly. We have qualified technical and customer support staff available 24 hours a day, 7 days a week, who will help you with any inquiry that you may have.

Customer Support

For the most up-to-date information about our support practices, business hours, and contact details, please visit veeam.com/support.html. You can also use this page to submit a support ticket and download the support policy guide.

Company Contacts

For the most up-to-date information about company contacts and office locations, please visit veeam.com/contacts.html.