Veeam Backup & Replication 13 Release Notes

This document provides last-minute information about Veeam Backup & Replication 13, including system requirements, installation and upgrade procedures, as well as relevant information on technical support, documentation, online resources, and so on.

The release version of Veeam Backup & Replication 13 is available for download at [veeam.com/backup-replication-download.html] starting from November 19, 2025.

If you are upgrading to Veeam Backup & Replication 13 from previous versions, please review the upgrade checklist closely before performing the upgrade.

See next:

System Requirements
Known Issues and Limitations
Installing the software
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, when they are present, we highly recommend registering 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:

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, virtual disks engaged in SCSI bus sharing, or residing on PMem datastores are not supported for host-based backup. Use agent-based backup to protect such VMs.
RDM virtual disks in physical mode, independent disks, and disks connected using in-guest iSCSI initiators are not supported for host-based backup. Such disks are automatically skipped from processing. 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
Microsoft Azure Local (former Azure Stack HCI 24H2 and later)

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 using in-guest FC or iSCSI initiators are not supported for host-based backup. Such disks are automatically skipped from processing. 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, 8.4, or 9.0 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)

Scale Computing HyperCore

Virtualization Platform

Scale Computing HyperCore versions 9.4.32.218226 – 9.5.x

Virtual Hardware

All types and versions of virtual hardware are supported

Guest Operating Systems

All operating systems supported by the underlying Scale Computing HyperCore version in use (see SC//HyperCore - Software Support Guide).

oVirt KVM

This section applies to Red Hat Virtualization (RHV) and Oracle Linux Virtualization Manager (OLVM) platforms

Virtualization Platform

Oracle Linux Virtualization Manager

Oracle Linux Virtualization Manager version 4.5.5 and later
Oracle Linux Virtualization node operating version 4.5
Oracle Linux Virtualization cluster compatibility version 4.7

To learn how to configure the cluster compatibility version, see Oracle Linux Virtualization Manager documentation. Red Hat Virtualization

Red Hat Virtualization version 4.4 SP1 (Red Hat Virtualization Manager 4.5.0 and later)
Red Hat Virtualization node operating version 4.5
Red Hat Virtualization cluster compatibility version 4.7

To learn how to configure the cluster compatibility version, see Red Hat Virtualization documentation.

Virtual Hardware

Virtual Hardware for VMs - CPU: 6 vCPU - Memory: 6 GB RAM - Disk Space: 100 GB for product installation, logs, and other data

The maximum number of concurrent tasks can be increased; however, additional resources must be allocated: 1 vCPU and 1 GB RAM for each additional task. When configuring the maximum number of concurrent tasks, consider the network traffic throughput in your virtual infrastructure. For large deployments, it is recommended to configure dedicated workers that perform data processing tasks. Workers are Linux-based VMs that are distributed among the cluster hosts (nodes) and are automatically launched for the duration of a backup or restore process. VMs running as dedicated workers must be allocated the following compute resources for each concurrent task:

CPU: 4 vCPU
Memory: 4 GB RAM

All operating systems supported by KVM 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)

Universal CDP

Operating Systems

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

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

Virtualization Platforms

VMware Cloud Director 10.4 to 10.6 (via Cloud Connect)
VMware vSphere 8.x and later

Unstructured Data

Object storage

The following object storage sources are supported:

Amazon S3 object storage
Microsoft Azure Blob storage
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 FAS/AFF/ASA, FlexArray (V-Series), ONTAP Edge/Select/Cloud VSA with ONTAP cluster-mode versions from 9.7 up to 9.17.1
Lenovo ThinkSystem DM/DG Series with ONTAP cluster-mode versions 9.7 to 9.17.1
Fujitsu ETERNUS HX/AX with ONTAP cluster-mode versions 9.7 to 9.17.1
Dell PowerScale (formerly Isilon) with OneFS versions 8.1.2 to 9.11
Nutanix Files Storage versions 3.8.1.3 to 5.2

Physical and Cloud Backup

To back up physical, virtual, or cloud-based 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 25H2)
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.

Disklayout

Microsoft Windows FAT, NTFS, ReFS file systems are supported.
MBR and GPT partition tables 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.

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.21 or later
.NET Desktop Runtime 8.0.21 or later

Veeam Agent for Linux

Veeam kernel module is used for creating system snapshots. The nosnap version of Veeam Agent for Linux leverages the native snapshot capabilities of the supported file systems.

Hardware

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

CPU:

x64 (for Veeam kernel module & nosnap version)
IBM POWER9 & POWER10 (for the nosnap version only)

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

Disk Space: 300-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.

[Veeam kernel module] For virtual machines: Only the 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 Veeam kernel module considerations and limitations that apply to the list of supported OSes.

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

[For Veeam kernel module and nosnap version]

Linux kernel version 2.6.32 to version 6.17 is supported.

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

Debian 11.0 - 13.1
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 10 (UEK R8)
SLES 12 SP5, 15 SP3 – 15 SP7
SLES for SAP 12 SP5, 15 SP3 – 15 SP7
Rocky Linux 8.10, 9.4 – 9.6 and 10.0
AlmaLinux 8.10, 9.4 – 9.6 and 10.0

[For Veeam kernel module]

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.
Amazon Linux 2 (starting from kernel version 5.10) and Amazon Linux 2023 – these distributions are supported for cloud machines only and have an experimental support status.

[For nosnap version]

Oracle Linux 7 (starting from UEK R4) – Oracle Linux 9 (up to 5.15.0-311.185.9.el9uek.x86_64)
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 Veeam kernel module considerations and limitations that apply to the list of supported file systems.

IMPORTANT! Check nosnap version 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, and for the nosnap version, these file systems are supported only when built on top of LVM logical volumes:

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

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 Veeam kernel module] 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.

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.

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 Veeam kernel module considerations and limitations that apply to the list of required components.

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

Protected computer must have the following components installed:

Only for installing Veeam Agent using dkms packages:

[For Veeam kernel module]

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:

[For Veeam kernel module & nosnap version]

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 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 Veeam kernel module]

libudev (for managing devices during backup and restore)
libncurses5 (for rendering TUI on SLES 12)
libncurses6 (for rendering TUI on RHEL 8 - 10 and SLES 15)
libmysqlclient (for processing MySQL database systems)
libpq5 (for processing PostgreSQL database systems)
python3 (for installing Veeam Agent on some distributions and other operations)

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

[For Veeam kernel module & nosnap version]

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)

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

26 Tahoe
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 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 already have the mlocate utility provided with a previous version of Veeam Agent for IBM AIX installed on your system, you must replace it 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 used 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 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 SharePoint Subscription Edition
Microsoft SharePoint 2019
Microsoft SharePoint 2016

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

Third-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 18
PostgreSQL 17
PostgreSQL 16
PostgreSQL 15
PostgreSQL 14
PostgreSQL 13

MongoDB

MongoDB 8.0
MongoDB 7.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

Hardware

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

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

Disk 1: This disk hosts Veeam JeOS, Veeam Backup & Replication software, configuration database and instant recovery cache. Recommended sizing depends on the number of protected workloads:

240GB minimum
480GB SSD for small environments (up to a few hundred workloads)
960GB SSD for medium-sized environments (up to a few thousand workloads)
Multi-TB SSD for large environments. Larger capacity increases the disk space available to instant recovery cache, allowing for running more machines for longer time.

Disk 2: This disk hosts guest file system catalogs and backups, therefore recommended sizing depends on your backup storage needs. Any additional disks found in the system will be automatically joined with Disk 2 into the single Logical Volume Manager (LVM) volume.

240GB minimum.

Note: Software RAID (madm) is not supported. RAID controller with battery or capacitor backed write cache is highly recommended for performance and reliability reasons.

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

VMware vSphere ESXi 7.0 U2 (7.0.2) or later for OVA deployments.
Veeam Software Appliance ISO deployment to a virtual machine is supported, provided the hypervisor is listed as supported by Veeam.

Veeam Infrastructure Appliance

Hardware

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

Memory: 8 GB RAM.

Disk Space: Minimum of 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

Veeam Infrastructure Appliance ISO deployment to a virtual machine is supported, provided the hypervisor is listed as supported by Veeam.

Veeam Backup & Replication Server on Windows

Hardware

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

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

Disk Space: 5 GB for product installation and 4.5 GB for Microsoft .NET Framework 4.7.2 installation. 10 GB per 100 VM for guest file system catalog folder (persistent data). Additional free disk space for Instant VM Recovery cache folder (non-persistent data, at least 100 GB recommended). When upgrading Veeam Backup & Replication, additional disk space is required. For details, see Upgrading Veeam Backup & Replication.

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.

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 (from version 22H2 to version 25H2)
Microsoft Windows 10 22H2
Microsoft Windows 10 LTSC 2021

Configuration Database

PostgreSQL 14.x, 15.x, 17.x (version 17.6 is included in the setup)
Note that Veeam Backup Enterprise Manager does not support PostgreSQL installations on cloud database services (for example, Amazon Relational Database Service (RDS).
Microsoft SQL Server 2016 to 2025

Software

Microsoft .NET Framework 4.8 (included in the setup)
Microsoft .NET Windows Desktop Runtime 8.0.21 (included in the setup)
Microsoft .NET Windows Server Hosting 8.0.21 (included in the setup)
Microsoft Edge WebView2 Runtime (included in the setup)
Microsoft Windows PowerShell 7.4.13 (included in the setup)
Microsoft System CLR Types for SQL Server 2014 (both for SQL Server and PostgreSQL, included in the setup)
Visual C++ Redistributable 14.40.33810.0 (included in the setup)
Windows Installer 4.5 or later

Veeam Backup Enterprise Manager on Windows

Hardware

Processor: x86-64 processor.

Memory: 8 GB RAM.

Hard Disk Space: 2 GB for product installation plus sufficient disk space to store guest file system catalog from connected backup servers (according to data retention policy).

Network: 1 Mbps or faster connection to Veeam Backup & Replication servers. Slow or unstable links will impact the performance of Veeam Backup Enterprise Manager data collection operations from Veeam Backup servers.

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

Configuration Database

PostgreSQL 14.x, 15.x, 17.x (version 17.6 is included in the setup)
Note that Veeam Backup Enterprise Manager does not support PostgreSQL installations on cloud database services (for example, Amazon Relational Database Service (RDS).
Microsoft SQL Server 2016 to 2025

Server Software

Microsoft .NET Framework 4.8 (included in the setup)
.NET Hosting 8.0.21 (included in the setup)
Visual C++ Redistributable 14.40.33810.0 (included in the setup)
Microsoft SQL Server System CLR Types 2014 (both for SQL Server and PostgreSQL, included in the setup)
Application Request Routing 3.0.05311 (included in the setup)
ASP.NET Core Module 8.0.21 (included in the setup)
Windows Installer 4.5
Microsoft Internet Information Services 7.5 or later
Microsoft URL Rewrite 2.0 for IIS 7

Hardware

Processor: x86-64 processor.

Memory: 8 GB RAM.

Hard Disk Space: 2 GB for product installation plus sufficient disk space to store guest file system catalog from connected backup servers (according to data retention policy).

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

Veeam Web UI

Client Software

Firefox, Google Chrome, or Microsoft Edge must be of the latest version.
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 (from version 22H2 to version 25H2)
Microsoft Windows 10 22H2
Microsoft Windows 10 LTSC 2021

Software

Microsoft .NET Framework 4.8 (included in the setup)
Microsoft Edge WebView2 Runtime (included in the setup)
Microsoft Windows PowerShell 7.4.13 (included in the setup)
Windows Installer 4.5

Remote PowerShell Console

Operating Systems

Rocky 9.2
RHEL 9.2

Software

Microsoft Windows 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. Additionally, there roles can be deployed on supported Windows-based servers.
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 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 (from version 22H2 to version 25H2)
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:

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 (from version 22H2 to version 25H2)
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 (from version 22H2 to version 25H2)
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 (from version 22H2 to version 25H2)
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.1
Oracle Linux 7 to 10
RHEL 8.6 to 10
Rocky Linux 9 and 10 latest supported minor release, see Rocky Linux Release and Version Guide
SLES 12 SP5, 15 SP3, 16
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 13.1
RHEL 8.6 to 10
Rocky Linux 9.4 to 10
SLES 15 SP3, 16
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 (from version 22H2 to version 25H2)
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 400 MB 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 (from version 22H2 to version 25H2)
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 (from version 22H2 to version 25H2)
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.5) 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, 4.2.3 or later for Gen4, 5.1.0 or later for Gen 5) with Catalyst license. Both Ethernet and Fibre Channel (FC) connectivity are supported
Infinidat InfiniGuard (InfiniGuard software 5.2.0 or later)
Quantum DXi (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 hot or cold storage classes of the following object storage systems 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, they can be further offloaded to archive storage classes of the following object storage systems using the Scale‑out Backup Repository Archive Tier:

Amazon S3 Glacier
Microsoft Azure Archive 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 a tape proxy server using the 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 (experimental)
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

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, Fibre Channel (FC), or iSCSI connectivity for VMware and Veeam Agent integrations
NFS or SMB (CIFS) connectivity for NAS integration
ONTAP cluster-mode versions 9.7 to 9.17.1 (Microsoft Windows-based Backup Server)
ONTAP cluster-mode versions 9.10 to 9.17.1 (Linux-based Backup Server)
ONTAP 7-mode is not supported

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), iSCSI or NVMe-oF connectivity for VMware and Veeam Agent integrations
OS version 9.3 or later

HPE Alletra Storage MP B10000

Fibre Channel (FC), iSCSI (starting from OS version 10.3 or later) or NVMe-oF 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, Fibre Channel (FC), or iSCSI connectivity for VMware and Veeam Agent integrations
NFS or SMB (CIFS) connectivity for NAS integration
ONTAP cluster-mode versions 9.7 to 9.17.1 (Microsoft Windows-based Backup Server)
ONTAP cluster-mode versions 9.10 to 9.17.1 (Linux-based Backup Server)
ONTAP 7-mode is not supported

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

NFS, Fibre Channel (FC), or iSCSI connectivity for VMware and Veeam Agent integrations
NFS or SMB (CIFS) connectivity for NAS integration
ONTAP cluster-mode versions 9.7 to 9.17.1 (Microsoft Windows-based Backup Server)
ONTAP cluster-mode versions 9.10 to 9.17.1 (Linux-based Backup Server)
ONTAP 7-mode is not supported
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.2

Universal Storage API Integrated Systems

DataCore SANsymphony

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
DataCore SANsymphony 10.0 PSP12 or later

Dell PowerMax

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
Dell PowerMax/VMAX All Flash (PowerMax OS microcode 5978.711.711 or later 5978 family updates or PowerMaxOS 10.1.0.0 or later)
Unisphere for PowerMax 9.2.1.6 or later

Dell PowerStore

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
Dell PowerStore (PowerStore OS 3.x or later)

Dell SC Series (formerly Compellent)

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
Storage Center OS 7.4.2 or later
FluidFS and Live Volumes are not supported

Fujitsu ETERNUS AF and DX series

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
ETERNUS AF series: AF250 S2, AF650 S2, AF150 S3, AF250 S3, AF650 S3
ETERNUS DX series: DX60 S4, DX100 S4, DX200 S4, DX500 S4, DX600 S4, DX8900 S4, DX60 S5, DX100 S5, DX200 S5, DX500 S5, DX600 S5, DX900 S5, DX600 S6, DX900 S6, DX8900 S6
Software version:
- ETERNUS AF S2 and DX S4 series (except DX8900 S4): V10L88-1000 or later
- ETERNUS AF S3 and DX S5 series, DX8900 S4: V11L30-5000 or later
- ETERNUS DX S6 series: V12L10-0000 or later

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.

INFINIDAT InfiniBox F-series

NFS, Fibre Channel (FC), or iSCSI connectivity for VMware and Veeam Agent integrations
InfiniBox version 5.0 and later

NEC Storage M Series

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
M120, M320, M320F, M520, M720, M720F (Storage Control Software revision 1234 or later)

NetApp SolidFire/HCI

iSCSI connectivity for VMware and Veeam Agent integrations
Element OS version 10.0 or later

Pure Storage FlashArray

NFS, Fibre Channel (FC), or iSCSI connectivity for VMware and Veeam Agent integrations
Purity version 6.3 or later

Tintri IntelliFlash (formerly Western Digital IntelliFlash, Tegile)

NFS, Fibre Channel (FC), or iSCSI connectivity for VMware and Veeam Agent integrations
Tintri IntelliFlash 3.11 or later

Known Issues and Limitations

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).
Qick Migration will not function if the HotAdd proxy and the Mount server are located on the same host. As a workaround, use a different proxy type (NBD or SAN), or configure the Mount server on another host.

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

Universal CDP

In comparison with traditional CDP, several features are currently not available in Universal CDP:
- Seeding and Mapping
- Replica Re-IP
- Application consistent long-term restore points
- Veeam Explorers
- Planned failover
- Test failover plan
- Failback to the original location

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

Upgrades are supported from the version 12.7.1.12 (7.1) plug-in only.
During upgrade from 12.7.1.12 (7.1) any existing AHV appliance VMs will be redeployed as workers if they operate embedded workers. Appliance VMs without embedded workers will be removed once their configuration has been imported into Veeam Backup & Replication.
Database log shipping: When upgrading from plug-in version 12.7.1.12 (7.1) the parent backup job must be run to re-initiate log shipping.
In certain circumstances the VM, virtual disk or instant recovery option context menu disables plug-in platform buttons when attempting restore operations.
In the Inventory view for AHV the “Add to backup job” option for VMs can intermittently become disabled
When attempting an application item restore from an AHV snapshot only Windows operating system platform options will be shown regardless of guest operating system..
In prior plug-in versions restoring a VM to a new location which had a static IP assigned from a Nutanix managed subnet would fail if the original VM was still actively using the static IP. We now detect this case and preset an option to use DHCP or assign a new static IP to the restored VM.
Database log shipping is not functional for VMs with IDE disk bus types
Instant recovery will fail for VMs with attached vTPM
Linux VMs with appliation-aware processing enabled will ignore designated guest interaction processing hosts and default to the Veeam Backup & Replication server for guest processing

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

Scale Computing HyperCore

Due to HyperCore API limitations, inactive backup snapshots may persist on the HyperCore cluster under certain circumstances. These may be safely removed manually from the HyperCore console. This will be corrected in a future release.

oVirt KVM

This section applies to Red Hat Virtualization (RHV) and Oracle Linux Virtualization Manager (OLVM) platforms

Red Hat Virtualization 4.4 SP1

You cannot back up hosted-engine VMs. You can use an engine-backup to create oVirt configuration backup. Related RHV bug:
- https://bugzilla.redhat.com/show_bug.cgi?id=1989121
An RHV host cannot be switched to the maintenance mode due to active data transfer being performed, however, no backup operations are being processed. To resolve the issue, contact Red Hat technical support. Related RHV bug:
- https://bugzilla.redhat.com/show_bug.cgi?id=2037057
For an RHV cluster setup with 2 network adapters, manual configuration of network routing may be required. Additionally, if a SAN network is reachable from the ovirtmgmt network through a gateway, RHV will use the ovirtmgmt network instead of the selected SAN network. To avoid this issue, perform network configuration so that the SAN network cannot be reached from the ovirtmgmt network. Related RHV bug:
- https://bugzilla.redhat.com/show_bug.cgi?id=2084186
By default, Veeam Backup for OLVM and RHV applies the following deduplication and compression settings to backed-up data:
- Deduplication: Enabled
- Data compression level: Optimal
- Storage optimization: 1MB
Due to technical limitations, you cannot change these settings while configuring backup jobs.
A repeated Health Check of the corrupted data returns a green session (disk is skipped from processing).
Backup Copy exclusions does not accept oVirt KVM jobs and objects.
If you want to back up a VM that has been configured with a oVirt KVM Cloud-Init custom script, first remove the script from the VM since it may contain secure data (such as credentials and authorized keys) that will appear in Veeam Backup for OLVM and RHV backup logs.
Only File-level restores are supported for StoreOnce Cloud Bank.
While restoring an oVirt VM with the QXL GPU device to the Oracle Linux KVM environment, Veeam Backup for OLVM and RHV changes the GPU device to VGA.
While restoring an oVirt VM with the CIRRUS GPU device to the Red Hat Virtualization environment, Veeam Backup for OLVM and RHV changes the GPU device to VGA.
If you perform the revert to a snapshot operation, during the next session, Veeam Backup for OLVM and RHV runs a full scan of the VM disks and creates an incremental backup.

Unstructured Data

NAS Backup

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.

Physical and Cloud Backup

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.
File-level recovery in compare mode may request credentials even if the agent was connected using the Deployment Kit.
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.
File-level recovery via a Linux Mount server to a Cloud-native agent machine may fail with the error: “Unable to establish connection with the machine”.
Veeam Agent for Windows in the “Managed by Agent” job type may ignore the setting “Perform full backup when the required extent is offline” in some cases when the backup is targeted to a Veeam Cloud Connect repository backed by a Scale-out Backup 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.

Veeam Agent for Windows

Certain antivirus applications may cause various issues during the product setup or crash the operating system when file level recovery is initiated. To prevent this from happening, temporarily disable the antivirus for the duration of the product installation and exclude Veeam Agent for Microsoft Windows service and application folders from real-time antivirus monitoring.
Microsoft Smart App Control feature must be disabled on the machine as otherwise the installation process will be blocked.
Backup job may fail with the “Cannot create a shadow copy of the volumes containing writer’s data. VSS asynchronous operation is not completed” error if file-level recovery is being performed at the same time.
Backup job cannot wake a computer up from sleep or detect missed backup on mobile devices in Connected Standby power saving mode.
Backup job cannot wake a computer up from sleep to perform a retry cycle if “Sleep after” power saving scheme timeout is set to less than 10 minutes.
Encrypted files and folders are skipped during file level backup with the “Access denied” error. To work around the issue, use volume-level backup.
Backup job targeted at the Wasabi object storage in the eu-central-1 region and throttled to 15 MB/s may have occasional connection drops or reconnections.
If a backup job is targeted at the Amazon S3 object storage and the selected bucket resides in US or Canada, make sure that the bucket name does not contain the dot character (.). Otherwise, the backup job will fail.
“File is ready for archiving” and “Allow this file to have content indexed in addition to file properties” advanced file and folder attributes are enabled on files recovered with the file level recovery.
Changed Block Tracking driver for file-level backup tracks files of 50 MB and larger. Smaller files are not tracked by the driver and are processed regularly without Changed Block Tracking driver.
Changed Block Tracking driver is unable to track the volume changes made by non-Windows operating systems while the original Windows operating system with CBT driver was offline. Consider using MFT changed-block tracking with such setup or perform an active full after the changes were made for volumes.
Size estimation may not work correctly when performing backup to a scale-out repository, deduplication repository or repository with ReFS configuration.
Restore to the original location via Veeam Enterprise Manager may not work if the original computer and Enterprise Manager server are in different domains.
When creating recovery media with the Include network settings option enabled, if a static IPv6 address was configured, no network settings were preserved in the recovery environment.
Editing a job on a standalone agent 6.x connected to the backup server 13.0.1 or later version with multiple jobs will break the jobs; As a workaround: recreate jobs or upgrade the agent to the latest version.

Veeam Agent for Linux

User interface may appear unreadable in some terminal programs due to using incorrect symbols for pseudographics. To fix the issue in the Kitty terminal emulator, select the Allow ACS line drawing in UTF check box.
If a directory contains file with a long name consisting of 2-byte characters, the content of this directory may not be displayed in the file system tree views of the user interface.
Modifying layouts on disks under tracking may lead to problems with unloading the Veeam kernel modules.
[For Veeam Agent for Linux on Power] In command line interface, you can target backup job at a Veeam backup repository only if an active product license is installed.
Volume-level backup jobs that rely on a device name under the /dev directory require volumes to have their corresponding device names under the /dev directory staying persistent — for example: /dev/md-127, /dev/dm-1. Otherwise, the job will back up the wrong volume.
Directories encrypted with eCryptfs can be backed up only in the following conditions:
- eСryptfs is unmounted (files will be encrypted inside the backup)
- snapshot-less mode is used (files will be decrypted inside the backup)
Network shares (both CIFS and NFS) can be selected as a source only in the snapshot-less mode.
LVM physical volumes cannot be backed up, as well as RAID members. Only LVM/RAID logical volumes containing file systems can be backed up. If a physical volume is selected, then all logical volumes residing on that physical volume will be backed up.
Disks partitioned with cfdisk version older than 2.25 are not supported.
File-level backup masks do not apply to directories.
Backup job type cannot be switched between file and volume levels.
Very high data change rate during backup may cause snapshot overflow. Should this happen, the job will attempt to retry processing up to 3 times with a larger snapshot.
Sparse files are backed up as regular files.
Configurations with degraded LVM mirrors cannot be backed up.
[For systems with GPT disk layout scheme] To guarantee successful data restore, the backed-up disk must not contain more than 128 partitions.
File-level restore cannot be performed on kernels versions 4.0.x–4.1.33 due to the bug in FUSE kernel module. To work around the issue, either upgrade the kernel, or perform file-level restore from the Recovery Media, or on another machine.
File-level restore for files residing on eCryptfs directories does not mount eCryptfs filesystem automatically.
Concurrent file-level restore sessions from different restore points are not supported because only one restore point can be mounted at a time. To perform a file-level restore from another restore point, unmount currently mounted one first.
Restore of encrypted devices is not supported.
If root partition and bootloader reside on software RAID (mdadm), the following operations will have to be performed manually via usage of the tools provided in the Recovery Media:
- bootloader installation
- software RAID configuration
- fstab and grub configuration adjustments
It is required to switch the agent from “Managed by backup server” mode to “Standalone” mode in order to restore from Veeam Cloud Connect repository.
Sparse files are restored as regular files.
If you restore data from an encrypted backup and create a LUKS volume using the product graphical user interface, the product creates a LUKS2 volume. The LUKS2 volume can be decrypted only on Linux kernel version 4.19 or later.
[For SLES-based systems with BTRFS file system and GNOME desktop environment ver. 3 or later] When Veeam Agent mounts a backup to the machine, GNOME detects the loop device and automatically creates its own mount point. After the restore process, you must manually remove the mount point created by GNOME, otherwise BTRFS will block the next attempt to mount the backup file.
Encrypted backups created with versions older than v3.0 cannot be imported to Veeam Agent for Linux directly.
Instant Restore feature is not available for backups created with versions older than 3.0.
Databases residing on ASM volumes cannot be backed up. However, they will be prepared by AAIP engine and will be shown in Veeam Explorer for Oracle without possibility to be restored.
For GPT disks: bootloader will not be backed up if BTRFS root and BIOS boot partition reside on different physical disks.
Configuration with a swap file residing on a BTRFS subvolume cannot be backed up.
Bugs and issues in the kernel that affect BTRFS snapshots and send/receive functionality can cause backup jobs to fail.
Backup progress for subvolumes cannot be properly shown on systems with btrfsprogs versions lower than v4.1.
Large overhead can be observed in the Transferred statistics field for backup jobs that include BTRFS that has no subvolumes.
If the root subvolume (id 5) is more than 50% full, restore of the subvolume may fail.
If a subvolume is deleted during restore, it is required to remove the corresponding entry from fstab manually. Otherwise, the system will not boot.
Pseudo file systems (such as /proc, /sys, tmpfs, and such) cannot be backed up in the snapshot-less mode.
User interface may not show backups that contain localized symbols in their names.
Using Veeam Recovery Media, you may experience certain rare issues. To learn more, see this Veeam KB article.
The launch of the recovery UI may take more time if there are DNS or Internet access issues in the network.
You cannot boot the system from a custom Veeam Recovery Media for Ubuntu 16.04 because this Linux distribution contains outdated drivers for the OverlayFS filesystem.
Statistics for file-level backup jobs managed by the backup server may be inaccurate.
A backup job that uses a network folder as a target cannot be created on systems with Kaspersky Endpoint Security 10.
If an LVM physical volume is selected for backup, all volume groups that fully reside in this physical volume will be backed up.
[For Debian 13] Veeam Agent installs the latest version of linux-headers-amd64 with the matching kernel and its headers. This can cause the kernel to be upgraded, which might affect drivers or software that rely on a specific kernel version. After kernel upgrade, you may need to rebuild or reinstall any custom kernel modules that you have on the system.

Veeam Agent for Mac

macOS saves CIFS/SMB credentials in cache. As a result, if credentials have been changed, Veeam Agent for Mac uses obsolete credentials and fails to connect to shared folders. To refresh cached credentials, reboot the Veeam Agent computer.
Veeam Agent for Mac does not restore Finder comments.
To perform file-level restore, AD network user must be added to the veeam group.

Veeam Agent for IBM AIX

While a backup is mounted for file-level restore within a WPAR, it is not possible to start a backup job on the WPAR’s host server.
[For Veeam Agent for IBM AIX installed in WPAR] If the network connection between Veeam backup repository and Veeam Agent is interrupted during backup or restore operation, you must restart the operation because Veeam Agent for IBM AIX cannot automatically reconnect to Veeam backup server.
The “Transferred” value in Text-based User Interface File Level Restore sessions is always displayed as “0 B”, regardless of the actual value.
Restoring multiple large files to a target with insufficient disk space may end with a warning, “Failed to restore some files” instead of an error. Incomplete files may appear in the target directory; verify file sizes after restore.
[For bare metal recovery with Recovery wizard] If you restore from a backup file residing in a repository managed by Veeam backup server, regardless of the user role, you must explicitly allow them access to that repository in Veeam backup console. For more information, see Setting Up User Permissions on Backup Repositories.
Disks are not automatically assigned to WPARs after bare-metal recovery.
Paths longer than 1006 symbols cannot be restored during bare metal recovery and must be restored manually afterwards.
After bare metal recovery, you may need to reset, or close and open the HMC terminal to resolve any possible issues with its behavior.
If you performed bare metal recovery from a backup located in an SMB (CIFS) network shared folder, some volume groups may become unavailable after reboot. For details, see this Veeam KB article.
During bare-metal recovery, access (atime), modified (mtime) and changed (ctime) timestamps are reset for all non-empty files or directories.
[For bare metal recovery of IBM cloud machines] After bare metal recovery, non-rootvg volume groups may not be automatically imported after reboot. You must import such volume groups manually.
[For flexible mapping] In certain cases, when you restore rootvg and also restore a logical volume to an existing volume group on the current system, the target volume group can get from the recovery environment a major device number that differs from its original major device number on the current system. Mismatching of the major device numbers can cause an infinite boot loop on the recovered system.
[For flexible mapping] Volume groups marked for destruction on the current system are not listed at the Recovery Summary step of the Recovery wizard.
Veeam Agent for IBM AIX can perform file system indexing only with the mlocate utility version 0.26-1 that comes with the product installation package.
Veeam Agent for IBM AIX does not back up extended attributes of backed-up files and directories.
Veeam Agent for IBM AIX does not support JFS2 snapshots.
Veeam Agent for IBM AIX does not support sparse files.
If the overall source data size significantly increases in comparison to the size of the data backed up during the previous backup job session, Veeam Agent for IBM AIX will create an active full backup.
Restoring only from file-level backups created by Veeam Agent version 4.0 or later is supported.
Bare-metal recovery to dissimilar hardware is not supported.
Bare-metal recovery from backups created from within WPARs is not supported.
Bare-metal recovery requires a backup that includes the full contents of the root directory (the --includedirs option must be set to /).
[For flexible mapping] To avoid possible OS inconsistency after restore, rootvg must be restored as a whole volume group.
[For flexible mapping] Logical volumes can be restored only to their local copy on the current system.
[For flexible mapping] During restore, Veeam Agent ignores mirrored copies of logical volumes.

Veeam Agent for Oracle Solaris

Veeam Agent for Oracle Solaris does not back up extended attributes of backed-up files and directories.
Veeam Agent for Oracle Solaris backs up and restores sparse files as standard data files.
Veeam Agent for Oracle Solaris backs up and restores file system snapshots as standard data files.
If the overall source data size significantly increases in comparison to the size of the data backed up during the previous backup job session, Veeam Agent for Oracle Solaris will create an active full backup.
Bare metal recovery to dissimilar hardware is not supported.
Bare metal recovery of SVM configurations is not supported.
Bare metal recovery from backups created from within non-global zones is not supported.
Bare metal recovery only from file-level backups created by Veeam Agent version 4.0 or later is supported.
Bare metal recovery requires a backup that includes the full contents of the root directory (the --includedirs option must be set to /).
During bare metal recovery, content of ZFS volumes is not recovered.
[For Oracle Solaris on x86 architecture] After booting from Veeam Recovery Media, the system that has only a VMXNET3 network adapter may receive only an IPv6 address and not an IPv4 address.
For file system whose encryption has a keysource unsupported by Veeam Agent, Veeam Agent will offer to specify a passphrase to keep the encryption after restore.
[For flexible mapping] You cannot map a ZFS pool that resides on a disk slice.
[For flexible mapping] You cannot map the system rpool to multiple disks.
[For flexible mapping] Any special ZFS pool configurations, such as RAIDZ, mirroring, cache devices, and so on, are ignored. All the disks assigned to the source ZFS pool are simply added together to form the target ZFS pool.
If Veeam Agent for Oracle Solaris is installed in a global zone on Oracle Solaris 10, it is not installed automatically into non-global zones.
If Veeam Agent for Oracle Solaris is installed in a global zone, store path in non-global zones will not be excluded automatically.
Veeam Agent for Oracle Solaris is unable to perform file system indexing if multiple mlocate tools are present in the system.
[For Oracle Solaris 10] If the network connection between Veeam Agent for Oracle Solaris and Veeam backup repository is interrupted during a backup or restore operation, the operation must be restarted because Veeam Agent for Oracle Solaris cannot automatically reconnect to Veeam backup server.
Paths longer than 1006 symbols cannot be restored during bare metal recovery and must be restored manually afterwards.
During bare metal recovery, access (atime), modified (mtime) and changed (ctime) timestamps are reset for all non-empty files or directories.
After bare metal recovery, you may need to reset, or close and open the OVMM terminal to resolve any possible issues with its behavior.
[For flexible mapping] ZFS pools marked for destruction on the current system are not listed at the Recovery Summary step of the Recovery wizard.

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.
After upgrading to Veeam Backup & Replication 13.0.1, existing Azure Restore Proxies must be removed and redeployed.

Instant Recovery to Microsoft Azure

If you previously added an Azure Compute Account using an existing Microsoft Entra ID application with limited permissions, make sure to update the application permissions as described in the product documentation after upgrading to version 13.0.1 to enable the new Instant Recovery to Microsoft Azure functionality.

Direct Restore to Google Cloud

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

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.

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

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.

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.

Malware Detection

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.
Malware autoscan is not supported for guest operating systems with BitLocker enabled or other encrypted disk types which cannot be decrypted automatically on the mount host.

Veeam Threat Hunter

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.

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.
Backups located on cloud repositories are not shown to users with custom roles but such repositories may remain visible on the tenant side.
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.
Users with the Manage Restores permission cannot cancel an active Publish Disk session.
In the restore wizards, the original location may be pre-filled with destination that is outside of the permitted restore scope for the user.
Encryption passwords are not accessible to users with the Manage Restores permission.
Custom operators may not retrieve all search results when using the search bar in the Backups node.
Standalone agent backups may not appear in restore wizards for users with custom operator roles; however, these backups should be visible in the Backups node.

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

Cloud Connect Backup

If tenant runs Veeam Software Appliance with any patches or hotfixes installed, the Remote Access Console connection to such tenant will fail, even if the Cloud Connect server has the same patches (or hotfixes) installed on it.
Microsoft SQL Server, Oracle, and PostgreSQL transaction log backup to a cloud repository is not supported. However, Backup Copy jobs in the immediate copy mode are supported for copying transaction logs backups to a cloud repository.

Cloud Connect Replication

Cloud gateways running on Veeam Infrastructure Appliance do not support the partial failover operation.
Cloud replica status is not refreshed in real-time but rather periodically. You can press F5 to retrieve the most current state.
vApp-level networks are not supported for the network mapping functionality (only org-level networks).
For non-Windows VMs, guest network settings cannot be detected automatically. Because of that, network mapping in the replication job wizard must be performed manually. Additionally, if you are replicating non-Windows VMs only, you need to manually specify the default gateways for each production network by using the Manage Default Gateways dialog on the Service providers node of the Backup infrastructure tab of the management tree.
Network extension functionality requires static IP addresses assigned to the processed VMs. Dynamic IP addressing via DHCP is not supported, and DHCP must be disabled.
The failover plan session cannot be viewed once the failover has been performed.
Enabling VM auto-import in Cloud Director settings may impact replication functionality.
Using the move functionality of Cloud Director to move cloud replicas may cause virtual disk loss.
The Remote Console and Remote Desktop features are not supported for Cloud Director-based tenants.
If a cloud provider renames the Virtual Switch in Hyper-V and updates the Hardware plan, network mapping will stop working for this Hardware plan. The replicas will be in the “Not connected” status, and failover will not work.
During the execution of the CDP Test Failover Plan, configuration changes to the source VM, such as adding or removing a disk or similar, are not replicated to the target replica VM.

Object Storage Repository

Not all Amazon and Microsoft Azure regions provide archive storage classes used by the Scale out Backup Repository Archive Tier, or the compute resources required for deploying archiver appliances. Consider this limitation when selecting a region.
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.

HPE StoreOnce

Target repositories running HPE StoreOnce version lower than 5.2 don’t support the BLAKE3 hashing algorithm. Health check for the jobs pointing to such repositories is skipped.

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

The first incremental file to tape backup after upgrading to version 13 may take significantly longer than usual. This behavior is expected and occurs only for the initial incremental job following the upgrade.
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.
Occasionally, backup files may not appear in the tenant-to-tape backup properties.

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 plug-in backup job will fail if the plug-in is running a version lower than 13.0.1 and the job targets an encrypted repository, or if encryption is enabled in the application backup policy settings.
After performing a switchover or failover in a VBR High Availability cluster, the Entra ID Tenant backup job may fail with the following error: “The number of restore points in the configuration database and in the Microsoft Entra ID backup repository is different. Rescan the repository to proceed.” To resolve this issue, rescan the Entra ID repository.
Database recovery performed by Veeam Explorer can be retried up to 20 minutes after the failover in the VBR High Availability cluster is completed.
The application backup policy will fail after a failover in a VBR High Availability cluster if a Protection Group rescan is not performed.

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

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

Backup infrastructure

Antivirus software with features like SSL/TLS Filtering may block connectivity for backup infrastructure components (e.g., remote PowerShell or Remote Backup Console). Ensure backup infrastructure activity is whitelisted.
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 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 their names and using 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.
When adding an Veeam Infrastructure Appliance version 13.0 to a 13.0.1 Backup Server, you may see the warning “Failed to synchronize update settings. Error: Failed to invoke SetSettings method.” This does not affect functionality — the appliance remains fully operational.

Veeam Software Appliance

Copy Backup, Export to VBK, VeeamZip and other activities 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.

High Availability

Cluster creation may hang if the Veeam High Availability service (veeamhasvc) is not running on the secondary node. To resolve this, reboot the primary node and verify the cluster creation request and the veeamhasvc service status on the secondary node before retrying.
Cluster synchronization may fail after recreating the backup server certificate on the primary node. To resolve this, restart the veeambackupsvc service on the secondary node.
The console may take longer to update the cluster state after a successful failover whenever the old primary node comes back online. To resolve this, reconnect the console to refresh the cluster state.
Snapshot operations may fail during application-aware processing, if the old primary node comes back online after successful failover. To resolve this, restart the veeambackupsvc service on the secondary node.
For clusters built with IPv6 configuration, the old primary node will not automatically rejoin the cluster after a failover if it comes back online. To resolve this, either keep the old primary node offline and reassemble the cluster with a new secondary node, or remove the cluster IPv6 address via CLI and reboot the server.
The backup console may incorrectly prompt for a failover immediately after a successful switchover. To avoid this, wait a few minutes before reconnecting to the cluster IP.
Automatic update of the secondary node may not retry if interrupted by a power-off, restart, or network disconnect. To resolve this, restart the update on the secondary node using the Host Management Console.
The Entra ID tenant backup job may fail after a failover or switchover. To resolve this issue, perform an Entra ID repository rescan.

Setup and Update

Upgrade may fail if the remote PostgreSQL server is not configured with the recommended settings, as advised by Veeam Compliance Analyzer.
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.
Deployment to Microsoft Windows may fail at the PostgreSQL step if the system locale name contains non‑ASCII characters. To resolve this, switch to an ASCII‑named locale or preinstall PostgreSQL with an ASCII locale.
After updating backup server to 13.0.1, re-run the wizard for each Linux mount server or distribution server to ensure components are redeployed properly.
After updating backup server to 13.0.1, remove existing Azure Restore Proxies and deploy new ones to ensure proper functionality.
After updating backup server to 13.0.1, update the granular permissions of your custom role for the Azure Compute Account to enable the new Instant Recovery to Azure feature.
Upgrade may fail if the remote PostgreSQL server is not configured with the recommended settings: max_connections = 3000 and max_wal_senders = 0, as advised by Veeam Compliance Analyzer. For details on the configuration file, see https://www.postgresql.org/docs/16/config-setting.html#CONFIG-SETTING-CONFIGURATION-FILE.

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.
File-level restore for Windows backups without a system disk may fail.
Downloading large files during File-level restore may fail.
Veeam Intelligence may fail to open when multi-factor authentication (MFA) is enabled.
Oracle guest processing retention option cannot be changed via the Web UI.

Remote Console

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.
Remote console auto-update functionality is supported starting from version 12.3.2 Patch 1 (build 12.3.2.4165).
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

When adding backup servers running version 12 to software appliance Veeam Enterprise Manager, use Active Directory (AD) credentials. Ensure the domain portion is capitalized in the format: username@DOMAINNAME.
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.

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.

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 the software

Veeam Software Appliance

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 & Replication 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.

Upgrading Veeam Software Appliance

The Veeam Software Appliance includes a built-in automated update engine, simplifying the installation of patches, updates, and major versions. Update settings are centrally managed from the backup server and are accessible in the Backup Infrastructure view within the Veeam Backup & Replication web UI, enabling monitoring and control of updates across your backup environment. Although the update engine is preconfigured by default, it is strongly recommended to review and adjust maintenance window settings to meet your organization’s operational requirements. Additionally, update configuration and status can be viewed or modified individually on each server using the Host Management interface.

Upgrading Veeam Hardened Repository

The Veeam Infrastructure Appliance allows you to upgrade a Hardened Repository v2 to the latest version using the corresponding option in the GRUB menu. Keep in mind that the upgrade process may take some time.

Note: If the Hardened Repository v2 also has the VMware proxy role, you must: Rerun the Linux Host Wizard, click Upgrade on the proxy component and rerform a rescan operation.

Installable Software on Microsoft Windows

Installing Veeam Backup & Replication

To install the Veeam Backup & Replication 13 server and management console to a Microsoft Windows machine:

Download the latest ISO version since it will have the latest available cumulative patch built in.
Mount the ISO and use autorun or the Setup.exe file. Click Install in the Veeam Backup & Replication 13 splash screen.
Select the Install Veeam Backup & Replication option.
Accept the terms of Veeam Backup & Replication and 3rd party components license agreements to install the product. You can find a copy at veeam.com/eula.html
Provide the setup program with your license file.
Review the default installation settings. To change the defaults, click Customize Settings and go through additional wizard steps.
Click Install to start the installation and follow the setup wizard steps.
Launch the backup console by clicking the Veeam Backup & Replication product icon on your desktop and specify localhost to connect to the local backup server.

Installing Veeam Backup Enterprise Manager

If you want to manage one or more Veeam Backup servers with a centralized management web UI, install Veeam Backup Enterprise Manager. You only need one Enterprise Manager installation per environment.

To install Veeam Backup Enterprise Manager:

Mount the ISO and use autorun or the Setup.exe file. Click Install in the Veeam Backup & Replication 13 splash screen.
Select the Install Veeam Backup Enterprise Manager option.
Accept the terms of the License Agreement to install the product.
Provide the setup program with your license file.
Review the default installation settings. To change the defaults, click Customize Settings and go through additional wizard steps.
Click Install to start the installation and follow the setup wizard steps.
Once the installation is complete, access the Veeam Backup Enterprise Manager web UI by clicking the Veeam Backup Enterprise Manager product icon on your desktop.

Uninstalling Veeam Backup & Replication or Veeam Backup Enterprise Manager

From the Start menu, select Control Panel > Add or Remove Programs.
In the programs list, select Veeam Backup & Replication or Veeam Backup Enterprise Manager and click the Remove button.
In the programs list, select and remove any additional remaining Veeam components.

Upgrading Veeam Backup & Replication

Veeam Backup & Replication 13 supports an automated in-place upgrade from version 12.3.1 (build 12.3.1.1139) or later, which preserves all product settings and configuration. To upgrade from earlier versions, contact Veeam Customer Support.

Use the checklist below to ensure your infrastructure is ready for the Veeam Backup & Replication upgrade. The built-in configuration check mechanism of the Veeam Backup & Replication Upgrade wizard performs some of the checks. Still, you can control them manually before starting the upgrade procedure.

Licensing

Veeam Backup & Replication 13 supports the same license file format, so you can use your existing license file to install version 13.
Your support contract must be active as of the date when the product build you are installing was built. This is determined by the Support Expiration date in your installed license. If required, you can install a new license during the upgrade procedure.

System Requirements

Verify that the backup server to be upgraded is running a supported operating system as specified in System Requirements. If not, perform a configuration backup, install Veeam Backup & Replication 13 on a supported OS, and restore the configuration backup created earlier. To learn how to perform the migration, see the Migrating Veeam Backup & Replication to Another Backup Server section in the Veeam Backup & Replication User Guide.
Ensure that the backup server has sufficient disk space. The minimum disk space is calculated dynamically during the system configuration check in the upgrade procedure. It is based on the list of required packages to be installed on the machine and usually is about 9 GB. We recommend allocating at least the minimum disk space calculated during the system configuration check, but not less than 55.5 GB: 3 x ISO size (50.5 GB) in the selected installation path (for example, D:) plus 5 GB for the database operations on the system volume (for example, C:).
Make sure that backup infrastructure components meet the system requirements listed in the System Requirements section of this document. In particular, ensure all backup infrastructure servers are based on 64-bit operating systems.
Ensure that the environment you will protect with Veeam Backup & Replication meets the requirements listed in the System Requirements section of this document.
Make sure that all necessary ports are open.
Make sure that all necessary permissions are granted.
Do you have legacy per-machine backup format with single metadata file? Detach or upgrade such backups to a new format to proceed with the upgrade.
Do you have legacy backup copy jobs? Switch your existing backup copy jobs to a supported mode before upgrading.
Do you have nested repository paths? Configurations where one repository is located inside another are no longer supported.
Do you use UNC path in export vbk wizard? Configurations with such settings are no longer supported.
Do you have file copy jobs? The backup server can no longer be used as a destination for File Copy jobs. Update the configuration for these jobs before proceeding with the upgrade.
Do you have Veeam Hardened Repository v2 added to backup infrastructure? Consider upgrading Veeam Hardened Repository to the latest version using Veeam Infrastructure Appliance.
Do you have FIPS mode option enabled? Persistent components will be required for guest processing.
Do you have trusted hosts hardening set to Manual? After the upgrade, open the backup console and make sure all your backup infrastructure servers are trusted.
Do you have any jobs using the transform previous backup chains into rollbacks option? This option has been removed from the product, and such jobs are no longer supported.
The following features are no longer available in the product.
Deprecated features:
- Restore point–based retention is no longer available for newly created jobs.
- Reversed incremental backup mode is no longer available for newly created jobs.
- Single-storage backup format option is no longer available in the repository settings.
- Active Directory–based authentication is no longer available for new Veeam Cloud Connect tenants.
Discontinued features:
- Universal Application-Item Recovery wizard (U-AIR).
- Initiating restore by double-clicking VBK/VBM files in Windows Explorer.
- Burning Recovery Media to a CD/DVD/BD media.
- Veeam Cloud Connect Portal
Are you using installations of Veeam Backup & Replication and Veeam Backup for Microsoft 365 on the same machine? First upgrade Veeam Backup for Microsoft 365, second upgrade Veeam Backup & Replication.
Are you using Server 2019-based ReFS backup repositories? If yes, avoid upgrading them to Server 2022 or mounting ReFS volumes from Server 2019 to new Server 2022 installations until you read this thread on Veeam R&D forums. Microsoft has addressed the known regression in the ReFS format upgrade code, and the fix is now publicly available.
Are you using Scale-Out Backup Repositories with immutable performance tier extents? Make sure that all extents have the same immutability settings.
Are you using a customized AntivirusInfos.xml file? During the upgrade, Veeam Backup & Replication will replace it with the default file. Make sure that you save your customized file at another path and make necessary changes to the default file after the upgrade.
Azure compute accounts based on Azure AD user credentials (created with the Use the existing account option) are obsolete. Replace these accounts with new ones to restore workloads to Microsoft Azure, use the Microsoft Azure archive storage or Microsoft Azure Plug-in for Veeam Backup & Replication appliance.
Are you using integration with Veeam Backup for Microsoft Azure? If yes, after upgrading to Veeam Backup & Replication 13 and replacing the obsolete accounts from p.21, select the existing Microsoft Azure compute account in the Manage Cloud Credentials, click Edit, and go through the Microsoft Azure Compute Account wizard to update account permissions. Otherwise, you can face problems when adding an external repository with backups created by Veeam Backup for Microsoft Azure.

Integration with Veeam Management and Monitoring Products

Are you using Veeam ONE to monitor your backup infrastructure? If yes, upgrade it first. Veeam ONE v13 supports monitoring of backup servers version 12 or later.
Are you using Veeam Backup Enterprise Manager? If yes, start the upgrade procedure with this component. Veeam Backup & Replication should be upgraded after that. If you have a backup server installed on the same machine, upgrade it immediately after completing the upgrade of the Veeam Backup Enterprise Manager server. Otherwise, the Veeam Configuration Database Connection Utility (DBConfig) utility will not work correctly for Veeam Backup & Replication.
Are you using the Veeam Backup Enterprise Manager server added to Veeam ONE? If yes, first upgrade Veeam ONE, second upgrade Veeam Backup Enterprise Manager, and third upgrade Veeam Backup & Replication.
Are you using Cloud Connect? If yes, consider the following:
- Check with your Cloud Connect service provider if they have already upgraded their systems to at least the version you are upgrading to.
- Ensure your Cloud Connect tenants use the supported Veeam product versions. The minimal supported tenant versions are: Veeam Backup & Replication 12.3.2.3617, Veeam Agent for Windows 6.3.2, Veeam Agent for Linux 6.3.2, Veeam Agent for Mac 2.3.1. Tenants running Veeam Software Appliance 13.0.0.4967 are not supported and must be upgraded to 13.0.1.
- The Veeam Cloud Connect Portal functionality is deprecated and cannot be used anymore.

Integration with Veeam Backup Agents and Enterprise Plug-Ins

Are you using Veeam Agents managed via Veeam Backup & Replication?
- If you use versions Veeam Agent for Microsoft Windows or Veeam Agent for Linux below 6.3.1, they will stop working after upgrading to Veeam Backup & Replication 13. In this case, we recommend immediately upgrading Veeam Agent for Microsoft Windows or Veeam Agent for Linux to 13. If you use Veeam Agent for Microsoft Windows or Veeam Agent for Linux 6.3.1 or later, they will continue working after upgrading to Veeam Backup & Replication 13, but new features implemented in Veeam Backup & Replication 13 will not be supported. In this case, you can upgrade Veeam Agent for Microsoft Windows or Veeam Agent for Linux to 13 later if the support of new features is not critical for you.
- If you use Veeam Agent for Mac below 2.3.1, it will stop working after upgrading to Veeam Backup & Replication 13. In this case, we recommend immediately upgrading Veeam Agent for Mac to 13. If you use version 2.3.1 or later of the agent, it will continue working with Veeam Backup & Replication 13, but new features of Veeam Backup & Replication 13 will not be supported. We recommend upgrading the agent to version 13 at your earliest convenience.
Are you using Veeam Plug-In for Oracle RMAN, Veeam Plug-In for SAP HANA, Veeam Plug-In for SAP on Oracle, Veeam Plug-In for IBM Db2 or Veeam Plug-In for Microsoft SQL Server? If yes, you upgrade Veeam Backup & Replication first, then you can upgrade Veeam Plug-ins.

Integration with Storage Systems

IBM FlashSystem: If you are using IBM FlashSystem Plug-In for Veeam Backup & Replication, upgrade it to version 2.3.77 or later. If the plug-in version is lower than the minimum required, storage integration will not function.
Hitachi VSP: If you are using Hitachi Plug-In for Veeam Backup & Replication, storage integration will stop working after the upgrade. Plug-in version with support for Veeam Backup & Replication will be released by the vendor later.
HPE XP: If you are using HPE XP Plug-In for Veeam Backup & Replication, storage integration will stop working after the upgrade. Plug-in version with support for Veeam Backup & Replication will be released by the vendor later.
NEC Storage V Series: If you are using NEC Storage V Series Plug-In for Veeam Backup & Replication, storage integration will stop working after the upgrade. Plug-in version with support for Veeam Backup & Replication will be released by the vendor later.
Make sure your storage systems work on a supported operating system:
- Cisco HyperFlex: the minimum supported operating system version is v5.0 (2x). Upgrade to it or remove the storage arrays from the backup server configuration. Also note that support for Cisco HyperFlex in this release is experimental.
- HPE Nimble: the minimum supported operating system version is 5.2. Upgrade to it or remove the storage arrays from the backup server configuration.
- Dell Data Domain: the supported operating system version is 7.9 to 8.5. Upgrade to it, or the backup jobs pointed to this repository will fail to start.
- ExaGrid: the minimum supported operating system version is 7.2.0 P08. Upgrade the storage array and Veeam Backup & Replication, open the corresponding Linux host properties and complete the wizard to install persistent data mover components on the storage array. If the same array was added twice under different names in the previous version, complete the wizard for one of the hosts and re-point all backup repositories to it.
- Fujitsu CS800: the minimum supported operating system version is 5.2.0. Upgrade the storage array and Veeam Backup & Replication, open the corresponding Linux host properties and complete the wizard to install persistent data mover components on the storage array. If the same array was added twice under different names in the previous version, complete the wizard for one of the hosts and re-point all backup repositories to it.
- Infinidat InfiniGuard: the minimum supported operating system version is 5.2.0. Upgrade the storage array and Veeam Backup & Replication, open the corresponding Linux host properties and complete the wizard to install persistent data mover components on the storage array. If the same array was added twice under different names in the previous version, complete the wizard for one of the hosts and re-point all backup repositories to it.
- Quantum DXi: the minimum supported operating system version is 5.2.0. Upgrade the storage array and Veeam Backup & Replication, open the corresponding Linux host properties and complete the wizard to install persistent data mover components on the storage array. If the same array was added twice under different names in the previous version, complete the wizard for one of the hosts and re-point all backup repositories to it.

Upgrade Process

Make sure the latest run for all existing jobs has been completed successfully. Rerun any failed jobs.
Ensure there are no running jobs, restore sessions, Instant Recovery sessions, or SureBackup jobs. We recommend that you do not stop running jobs and let them complete successfully.
Disable any periodic and backup copy jobs temporarily to prevent them from starting during the upgrade.
Disable CDP policies.
Ensure there are no active tasks from standalone (unmanaged) agents.
Ensure there are no active Veeam Disaster Recovery Orchestrator tasks.
Perform the configuration backup, as described in Running Configuration Backups Manually.
Ensure you have configuration backup encryption enabled. Otherwise, stored credentials will not be included in it. For more information, see Creating Encrypted Configuration Backups.

Upgrading Veeam Backup & Replication Server

Download the latest ISO version since it will have the latest available cumulative patch built in.
Ensure there are no active processes, such as any running jobs and restore sessions. We recommend that you do not stop running jobs and let them complete successfully instead. Disable any periodic and Backup Copy jobs so that they do not start during the upgrade.
Perform a backup of the corresponding SQL Server configuration databases used by the backup server so that you can easily go back to the previous version in case of issues with the upgrade. You can also use the built-in configuration backup functionality.
Mount the product ISO and use autorun or run the Setup.exe file. Click Upgrade in the Veeam Backup & Replication 13 splash screen.
Select the Upgrade Veeam Backup & Replication option.
Follow the upgrade wizard steps as outlined in the installation procedure above. Be sure to select the same SQL database and instance used by the previous product version.
Open the Veeam Backup & Replication user interface. If necessary, the automated upgrade wizard will automatically appear, prompting you to upgrade product components running on remote servers. Follow the wizard to complete the upgrade process.
If some remote servers are unavailable at the time of the upgrade, you can run the Upgrade wizard at any time later from the main product menu. Note that jobs cannot use out-of-date product components until updated to the backup server version.
Enable any scheduled jobs that you have disabled before the upgrade.

Please note that immediately after the upgrade, backup server performance may be impacted due to the configuration database being optimized by the maintenance job. This can take up to an hour, depending on the database size.

Upgrading Veeam Backup Enterprise Manager

To upgrade Veeam Backup Enterprise Manager to version 13, you must run version 12.3.1 (build 12.3.1.1139) or later on the supported operating system (refer to the System Requirements section of this document). To upgrade from previous versions, contact Veeam Customer Support.

Download the latest ISO version since it will have the latest available cumulative patch built in.
Perform a backup of the corresponding SQL Server configuration databases used by the Enterprise Manager server so that you can go back to the previous version in case of issues with the upgrade.
Mount the product ISO and use autorun or run the Setup.exe file. Click Upgrade in the Veeam Backup & Replication 13 splash screen.
Select the Upgrade Veeam Backup Enterprise Manager option.
Follow the setup wizard steps as outlined in the installation procedure above. Be sure to select the same SQL database and instance used by the previous Veeam Backup Enterprise Manager version.
If you have the Veeam Backup & Replication server installed on the server, upgrade it immediately after completing the upgrade of the Veeam Backup Enterprise Manager server. Otherwise, this local backup server will not be able to run jobs.

Please note that immediately after the upgrade, Enterprise Manager performance may be impacted due to the configuration database being optimized by the maintenance job. This can take up to an hour, depending on the database size.

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.