Veeam Backup & Replication 12.3 Release Notes

This document provides last-minute information about Veeam Backup & Replication 12.3, 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 12.3 is available for download at veeam.com/backup-replication-download.html starting from December 3, 2024.

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

See next:

System Requirements
Known Issues and Limitations
Installing Veeam Backup & Replication
Uninstalling Veeam Backup & Replication
Upgrading Veeam Backup & Replication
Licensing
Updating Veeam Backup & Replication License
Technical Documentation References
Technical Support
Contacting Veeam Software

System Requirements

We recommend that all 3rd party software and components are kept at the latest patch level since these updates often address issues that can cause slow performance, backup failures, and data corruption.

VMware Infrastructure

Platforms

VMware vSphere
VMware vCloud 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 8.0 (up to 8.0 U3)
ESXi 7.x
ESXi 6.x

Software

vCenter Server or vCenter Server Appliance 8.0 (up to 8.0 U3)
vCenter Server or vCenter Server Appliance 7.x
vCenter Server or vCenter Server Appliance 6.x
vCloud Director 10.1 to 10.6

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

Veeam CDP

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

The minimum supported ESXi version is 6.5 U2.
For Cloud Director Continuous Data Protection, the version of target hosts must be 7.0 or higher. Target hosts of versions 6.5 and 6.7 are not supported.
Cisco HyperFlex 4.5 (2a) and later can be used as a source or target only with VMware vSphere 7.0 U2 and later. With the previous versions of VMware vSphere, Cisco HyperFlex is not supported.
Minimum 16GB 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.

vSphere Virtual Machines

Virtual Hardware

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

All operating systems supported by the VMware vSphere version in use.
Microsoft VSS integration is supported for Microsoft Windows Server 2008 and later, except for Nano Server (due to the absence of VSS framework).
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)

Software

VMware Tools (optional, recommended)

Microsoft Infrastructure

Platforms

Microsoft Windows Server Hyper-V
Microsoft Hyper-V Server (free hypervisor)
Microsoft Azure Stack HCI

Hosts

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

Microsoft Windows 11 Hyper-V (versions 21H2, 22H2, 23H2, 24H2) and Windows 10 Hyper-V (versions 1909 to 23H2) 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.

Microsoft Nano Server with Hyper-V role installed is not supported for any functionality.

Software

Microsoft Windows PowerShell 5.1 (optional, enables network-less guest processing)
Microsoft System Center Virtual Machine Manager 2012 SP1 to 2025

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

Hyper-V Virtual Machines

Virtual Hardware

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

All operating systems supported by the Hyper-V version in use.
Microsoft VSS integration is supported for Microsoft Windows 2008 and later, except for Nano Server (due to the absence of VSS framework). The persistent guest agent requires Windows Server 2008 SP2 or later.
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)

Software

Hyper-V integration components (optional, recommended)

Proxmox VE Infrastructure

Virtualization Platform

Proxmox VE version 8.2 or later 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.

Proxmox VE Virtual Machines

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.

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)

Oracle Linux Virtualizaion Manager and Red Hat Virtualization

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 for VMs

During the deployment process, the Veeam Backup for OLVM and RHV Backup Appliance (backup appliance) is deployed on a KVM host as a dedicated Linux-based VM. The backup appliance configuration determines the maximum number of tasks (backup or restore sessions) that the backup appliance can handle in parallel. If this number is exceeded, the backup appliance will not start a new task until one of the current tasks finishes. By default, the backup appliance supports 4 concurrent tasks and runs on a VM with the following configuration:

CPU: 6 vCPU
Memory: 6 GB RAM
Disk Space: 100 GB for product installation, internal database files, 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: 1 vCPU
Memory: 1 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)

Veeam Backup & Replication Server

Hardware

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

Memory: 8 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 Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

Configuration Database

PostgreSQL 14.x, 15.x (version 15.10.1 is included in the setup)
Note that Veeam Backup & Replication does not support PostgreSQL installations on cloud database services (for example, Amazon Relational Database Service (RDS)).
Microsoft SQL Server 2012 to 2022

Software

Microsoft .NET Framework 4.7.2 (included in the setup)
Microsoft Windows Desktop Runtime 8.0 (included in the setup)
Microsoft ASP.NET Core Shared Framework 8.0 (included in the setup)
Microsoft Windows PowerShell 5.1 (included in the setup)
Microsoft SQL Server System CLR Types (both for SQL Server and PostgreSQL, included in the setup)
Microsoft Report Viewer Redistributable 2015 (included in the setup)
Microsoft Universal C Runtime (included in the setup)
Microsoft Visual C++ 2015-2022 Redistributable (included in the setup)
System Center Virtual Machine Manager 2012 SP1 to 2025 Admin UI (optional, to register SCVMM server with Backup & Replication infrastructure)
Microsoft Edge WebView2 Runtime (included in the setup)
Windows Installer 4.5

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 Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

Software

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

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

Hardware

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

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

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

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

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 Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

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

AlmaLinux 9.3
CentOS 7.x
Debian 10.0 to 12.2
Oracle Linux 7 (UEK3) to 9 (UEK R7)
Oracle Linux 7 to 9 (RHCK)
RHEL 7.0 to 9.5
Rocky Linux 9.0 to 9.5
SLES 12 SP4 or later, 15 SP1 or later
Ubuntu 18.04 LTS, 20.04 LTS, 22.04 LTS, 24.04 LTS

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

Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012

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
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012

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 Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)
SMB 3.0 file share backup from Microsoft VSS snapshots requires Microsoft Windows Server 2012 R2 or later.

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

CentOS 7.x
Debian 10.0 to 12.2
Oracle Linux 7 (UEK3) to 9 (UEK R7)
Oracle Linux 7 to 9 (RHCK)
RHEL 7.0 to 9.3
SLES 12 SP4 or later, 15 SP1 or later
Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS

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.

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.

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 Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

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

CentOS 7.x
Debian 10.0 to 12.2
Oracle Linux 7 (UEK3) to 8.3 (UEK R6 U2)
Oracle Linux 7 to 8.5 (RHCK)
RHEL 7.0 to 9.3
SLES 12 SP4 or later, 15 SP1 or later
Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS

Backup Repository Server

These requirements also apply to mount servers (if separated from the repository server), gateway servers for file shares, object storage and deduplicating appliance-based repositories, and cache repository servers.

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.

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 Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

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

AlmaLinux 9.3
CentOS 7.x
Debian 10.0 to 12.2
Oracle Linux 7 (UEK3) to 9 (UEK R7)
Oracle Linux 7 to 9 (RHCK)
RHEL 7.0 to 9.5
Rocky Linux 9.0 to 9.5
SLES 12 SP4 or later, 15 SP1 or later
Ubuntu: 18.04 LTS, 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:

AlmaLinux 9.3
Debian 10.0 to 12.2
RHEL 8.2 to 9.5
Rocky Linux 9.0 to 9.5
SLES 15 SP2 to SP6
Ubuntu 18.04 LTS, 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.

Tape Server

Hardware

CPU: x86-64 processor.

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

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

Network: 1 Gbps or faster.

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 Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

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

CentOS 7.x
Debian 10.0 to 12.2
Oracle Linux 7 (UEK3) to 9 (UEK R7)
Oracle Linux 7 to 9 (RHCK)
RHEL 7.0 to 9.4
Rocky Linux 9.4
SLES 12 SP4 or later, 15 SP1 or later
Ubuntu: 18.04 LTS, 20.04 LTS, 22.04 LTS, 24.04 LTS

WAN Accelerator Server

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.

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 Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

Veeam Backup Enterprise Manager

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 Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

Configuration Database

PostgreSQL 14.x, 15.x (version 15.10.1 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 2012 to 2022

Server Software

Microsoft .NET Framework 4.7.2 (included in the setup)
Microsoft SQL Server System CLR Types (both for SQL Server and PostgreSQL, included in the setup)
Microsoft Report Viewer Redistributable 2015 (included in the setup)
Microsoft Universal C Runtime (included in the setup)
Microsoft Visual C++ 2015-2022 Redistributable (included in the setup)
Microsoft Internet Information Services 7.5 or later
Microsoft URL Rewrite 2.0 for IIS 7
Windows Installer 4.5 (included in the setup)

Client Software

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

Backup Target

Backups can be performed directly to the following disk-based 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.3 to 8.3) with the DDBoost license. Both Ethernet and Fibre Channel (FC) connectivity are supported.
ExaGrid (firmware version 5.0.0 or later).
Fujitsu CS800 (CS800 software 3.4.0 or later).
HPE StoreOnce (firmware version 3.18.18 or later for Gen3 and 4.2.3 or later for Gen4) with Catalyst license. Both Ethernet and Fibre Channel (FC) connectivity are supported.
Infinidat InfiniGuard (InfiniGuard software 3.6 or later).
Quantum (DXi software 3.4.0 or later). Supported Quantum DXi systems include DXi4700 (NAS configuration), DXi4700 (multi-protocol configuration), DXi 4800, DXi 6900, DXi 6900-S, DXi 9000, DXi 9100, and DXi V5000. FIPS-compliant operations mode requires DXi software 4.0 or later.

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

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

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

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

Veeam CDP

The following source and target datastores are supported:

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

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

Tape

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

LTO3-LTO9
IBM 3592 (TS1160 and TS1170)

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

Drivers

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

Storage Snapshot Integrations

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

Built-in Storage Systems

Cisco HyperFlex HX-Series

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

Dell VNX, VNX2, VNXe, Unity and Unity XT

NFS, Fibre Channel (FC), or iSCSI connectivity for VMware and Veeam Agent integrations
Dell VNX/VNX2 all OE versions are supported
Dell VNXe OE versions 3.x
Dell Unity XT/Unity OE versions 5.0 up to 5.4

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

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 7-mode versions 8.2 up to 8.2.5
ONTAP cluster-mode versions 9.1 to 9.16.1

HPE 3PAR StoreServ

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

HPE Primera

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

HPE Alletra 9000

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

HPE Alletra MP

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
iSCSI is supported starting from OS version 10.3.
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.0 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

HPE StoreVirtual (formerly LeftHand / P4000 series) and StoreVirtual VSA

iSCSI connectivity for VMware and Veeam Agent integrations
LeftHand OS versions 9.5 to 12.8
HPE SV3200 (LeftHand OS version 13) is not supported

IBM N Series

NFS, Fibre Channel (FC), or iSCSI connectivity for VMware and Veeam Agent integrations
ONTAP 7-mode versions 8.2 up to 8.2.5
ONTAP cluster-mode versions 9.1 to 9.16.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 7-mode versions 8.2 up to 8.2.5
ONTAP cluster-mode versions 9.1 to 9.16.1

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 7-mode versions 8.2 up to 8.2.5
ONTAP cluster-mode versions from 9.1 up to 9.16.1
NetApp ASA r2 systems (ASA A1K, ASA A70, and ASA A90) are not supported.

Nutanix Files

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

Universal Storage API Integrated Systems

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 family 5978 or later 5978 family updates and PowerMaxOS 10.1.0.0 or later)
Unisphere for PowerMax 9.2.1.6 or later (versions 10.0.x are not supported)

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

Hitachi VSP

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
VSP E series (93-03-01-60/00 or later)
VSP F series (88-07-01-x0/00 or later)
VSP G series (88-07-01-x0/00 or later)
VSP 5100 and VSP 5500 (90-05-01-00/00 or later)
VSP 5200 and VSP 5600 (90-08-01-00/00 or later)

HPE XP

Fibre Channel (FC) connectivity for VMware and Veeam Agent integrations
HPE XP8 (90-05-01-00/00 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.2 or later
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)

NEC Storage V Series

Fibre Channel (FC) or iSCSI connectivity for VMware and Veeam Agent integrations
V100, V300 (93-04-21-XX or later), V10e (88-08-09-XX 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

Microsoft Entra ID Plug-in for Veeam Backup & Replication

Backup Server

Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

Backup Console

Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016
Microsoft Windows 11 (versions 21H2, 22H2, 23H2, 24H2)
Microsoft Windows 10 (versions 1909 to 22H2)
Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

Microsoft Entra ID Backup Repository

PostgreSQL 16.x
PostgreSQL 15.x (version 15.10.1 is included in the setup)
PostgreSQL 14.x

Veeam Explorer for Microsoft Active Directory

Microsoft Active Directory Domain Controllers

Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008

The minimum supported domain and forest functional level is Windows 2008.

Veeam Explorer for Microsoft Exchange

Microsoft Exchange

Microsoft Exchange 2019
Microsoft Exchange 2016
Microsoft Exchange 2013

Software

Microsoft Outlook for PST exports (optional)

Veeam Explorer for Microsoft SharePoint

Microsoft SharePoint Server

Microsoft SharePoint Server Subscription Edition
Microsoft SharePoint 2019
Microsoft SharePoint 2016
Microsoft SharePoint 2013
The 3rd party RBS providers are not supported.

Veeam Explorer for Microsoft SQL Server

Microsoft SQL Server

Microsoft SQL Server 2022
Microsoft SQL Server 2019
Microsoft SQL Server 2017
Microsoft SQL Server 2016
Microsoft SQL Server 2014
Microsoft SQL Server 2012
Microsoft SQL Server 2008 R2
Microsoft SQL Server 2008

Veeam Explorer for MongoDB

Only 64-bit versions of the following operating systems are supported for the database server:

Debian 9 or later
RHEL 6.2 or later
CentOS 6.2 or later
Oracle Linux 6.2 or later
Rocky 8.0 or later
Alma 8.0 or later
SLES 12 SP4, SP5
SLES 15 SP1 – SP5
Ubuntu 16.04 or later

MongoDB

MongoDB 8.0
MongoDB 7.0
MongoDB 6.0
MongoDB 5.0

Veeam Explorer for Oracle

Both 32-bit and 64-bit versions of the following operating systems are supported for the database server, according to the Oracle Database version compatibility matrix:

Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows Server 2016
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008
CentOS 7.x
RHEL 7.0 to 9.4
SLES 12 SP4 or later, 15 SP1 or later
Oracle Linux 7 (UEK3) to 9 (UEK R7)
Oracle Linux 7 to 9 (RHCK)

Oracle Database

Oracle 21
Oracle 19
Oracle 18
Oracle 12
Oracle 11

Configuration

Oracle Automatic Storage Management (optional, requires ASMlib present)

Veeam Explorer for PostgreSQL

PostgreSQL

PostgreSQL 17
PostgreSQL 16
PostgreSQL 15
PostgreSQL 14
PostgreSQL 13
PostgreSQL 12

Known Issues and Limitations

Backup infrastructure

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

Proxmox VE

The cluster credentials update session shows as failed despite the credentials update being successful.
Full VM restore process may change VM disk names without changing bus and bus number.
Only the file-level restore is supported for HPE StoreOnce Cloud Bank.
Workers with concurrent tasks set to 1 may turn off and on sporadically if there are 2 or more VMs in a backup job. We do not recommend setting the number of concurrent tasks to less than 4 (default).
Instant Recovery of Proxmox VMs to VMware limitations: UEFI VMs with MBR are not supported; VMs may have an incorrect number of cores per vCPU assigned; static IP addresses are not restored for Windows VMs.
[Resolved in 12.3.1] OS type of VMs restored from backups of other hypervisors is erroneously set as Other.
[Resolved in 12.3.1] Backups of powered-off VMs with PCIe passthrough devices fail due to an attempt to back up those devices.
[Resolved in 12.3.1] Backup of VMs that are linked clones is not supported and will now correctly fail instead of processing only the base disk without capturing delta.
[Resolved in 12.3.1] Open vSwitch (openvswitch, OVS) and its associated features are not supported

Oracle Linux Virtualization Manager and Red Hat Virtualization

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
Veeam Backup for OLVM and RHV does not create application-consistent backups. You can use Veeam Agent for Linux or Veeam Agent for Windows to create application-consistent backups.
Veeam Backup for OLVM and RHV supports VM backups with mixed virtual disks: RAW and QCOW2.
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.
By default, backup encryption is disabled for backed-up data. However, you can enable encryption at the repository level. For more information, see the Access Permissions section of the Veeam Backup & Replication User Guide.
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.
VeeamZIP retention is not supported.
You cannot back up a VM while previewing its snapshot.
You can back up each VM with one backup job at a time. If a VM is already being processed by a backup job, another backup job will not start processing this VM unless the currently running backup operation completes.
You cannot include into a backup job a VM being backed up by 3rd party software or a backup appliance connected to another backup server. Wait for the backup process to complete or stop the job manually, and then add the VM to a backup job.
Since Veeam Backup & Replication does not allow you to assign information about locations to oVirt KVM Manager and backup proxies, job statistics do not include information on the oVirt VM data migration between different geographic regions.
Manual Move backup functionality is not supported for oVirt KVM backups.
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.
To send email notifications on backup job results, Veeam Backup for OLVM and RHV uses account settings configured in the Veeam Backup & Replication console. However, mail servers with SMTP basic authentication are only supported.
Starting from version 4.1, Veeam Backup for OLVM and RHV uses disk alias for configuring disk exclusions in backup jobs.
Veeam Cloud Connect repositories are not supported as backup repositories for Veeam Backup for OLVM and RHV.
Only File-level restores are supported for StoreOnce Cloud Bank.
You can perform Instant Recovery to VMware, Hyper-V, Nutanix AHV hosts from backups created by Veeam Backup for OLVM and RHV. VMware vSphere, Hyper-V or Nutanix AHV hosts must be added to the Veeam Backup & Replication backup infrastructure.
Veeam Backup for OLVM and RHV supports restore from another oVirt instance for the imported backups.
Starting from version 6.0, Veeam Backup for OLVM and RHV supports restore from another platforms backups.
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.
If a VM added to the restore session contains multiple disks, Veeam Backup for OLVM and RHV restores one disk per job at a time.
SureBackup for backups created by Veeam Backup for OLVM and RHV is supported in the Backup verification and content scan only verification mode.
Veeam Backup Enterprise Manager
You can use Veeam Backup Enterprise Manager to file-level restore guest OS files of oVirt VMs and manage oVirt VM backup copy jobs. All other operations are not supported.

VMware

Replication of encrypted VMs with datasets is not supported for vSphere v8.
On ESXi 7.0 and above, the 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.
NSX-T networking is not supported for Veeam Cloud Connect Replication.
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 vCloud Director VMs.
The state of the Standalone VM option of vCloud 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.
Due to a change in ESXi 6.0 Update 1, replication and quick migration to VVol datastores are not possible with either Veeam or vSphere replication.
RDM disks in virtual compatibility mode are skipped during Backup from Storage Snapshot.
Pre-freeze and post-thaw scripts for Linux do not perform elevation to root (sudo) when networkless processing (VIX) is used.
The entire VM restore to the original location does not preserve disk IOPs limits, erroneously removing the associated records from the VMX file. However, restoring to another location will keep these parameters.
Encryption storage policy is not supported for the instant recovery to First Class Disk (FCD).

VMware Cloud on AWS

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

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.
Following the ESXi host update from vSphere 6.x to 7.0, the CDP replica rescan fails with the “Failed to rescan CDP replicas” error. To solve the issue, open a support ticket and request updated CDP components (that have been certified by VMware after the Veeam Backup & Replication 12 GA release).
I/O filter cannot be attached to VMs with snapshots. Remove all snapshots from VMs to be protected before creating a CDP policy.
Using a vCenter Server as a CDP proxy is not supported and may cause various issues.
Setup programs of specific primary storage integration plug-ins leave the CDP service stopped after the installation. Please verify the service state following the installation and start it manually if needed.
Windows Server 2012 is not supported for the Veeam CDP due to incompatibility with the FIPS-certified version of OpenSSL. To use this functionality, disable FIPS-compliant operations in the Security options of the backup server or upgrade your backup server and CDP proxies to Windows Server 2012 R2 or later.
Cloning a Cloud Director CDP policy with automatic proxy selection fails with the “Invalid proxy type” error
To set a short-term retention period longer than 24 hours, it is necessary to update the I/O filters to the latest version. If you are using Cloud Connect Replication, make sure your provider updates the I/O filter to the latest version before you set a short-term retention period longer than 24 hours.

Hyper-V 2016/2022

The Hyper-V 2022 host forces the VM configuration version to be updated from 5.0 to 8.0.
Restoring VMs, which were backed up from Hyper-V 2012R2 (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.

Hyper-V

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.
Backup of VMs with virtual disks located both on local and shared CSV/SMB storage is not supported due to Hyper-V limitation.
Off-host backup from deduplicated volume fails if the Data Deduplication feature is disabled on the backup proxy server.
Shared VHDX virtual disks can be backed up in crash-consistent mode only.
Transaction log backup for Microsoft SQL Cluster running on shared VHDX is not supported due to a Microsoft limitation (no VSS support for Shared VHDX).
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.

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.

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.

Agent Management

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.
Backup agents will fail to perform retention for backups located at capacity extents after backup chain has been evacuated between Scale-out repository object storage performance extents running in direct connection mode.

Microsoft Windows Server Failover Cluster

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

Direct Restore to Amazon EC2

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

Direct Restore to Microsoft Azure and Azure Stack Hub

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.
Microsoft Azure Stack subscription limits are not validated before the restore.

Direct Restore to Google Cloud

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

Malware Detection

Microsoft Windows Defender does 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.
Indicators of compromise detection remains inactive if File system activity analysis is disabled. To workaround this issue enable both options in the Malware Detection Settings > File Detection properties.

Windows File Level Restore

File-level restore may fail if a VM you are restoring from lacks free disk space at the time of backup.
Storage Spaces volumes are not supported for file-level recovery. Consider using Instant VM Recovery to recover guest files from such VMs. Note that Microsoft does not support Storage Spaces within a VM.
To restore files from deduplicated volumes, ensure the mount server and backup console are installed on Windows Server with the Data Deduplication feature enabled and the Windows Server version is the same or greater than the version of the VM you are restoring from. Otherwise, the deduplication driver incompatibility will cause file-level recovery errors with false data corruption reports.
CopyTo operation cannot be canceled in the remote mount server case.

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

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.
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).
Restoring files to the original location for Windows VMs is not supported. To work around this, use Windows FLR instead.

Guest File System Indexing

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

Replica Failover

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

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.

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.

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.

Cloud Connect Backup

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 providers cannot import their tenants’ backups on the Cloud Connect server — the operation has been blocked in the UI.

Cloud Connect Replication

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 vCloud Director settings may impact replication functionality.
Using the move functionality of vCloud Director to move cloud replicas may cause virtual disk loss.
The Remote Console and Remote Desktop features are not supported for vCloud 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.
Tenants’ CDP failover plans are not visible in the Cloud Connect Self-Service portal.
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

Backup Copy

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

Object Storage Repository

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

Tape

Source backup chain upgrade for VM backups will cause Backup to Tape to process the upgraded chain from scratch to ensure the data and metadata consistency on the tape media.
File to Tape job fails to build a list of files to process if the catalog contains files with certain Unicode symbols.
Backup to Tape job will perform a full backup during each run if the source forever forward incremental backup job or backup copy job in the immediate copy mode has a retention of less than 3 restore points or if the source backup copy job in the periodic copy mode has a retention of less than 4 restore points.
SQL, PostgreSQL, and Oracle transaction log backup to tape are not supported.
If you manage several tape libraries with the same Veeam backup server and use barcodes to identify tapes in these libraries, all barcodes must be unique across all tape libraries.

Applications

After migrating the Veeam configuration (using .bco file) and upgrading from a version lower than 12.1, restore from application plug-in backups that reside on the Capacity Tier or download of these backups fails. Contact our Customer Support to get a workaround.
MongoDB incremental backups to object storage based backup repository with encryption enabled fails. Contact our Customer Support for a workaround,
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.

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.

Microsoft Entra ID Plug-in for Veeam Backup & Replication

The Microsoft Entra ID Logs backup job is incorrectly displaying the job progress

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.

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.
32-bit Oracle application running on 64-bit operating systems 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.

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

NetApp ONTAP

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

HPE StoreOnce

When using Veeam Agent for Windows to back up a Windows Cluster with multiple nodes to an HPE StoreOnce repository, the following Catalyst Copy job may mark target restore points as incomplete. This occurs because the integrity check is skipped for the second and all subsequent nodes, despite the data copy completing successfully.

Globalization

Non-ASCII characters are not supported in the product installation path. Some user interface (UI) controls may appear misplaced when a non-standard display DPI setting is set. To work around the issue, change the DPI setting to 100% or 125% using the Display settings of the Windows Control Panel.

Veeam Intelligence

Windows Server 2012 is not supported for the Veeam Intelligence assistant. To use this functionality, your backup server and backup console must run on Windows Server 2012 R2 or later.

User Interface

If a NETBIOS domain name differs from a fully qualified domain name, the AD browser dialog will resolve the NETBIOS domain name incorrectly when new credentials are added. To work around the issue, fix credentials manually.
Job filter functionality includes unmanaged Linux agent jobs under both Server and Workstation workload types.

Enterprise Manager

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.
The .NET 3.5.1 WCF HTTP Activation Windows component prevents Enterprise Manager from functioning. To work around the issue, uninstall this component.
The self-service configuration dialog does not display correctly in Microsoft Internet Explorer 11. To work around the issue, use another supported browser.
Upgrade process will fail if REST API certificate binding does not have correct Certificate Store Name specified. Read https://www.veeam.com/kb4660 for more details.
Instant Recovery to another location will fail with the “Failed to prepare change storage” error if the Redirect cache option is used.
Restoring Oracle application items to another server from a Windows-based machine backup fails if the default logging level is enabled in Enterprise Manager. Contact Veeam Support to get the registry key for changing the logging level.

PowerShell

Restores from imported backups residing on an SMB (CIFS) share are not supported through PowerShell.

Setup and Upgrade

Windows Smart Screen may block the Veeam Backup & Replication ISO file, preventing it from mounting. To work around the issue, go to the ISO file properties, open the General tab, and unblock the file in the Security section.
For Windows Server Hyper-V 2012 and Windows Server Hyper-V 2012 R2, the first job run after the upgrade will not use the changed block tracking information and thus may take longer than expected.
After upgrading to Veeam Backup & Replication 12.3, the next scheduled backup job run will perform a full scan-based incremental run for all machines with virtual disks formatted with NTFS and cluster size 64KB or larger.
Veeam Backup & Replication 12.3 setup may fail to install the configuration database if the system has more than one user account in the list with identical names (for example, local machine\administrator and domain\administrator).
Automatic update of remote backup consoles cannot be performed for versions 12.1.X. Use the standalone console installer or 12.3 ISO to upgrade manually.

Installing Veeam Backup & Replication

Veeam Backup & Replication Server

To install the Veeam Backup & Replication 12.3 server and management console:

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

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

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

Upgrading Veeam Backup & Replication

Veeam Backup & Replication 12.3 supports an automated in-place upgrade from any version 11a (build 11.0.1.1261), which preserves all product settings and configuration. To upgrade from earlier versions, contact our Veeam Customer Support.

Use the following checklist 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 12.3 uses the same license file format introduced with version 10, so you can use your existing version 10/11 license file to install version 12.3.
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 the installed license. If required, you can install a new license during the upgrade procedure.
Are you using Veeam Backup Starter? This edition has been discontinued, so Veeam Backup & Replication 12.3 will not accept such a license file. Please download a replacement license file from the Veeam Customer Support Portal before upgrading.

System Requirements

Check if the backup server to be upgraded is installed on the supported operating system version according to System Requirements. If it is not, create a configuration backup, install Veeam Backup & Replication 12.3 on the supported OS first, and then 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 on the flight after the system configuration check during 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 providing the minimum disk space calculated during the system configuration check, but not less than 39.5 GB of disk space: 3 x ISO size (34.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.
Note that starting from Veeam Backup & Replication 12 (build 12.0.0.1420), Microsoft Windows Server Semi-Annual Channel versions are not supported. If you are upgrading from earlier Veeam Backup & Replication versions, make sure you do not have such servers in your backup infrastructure.
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.
Are you using a hardened repository? Consider the following:
- Ensure that any Linux server associated with the hardened repository is configured to use a non-root account. For more information, see this Veeam KB article.
- Ensure that the backup directory has 0700 permissions and does not have the SGID bit. For more information, see this Veeam KB article.
- Veeam Backup & Replication does not support symlinks in the path to the hardened repository.
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. For more information, see this Veeam KB article.
Are you using File to Tape jobs? Consider the following:
- They have been re-engineered for scalability and are no longer free with Veeam Backup & Replication 12.3. You will have a grace period of 3 months following the upgrade to Veeam Backup & Replication 12.3, during which your existing jobs will not consume a license. For more information, see Instance Consumption for Object Storage Backup, File Backup, and File to Tape Jobs.
- File to tape jobs can now process Distributed File Systems (DFS) data.
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.
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 12.3 and replacing the obsolete accounts from p.12, 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 6.0.
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.
Are you using Azure Local (formerly known as Azure Stack HCI)? You may need to apply an updated WDAC policy before upgrading if you have WDAC enabled on your Azure Local nodes. For more information, see this Veeam KB article.

Integration with Veeam Management and Monitoring Products

Are you using Veeam ONE to monitor your backup infrastructure? If yes, upgrade it first. Veeam ONE supports monitoring of backup servers version 11a or later.
Are you using Veeam Backup Enterprise Manager? If yes, consider the following:
- Important! Starting with Veeam Backup Enterprise Manager 12, a new port (port 9405) is used for certificate communication between Enterprise Manager and Veeam Backup & Replication. Ensure that your firewalls are configured to take into account this new port to avoid communication issues between Enterprise Manager and Veeam Backup & Replication.
- 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.
- From Veeam Backup Enterprise Manager, you cannot edit jobs managed by backup servers of earlier versions, as well as Veeam Agent backup jobs, file share backup jobs, and backup copy jobs. To edit the settings of such jobs, use the Veeam Backup & Replication console.
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.0, Veeam Agent for Windows 6.0, Veeam Agent for Linux 6.0, Veeam Agent for Mac 2.0.
Are you using Veeam Recovery Orchestrator? If yes, note that Veeam Disaster Recovery Orchestrator 6.0 is compatible with Veeam Backup & Replication 11a and 12, Veeam Recovery Orchestrator 7.0 — with Veeam Backup & Replication 12, 12.1 and 12.2, Veeam Recovery Orchestrator 7.1 — with Veeam Backup & Replication 12, 12.1, 12.2 and 12.3. If necessary, upgrade Veeam Recovery Orchestrator before upgrading to Veeam Backup & Replication 12.3.

Integration with Veeam Backup for Public Clouds

Are you using Veeam Backup & Replication integrated with Veeam Backup for Public Cloud solutions? If yes, first upgrade Veeam Backup & Replication to version 12.3. Second upgrade plug-ins for Veeam Backup for AWS, Veeam Backup for Microsoft Azure and Veeam Backup for Google Cloud. Third upgrade connected appliances to the most recent version.

Integration with Veeam Backup for Hypervisors

Are you using Veeam Backup & Replication integrated with Veeam Backup for Hypervisors?

Veeam Backup for Nutanix AHV: the plug-in for version 7 of this product is included with the Veeam Backup & Replication 12 redistributable. During the upgrade to version 12.3, the plug-in will be automatically upgraded.

Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization: the plug-in for version 6 of this product is included with the Veeam Backup & Replication 12 redistributable. During the upgrade to version 12.3, the plug-in will be automatically upgraded to the required version.

Veeam Backup for Proxmox Virtual Environment: the plug-in for version 1 of this product is included with the Veeam Backup & Replication 12 redistributable. During the upgrade to version 12.3, the plug-in will be automatically upgraded to the required version.

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 4.0, they will stop working after upgrading to Veeam Backup & Replication 12.3. In this case, we recommend immediately upgrading Veeam Agent for Microsoft Windows or Veeam Agent for Linux to 6.3. If you use Veeam Agent for Microsoft Windows or Veeam Agent for Linux 5.0 or later, they will continue working after upgrading to Veeam Backup & Replication 12.3, but new features implemented in Veeam Backup & Replication 12.3 will not be supported. In this case, you can upgrade Veeam Agent for Microsoft Windows or Veeam Agent for Linux to 6.3 later if the support of new features is not critical for you.
- If you use Veeam Agent for Mac 1.0, it will stop working after upgrading to Veeam Backup & Replication 12.3. In this case, we recommend immediately upgrading Veeam Agent for Mac to 2.3. If you use version 1.0.1 of the agent, it will continue working with Veeam Backup & Replication 12.3, but new features of Veeam Backup & Replication 12.3 will not be supported. We recommend upgrading the agent to version 2.3 at your earliest convenience.
- If you use versions Veeam Agent for IBM AIX or Veeam Agent for Oracle Solaris 3.0 or later, they will continue working after upgrading to Veeam Backup & Replication 12.3, but new features of Veeam Backup & Replication 12.3 will not be supported. In this case, you can upgrade Veeam Agent for IBM AIX or Veeam Agent for Oracle Solaris to 4.6 later if the support of new features is not critical for you.
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. Please note that Veeam Backup & Replication supports only two latest major updates of Veeam Plug-ins. For example, Veeam Backup & Replication 12.3 supports Veeam Plug-in 12.3 and 12.2.

Integration with Storage Systems

IBM FlashSystem: In Veeam Backup & Replication 12.2, the storage snapshot integration functionality was re-implemented as an independent plug-in. If you upgrade Veeam Backup & Replication to version 12.3 from version 12.1 or earlier, after the upgrade, download and install the IBM FlashSystem Plug-in for Veeam Backup & Replication from the Veeam Download page to continue using jobs utilizing storage snapshots on IBM FlashSystem arrays.
Make sure your storage systems work on a supported operating system:
- Huawei: storage arrays of this vendor are not supported for Veeam storage snapshot integration. Remove the storage arrays from the backup server configuration and use other backup transport modes instead.
- Cisco HyperFlex: the minimum supported operating system version is v4.0(2x). Upgrade to it or remove the storage arrays from the backup server configuration.
- HPE 3PAR WSAPI: the minimum supported WSAPI version is 1.5. Upgrade to it or remove the storage arrays from the backup server configuration.
- HPE Nimble: the minimum supported operating system version is 5.0. Upgrade to it or remove the storage arrays from the backup server configuration.
- Dell Data Domain: the supported operating system version is 7.3 to 8.3. Upgrade to it, or the backup jobs pointed to this repository will fail to start.
- HPE StoreOnce: the minimum supported operating system version is 3.18.18 for Gen3 and 4.2.3 for Gen4. Upgrade to it, or the backup jobs pointed to this repository will fail to start.
IBM HyperSwap: If you upgrade Veeam Backup & Replication to version 12.3 from 11.x versions, select the secondary destination for IBM HyperSwap configurations explicitly in the backup job.

Other Changes

Note that the last known time-based retention policy is now applied to backups belonging to disabled backup jobs and to orphaned backups. You can use the Copy Backup functionality of Veeam Backup & Replication 12.3 to create a fully independent copy of the required backups, which will not be subject to the retention policy.
Veeam Backup & Replication 12.3 supports protecting NAS backups with Backup to Tape jobs. If you have entire repositories added as sources for backup to tape jobs, make sure these repositories contain only backups that you want to protect with backup to tape jobs.

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 Enterprise Manager

To upgrade Veeam Backup Enterprise Manager to version 12.3, you must run version 11a (build 11.0.1.1261) 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 12.3 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.

Upgrading Veeam Backup & Replication Server

To upgrade the Veeam Backup & Replication server to version 12.3, you must run version 11a (build 11.0.1.1261) or later. 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.
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 12.3 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.
If you are using the Virtual Labs functionality, please open the settings of each virtual lab and click through the wizard to redeploy each virtual lab with the new proxy appliance version.
If you use Linux servers for your backup infrastructure components, the upgrade process will automatically deploy the new persistent data mover only to Linux servers with the VMware Backup Proxy role. To deploy it on other Linux servers, click through the Linux server properties or use the Set-VBRLinux PowerShell cmdlet to mass-deploy. Until you do this, those Linux servers will continue using the legacy runtime data mover to avoid issues with the backup repository not meeting the persistent data mover requirements.
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.

Licensing

Veeam Backup & Replication can be licensed per protected workload with Veeam Universal License (VUL) or per CPU Socket of the underlying hypervisor host (for vSphere or Hyper-V VMs protection only). 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. Perpetual Socket license includes a one-year maintenance plan with Basic support. To renew or upgrade your maintenance plan, contact Veeam Renewals at veeam.com/renewal.html

Updating Veeam Backup & Replication License

The Veeam Backup & Replication server license is 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 Backup & Replication, you may use the following resources:

Product web page: veeam.com/vm-backup-recovery-replication-software.html
User guides: veeam.com/documentation-guides-datasheets.html
Community 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.
Log files. To export the log files, select Help > Support Information from the main menu and follow the wizard to export the relevant 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.