System Requirements

Make sure that servers that you plan to use as backup infrastructure components meet the listed system requirements.

Note

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

Limitations and Recommendations

Coexistence with Mission-Critical Production Servers

We do not recommend you to install Veeam Backup & Replication and its components on mission-critical machines in the production environment such as vCenter Server, Domain Controller, Microsoft Exchange Server, Small Business Server/ Windows Server Essentials and so on. If possible, install Veeam Backup & Replication and its components on dedicated machines. Backup infrastructure component roles can be co-installed.

Microsoft Windows Server Core

You can assign roles of a backup proxy, backup repository, WAN accelerator, Veeam Cloud Connect infrastructure components and tape infrastructure components to machines running Microsoft Windows Server Core.
Note that you cannot install Veeam Backup & Replication and Veeam Backup Enterprise Manager on a machine running Microsoft Windows Server Core.

Windows Server IoT/Windows Storage Server Support

For information about support of Windows Server IoT/Windows Storage Server, see this Veeam KB article.

Domain Member

The machine on which you plan to install Veeam Backup & Replication does not necessarily need to be a domain member. However, if you plan to restore Microsoft Exchange items from the Veeam Backup Enterprise Manager UI, you must install Veeam Backup Enterprise Manager on the domain member server from the Microsoft Active Directory forest in which Microsoft Exchange mailboxes are located.

Encrypted Communication

Veeam backup infrastructure components support the following TLS versions:

Note

For security reasons, disable outdated protocols TLS 1.0 and 1.1 if they are not needed. For more information, see this Microsoft article.

To avoid negotiation problems between Veeam Backup & Replication and a Microsoft Windows server, ensure that both sides of communication support the same ciphers.

To avoid negotiation problems between Veeam Backup & Replication and a Linux server, the latter should use ciphers, Key Exchange (KEX) algorithms, and MAC algorithms compatible with SSH libraries supported by Veeam Backup & Replication:

Algorithms

Supported values

Ciphers

Recommended: aes128-ctr, aes192-ctr, aes256-ctr, aes128-gcm@openssh.com, aes256-gcm@openssh.com, chacha20-poly1305@openssh.com

Supported for backward compatibility: 3des-cbc, 3des-ctr, aes128-cbc, aes192-cbc, aes256-cbc, arcfour, arcfour128, arcfour256, blowfish-cbc, blowfish-ctr, cast128-cbc, twofish-cbc, twofish128-cbc, twofish128-ctr, twofish192-cbc, twofish192-ctr, twofish256-cbc, twofish256-ctr

KEX algorithms

Recommended: diffie-hellman-group-exchange-sha256, diffie-hellman-group14-sha256, diffie-hellman-group15-sha512, diffie-hellman-group16-sha512, ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, curve25519-sha256, curve25519-sha256@libssh.org

Supported for backward compatibility: diffie-hellman-group1-sha1, diffie-hellman-group14-sha1, diffie-hellman-group-exchange-sha1

MAC algorithms

Recommended: hmac-sha2-256, hmac-sha2-512

Supported for backward compatibility: hmac-md5, hmac-md5-96, hmac-sha-256-96, hmac-sha1-96, hmac-sha2-512-96, hmac-ripemd160, hmac-ripemd160@openssh.com, hmac-sha1

Ensure that your SSH configuration on the Linux server allows you to use at least one cipher, KEX algorithm, and MAC algorithm from the table above. You can run the following command to verify the list of allowed algorithms:

sudo sshd -T | grep "\(ciphers\|macs\|kexalgorithms\)"

All-in-One Installations

For all-in-one installations, you can subtract 2 GB of memory resources from each but one role. These 2 GB are allotted to the OS itself, assuming each component is installed on the dedicated server.

Unstructured Data Backup

Each of the following components for unstructured data backup may consume up to 4 GB RAM per task (in case of deduplicating storage appliances, up to 8 GB RAM): backup repository, backup proxy, cache repository. Make sure you allocate enough memory resources for your installation. For all-in-one installations, the server where all the components are installed must have enough memory resources for all components.

Sharing Backup Infrastructure Components Across Veeam Installations

Using Linux-based shared backup infrastructure components across different Veeam installations is not supported.

As for non-Linux backup infrastructure components, we do not recommend using them shared across different Veeam installations due to several reasons:

  • Veeam installations compete for resources.
  • Backup components cannot simultaneously interact with Veeam Backup & Replication of different versions.
  • Adding the same repository to different Veeam Backup & Replication installations may lead to corrupted backup and data in the database.

Backup Server

Specification

Requirement

Hardware

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

Memory: 4 GB RAM plus 500 MB RAM for each concurrent job. Memory consumption varies according to the number of VMs in the job, size of VM metadata, size of production infrastructure, and so on.

Additionally, for users with tape installations (for file to tape jobs processing more than 1,000,000 files):

  • 1.5 GB RAM for file to tape backup for each 1,000,000 files
  • 2.6 GB RAM for file restore for each 1,000,000 files
  • 1.3 GB RAM for catalog jobs for each 1,000,000 files

Disk Space: 5 GB1 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 Recovery cache folder (non-persistent data, at least 100 GB recommended). At least 10 GB for storing logs, although the disk space required for logging depends on the set of features used and may significantly increase. For details on logs locations, see Logging.

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

1 Here and throughout this document GB is considered as 2^30 bytes, TB as 2^40 bytes.

OS

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

  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2012 R22, 3
  • Microsoft Windows Server 20122, 3
  • Microsoft Windows 11 (versions 21H2, 22H2, 23H24)
  • Microsoft Windows 10 (from version 1909 to version 22H2)
  • Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

1 Running Veeam backup server or any of Veeam backup infrastructure components on Insider versions of Microsoft Windows OS (both Client and Server) is not supported.

2 VMware Cloud Director servers cannot be added or used in this version of Microsoft Windows OS.

3 There may be issues when using Veeam Backup for Nutanix AHV with backup server running on this version of Microsoft Windows OS. For more information, see this Veeam KB article.

4 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

Configuration Database

Local or remote installation of the following versions of PostgreSQL1:

  • PostgreSQL 14.x
  • PostgreSQL 15.x (PostgreSQL 15.5 is included in the Veeam Backup & Replication 12.1 setup)

Local or remote installation of the following versions of 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

All editions of Microsoft SQL Server are supported. The usage of Microsoft SQL Server Express Edition is limited by the database size up to 10 GB. If you plan to have larger databases, use other editions of Microsoft SQL Server.

If you plan to use a database engine other than PostgreSQL 15.1, included in the Veeam Backup & Replication setup, you must install it yourself. If you want to use an already installed PostgreSQL instance for the configuration database, make sure the instance contains the default postgres database. If you allow the setup to install a new PostgreSQL instance, the postgres database will be created on the instance automatically. Since Veeam Backup & Replication connects to the postgres database to access the configuration database, do not rename the postgres database upon the installation.

Veeam Backup & Replication does not support Microsoft SQL Server database with case-sensitive collations.

Veeam Backup & Replication and Veeam Backup Enterprise Manager configuration databases can be deployed in Microsoft SQL Always On Availability Groups. For more information, see this Veeam KB article.

1 Veeam Backup & Replication does not support PostgreSQL installations on cloud database services (for example, Amazon Relational Database Service (RDS).

Software

During setup, the system configuration check is performed to determine if all prerequisite software is available on the machine where you plan to install Veeam Backup & Replication. If some of the required software components are missing, the setup wizard will offer you to install missing software automatically. This refers to:

  • Microsoft .NET Framework 4.7.2
  • Microsoft ASP.NET Core Shared Framework 6.0.25 — for Veeam Backup & Replication 12.1.1 (build 12.1.1.56), 6.0.24 — for version 12.1 (build 12.1.0.2131) (the latest patch release is recommended)
  • Microsoft Edge WebView2 Runtime 119.0.2151.72 (not installed for Microsoft Windows Server 2012 and 2012 R2 due to the version incompatibility)
  • Microsoft PowerShell 5.1
  • Microsoft Report Viewer Redistributable 2015
  • Microsoft SQL Server System CLR Types (both for SQL Server and PostgreSQL installations)
  • Microsoft Universal C Runtime
  • Microsoft Visual C++ 2015-2019 Redistributable 14.29.30037
  • Microsoft Windows Desktop Runtime 6.0.25 — for Veeam Backup & Replication 12.1.1 (build 12.1.1.56), 6.0.24 — for version 12.1 (build 12.1.0.2131) (the latest patch release is recommended)

 

The backup server installation also requires the automatic installation of the prerequisite software for Veeam Cloud Plug-Ins.

The following software must be installed manually:

  • Firefox, Google Chrome, or Microsoft Edge (optional, to use Veeam Backup Enterprise Manager web UI).
  • Windows Installer 4.5

If you plan to install Veeam Backup & Replication in the unattended mode using the command line interface, manually install all prerequisite software before that. For more information, see Installing Veeam Backup & Replication in Unattended Mode.

Consider the following:

For more information, see the Backup Server section.

Veeam Backup & Replication Console

 

Specification

Requirement

Hardware

CPU: x86-64 processor.

Memory: 2 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 impact user interface responsiveness.

OS

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

  • 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, 23H21)
  • Microsoft Windows 10 (from version 1909 to version 22H2)
  • Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

Software

During setup, the system configuration check is performed to determine if all prerequisite software is available on the machine where you plan to install the Veeam Backup & Replication Console. If some of the required software components are missing, the setup wizard will offer you to install missing software automatically. This refers to:

  • Microsoft .NET Framework 4.7.2
  • Microsoft Edge WebView2 Runtime 119.0.2151.72 (not installed for Microsoft Windows Server 2012 and 2012 R2 due to the version incompatibility)
  • Microsoft PowerShell 5.1
  • Microsoft Report Viewer Redistributable 2015
  • Microsoft SQL Server System CLR Types (both for SQL Server and PostgreSQL installations)
  • Microsoft Universal C Runtime
  • Microsoft Windows Desktop Runtime 6.0.24

The following software must be installed manually:

  • Firefox, Google Chrome, or Microsoft Edge (optional, to use Veeam Backup Enterprise Manager web UI)
  • Windows Installer 4.5

For more information, see the Backup & Replication Console section.

VMware Backup Proxy

Specification

Requirement

Hardware

CPU: x86-64 processor with 2 cores (vCPUs) minimum, plus 1 core (vCPU) for each 2 additional concurrent tasks. Using faster processors improves data processing performance. For more information, see Limitation of Concurrent Tasks.

Memory: 2 GB RAM plus 500 MB 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 (DDR3/DDR4) 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, and 1 Mbps or faster for off-site backup and replication. High latency and reasonably unstable WAN links are supported.

OS

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

  • 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, 23H21)
  • Microsoft Windows 10 (from version 1909 to version 22H2)
  • Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

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.11, 12.21
  • Oracle Linux 7 (UEK3) to 9 (UEK R7)
  • Oracle Linux 7 to 9 (RHCK)
  • RHEL 7.0 to 9.31
  • SLES 12 SP4 or later, 15 SP1 or later
  • Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

For more information, see the VMware Backup Proxies section.

General-Purpose Backup Proxy

The following table shows the minimum system requirements for a general-purpose backup proxy used for agent-based backup of object storage repositories, NAS, filers, file shares and off-host backup of physical servers.

Specification

Requirement

Hardware

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

Memory: 4 GB RAM for each concurrent task. Using faster memory (DDR3/DDR4) improves data processing performance.

Disk Space: 300 MB.

Network: High latency and reasonably unstable WAN links are supported.

OS

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

  • 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, 23H21)
  • Microsoft Windows 10 (from version 1909 to version 22H2)
  • Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

Backup proxies running Microsoft Windows Server 2012 R2 or later support the VSS for SMB File Shares feature. To use it, make sure that all requirements listed in this Veeam KB article are met.

For object storage backup, also 64-bit versions of the following Linux distributions are supported:

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

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

For more information, see the General-Purpose Backup Proxies section.

VMware CDP Proxy

The following table shows the minimum system requirements for a VMware CDP proxy.

Specification

Requirement

Hardware

CPU : x86-64 processor with 4 cores (8 cores before Veeam Backup & Replication 12.1 (build 12.1.0.2131)) minimum. Using multi-core processors improves data processing performance and allows for more tasks to be processed concurrently. Enabling the encryption may cause the performance reduction: in this case, increase the vCPU count up to 2 times.

Memory: 8 GB RAM minimum (16 GB RAM before Veeam Backup & Replication 12.1 (build 12.1.0.2131)). 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). Larger cache allows for longer network downtime periods before a CDP policy switches to the CBT mode.

Network: 100 Mbps or faster.

OS

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

  • 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, 23H21)
  • Microsoft Windows 10 (from version 1909 to version 22H2)
  • Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

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.11, 12.21
  • Oracle Linux 7 (UEK3) to 8.3 (UEK R6 U2)
  • Oracle Linux 7 to 8.5 (RHCK)
  • RHEL 7.0 to 9.31
  • SLES 12 SP4 or later, 15 SP1 or later
  • Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

For more information, see the VMware CDP Proxies section.

Backup Repository

These requirements also apply to separate mount servers (they can be only Windows-based), gateway servers for unstructured data backup, deduplicating appliance-based repositories and cache repository servers.

Specification

Requirement

Hardware

CPU: x86-64 processor. The number of cores depends on the concurrent task settings. For more information, see Limitation of Concurrent Tasks.

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). For more information, see Limitation of Concurrent Tasks. For RAM allocation recommendations for unstructured data backup, see Limitations and recommendations for unstructured data backup.

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

OS

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

  • 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, 23H21)
  • Microsoft Windows 10 (from version 1909 to version 22H2)
  • Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

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

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

Bash shell and SSH are required to deploy the management agent (SSH connection is not required for updating Veeam components and can be disabled afterwards). Perl is required only for non-persistent Veeam Data Movers. Check the full list of required Perl modules in this Veeam KB article.

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

  • Debian 10.0 to 12.11, 12.21
  • RHEL 8.2 to 9.31
  • SLES 15 SP2, SP3, SP4, SP51
  • Ubuntu 18.04 LTS, 20.04 LTS, 22.04 LTS

For other distributions, XFS integration support is experimental, with kernel version 5.4 or later recommended. For more information, see this Veeam KB article.

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

For more information, see the Backup Repositories section.

Note

Consider the following:

  • If you plan to use a Microsoft Windows backup repository with Data Deduplication, make sure that you set up the Microsoft Windows server correctly. For more information, see this Veeam KB article.
  • In rare cases, Veeam backups may become corrupted when stored on the exFAT file system. We strongly discourage using the exFAT filesystem for backup storage when attached to Windows 10 or Windows Server 2019 and later. For more information, see this Veeam KB article.

Cache Repository

The following storage types can be used as a cache repository for unstructured data backup:

For system requirements of backup repositories that can be used as a cache repository, see Backup Repository.

For more information, see Cache Repository in the Backup Infrastructure for Unstructured Data Backup section.

Cache Repository for Object Storage Repository

If the cache repository works with an unstructured data source being backed up to an object storage repository, it also processes active metadata that is heavily used during backup and restore operations. So you will require more disk space for the cache repository. The volume of this disk space depends on the number of the file versions on the data source and the number of unstructured data backup jobs that protect this data source. We recommend allocating not less than 1 GB of disk space for active metadata of each 1,000,000 file versions protected with 1 file backup job or object storage backup job. If you protect the same data source, for example, with 2 different backup jobs, the volume of metadata will double. For more information, see the Unstructured Data Backups in Object Storage Repositories section.

Tip

We strongly recommend utilizing a fast storage disk, for example, an SSD in the role of the cache repository used for working with an object storage repository.

Tape Server

Specification

Requirement

Hardware

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

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 10 GB for temporary data storage for backup and restore operations.

Network: 1 Gbps or faster.

For system requirements for large number of files in the file backup to tape job, see the Before You Begin section for file backup to tape.

OS

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

  • 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, 23H21)
  • Microsoft Windows 10 (from version 1909 to version 22H2)
  • Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

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

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

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

2 Note that the tape server requires root access rights. For this reason, hardened repository cannot be used as the tape server.

For more information, see the Tape Servers section.

WAN Accelerator

Specification

Requirement

Hardware

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

Memory: 8 GB RAM. Using faster memory (DDR3/DDR4) 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 user (fixed amount). Disk space is reserved immediately upon selecting the WAN Accelerator as a target one in any job. For more information, see WAN Accelerator Sizing.

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

OS

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

  • 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, 23H21)
  • Microsoft Windows 10 (from version 1909 to version 22H2)
  • Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

For more information, see the WAN Accelerators section.

Note

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

Backup Target

Backed up data can be stored in the following disk-based systems:

The DAS must be connected to the backup repository, including external USB/eSATA drives, USB pass through and raw device mapping (RDM) volumes.

The backup repository must be connected into the SAN fabric through hardware or virtual HBA, or software iSCSI initiator.

The NAS must be able to present its capacity as NFS share (protocol versions 3.0 and 4.1 only) or SMB (CIFS) share (any protocol versions). Using consumer-grade NAS storage without an enterprise-grade RAID controller with battery-backed write cache (BBWC) is not recommended for reliability considerations.

Both Ethernet and Fibre Channel (FC) connectivity is supported.

Both Ethernet and Fibre Channel (FC) connectivity are supported. Note that HPE StoreOnce Federated Catalyst is not supported.

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.

1 Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131).

2 These storage systems use the Veeam Transport Service. Make sure that they also meet system requirements for the backup repository.

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:

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

For the full list of partner-tested solutions including primary backup storage solutions, S3-compatible object storage solutions and offline storage solutions, see this Veeam page.

For information on unstructured data backup target, see Storage Repositories in the Backup Infrastructure for Unstructured Data Backup section.

Veeam CDP Source and Target Datastores

The following source and target datastores are supported for Veeam CDP:

VSAN is supported for all hyper-converged infrastructure (HCI) appliances.

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 HCI appliances is pending validation by Veeam. The documentation will be updated based on the testing results. For the updates, see CDP Requirements and Limitations.

Note

Consider the following:

  • 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.
  • VVOL and VSAN of each vendor have limits for the number of storage objects. Once the limit is reached, CDP starts to fail because creation of new objects cannot be completed. To restore the CDP process, remove some objects from VSAN/VVOL.
  • CDP performance depends on your datastore characteristics. For better performance, check that your target datastore is able to process the I/O workload produced on the source datastore.

Tape

Specification

Requirement

Hardware

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

  • LTO3-LTO9
  • IBM 3592 (TS1160 and TS1170)1

Tape device must be directly attached to the backup server, to a tape server through SAS, FC or iSCSI interface. Note that VMware does not support connecting tape libraries to ESXi for VM pass-through.

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

Software

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

For more information, see the Tapes section.

Storage Systems

Veeam Backup & Replication provides different types of snapshot integrations and these integrations support different storage systems:

NAS Integration

NAS integration is possible with the following built-in storage systems.

Dell PowerScale (formerly Isilon)

Fujitsu ETERNUS HX/AX

Version 9.13.1 or 9.14.1 combined with Veeam Backup & Replication 12 (build 12.0.0.1420) have some issues. For more details, see this Veeam KB article.

  • MetroCluster is supported
  • ONTAP features application-aware data management and SVM-DR are not supported
  • Synchronous SnapMirror is not supported

Lenovo DM Series

Version 9.13.1 or 9.14.1 combined with Veeam Backup & Replication 12 (build 12.0.0.1420) have some issues. For more details, see this Veeam KB article.

  • MetroCluster is supported
  • ONTAP features application-aware data management and SVM-DR are not supported
  • Synchronous SnapMirror is not supported

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

Version 9.13.1 or 9.14.1 combined with Veeam Backup & Replication 12 (build 12.0.0.1420) have some issues. For more details, see this Veeam KB article.

  • MetroCluster is supported
  • ONTAP features application-aware data management and SVM-DR are not supported
  • NetApp Synchronous SnapMirror is not supported

Nutanix Files

VMware and Veeam Agent Integrations with Built-in Storage Systems

VMware and Veeam Agent integrations are possible with the following built-in storage systems.

Cisco HyperFlex HX-Series

Dell VNX, VNX2, VNXe and Unity XT/Unity

Fujitsu ETERNUS HX/AX

Version 9.13.1 or 9.14.1 combined with Veeam Backup & Replication 12 (build 12.0.0.1420) have some issues. For more details, see this Veeam KB article.

  • MetroCluster is supported
  • ONTAP features application-aware data management and SVM-DR are not supported
  • Synchronous SnapMirror is not supported

HPE 3PAR StoreServ

HPE Primera

HPE Alletra 9000

HPE Alletra MP

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

HPE Alletra 5000/6000

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

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

IBM N Series

Version 9.13.1 or 9.14.1 combined with Veeam Backup & Replication 12 (build 12.0.0.1420) have some issues. For more details, see this Veeam KB article.

  • MetroCluster is supported
  • ONTAP features application-aware data management and SVM-DR are not supported
  • Synchronous SnapMirror is not supported

Lenovo DM Series

Version 9.13.1 or 9.14.1 combined with Veeam Backup & Replication 12 (build 12.0.0.1420) have some issues. For more details, see this Veeam KB article.

  • MetroCluster is supported
  • ONTAP features application-aware data management and SVM-DR are not supported
  • Synchronous SnapMirror is not supported

Lenovo Storage V Series

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

Version 9.13.1 or 9.14.1 combined with Veeam Backup & Replication 12 (build 12.0.0.1420) have some issues. For more details, see this Veeam KB article.

  • MetroCluster is supported
  • ONTAP features application-aware data management and SVM-DR are not supported
  • NetApp Synchronous SnapMirror is not supported

VMware and Veeam Agent Integrations with Universal Storage API Integrated Systems

To start working with Universal Storage API integrated systems, you must install storage system plug-ins. VMware and Veeam Agent integrations are possible with the following storage systems.

DataCore SANsymphony

Dell PowerMax

Dell PowerStore

Dell SC Series (formerly Compellent)

Fujitsu ETERNUS AF and DX Series

Hitachi VSP

HPE XP

INFINIDAT Infinibox F-Series

Note

You must add to the backup infrastructure only one of the two InfiniBox storage arrays for which Active/Active Replication is configured, or exclude the replicating volumes on one of these arrays from rescan. For details on how to exclude volumes from rescan, see Rescanning Storage Systems.

NEC Storage M Series

NEC Storage V Series

NetApp SolidFire/HCI

Pure Storage FlashArray

Tintri IntelliFlash (formerly Western Digital IntelliFlash, Tegile)

Gateway Server

Specification

Requirement

Hardware

CPU: x86-64 processor, 2 or more cores.

Memory: 4 GB RAM, plus up to 4 GB RAM for each concurrently processed machine, file share or object storage. For more information, see Limitation of Concurrent Tasks. For RAM allocation recommendations for unstructured data backup, see Limitations and recommendations for unstructured data backup.

Disk space: 2 GB per TB of data processed during a SOBR offload job for a machine that acts as a gateway server for an Object Storage Repository. For more information, see this Veeam KB article.

Note: If a unstructured data backup stored in an object storage does not have metadata in the cache repository, during the restore or health check operation this metadata will be downloaded to the gateway server. That can consume up to 80% of the gateway server disk space.

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

OS

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

  • 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, 23H21)
  • Microsoft Windows 10 (from version 1909 to version 22H2)
  • Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

For the communication with object storage repositories, external repositories and NFS backup repositories, you can use machines running 64-bit versions of the following Linux distributions:

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

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

For more information, see the Gateway Server section.

Mount Server

Specification

Requirement

Hardware

CPU: x86-64 processor with 2 cores (vCPUs) minimum, plus 1 core (vCPU) for each 2 additional concurrent tasks. Using faster processors improves data processing performance.

Memory: 4 GB RAM, plus not less than 1 GB RAM for each concurrently processed machine disk.

The following jobs consume not less than 400 MB RAM per guest VM on mount server:

  • Windows file level restore

The following jobs consume 1 GB RAM per guest VM disk on mount server + 100 MB RAM per VM:

  • SureBackup
  • Instant Recovery
  • Instant Disk Recovery

Disk Space: 1.4 GB for product installation and 4.5 GB for Microsoft .NET Framework 4.7.2 installation. If Microsoft .NET Framework 4.7.2 is not installed on the machine, Veeam Backup & Replication will install it automatically.

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

OS

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

  • 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, 23H21)
  • Microsoft Windows 10 (from version 1909 to version 22H2)
  • Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

Note: If you plan to restore VM guest OS files from VMs running Microsoft Windows ReFS or from VMs with data deduplication enabled for some volumes, you must assign the mount server role to machines running specific OS versions. For more information, see ReFS and Data Deduplication subsections in Restoring VM Guest OS Files (FAT, NTFS or ReFS).

For more information, see the Mount Server section.

Helper Host

OS

Version/Distribution

Linux

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.11, 12.21
  • Oracle Linux 7 (UEK3) to 9 (UEK R7)
  • Oracle Linux 7 to 9 (RHCK)
  • RHEL 7.0 to 9.31
  • SLES 12 SP4 or later, 15 SP1 or later
  • Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS

1 This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

For more information, see Restore from Linux, Unix and Other File Systems.

Veeam Backup Enterprise Manager Server

The machine where you plan to install Veeam Backup Enterprise Manager must meet the requirements listed in the System Requirements section of the Enterprise Manager User Guide.

Veeam Plug-Ins

The machine where you plan to install Veeam plug-ins must meet the following requirements:

Veeam Plug-In

Requirement

AWS Plug-in for Veeam Backup & Replication version 12.0.5.xxx and later

Microsoft .NET Core Runtime 6.0 or later

Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for AWS User Guide.

Microsoft Azure Plug-in for Veeam Backup & Replication version 12.0.4.xxx and later

Microsoft .NET Core Runtime 6.0 or later

Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for Microsoft Azure User Guide.

Google Cloud Plug-in for Veeam Backup & Replication version 12.0.3.xxx and later

Microsoft .NET Core Runtime 6.0 or later

Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for Google Cloud User Guide.

Nutanix AHV Plug-in for Veeam Backup & Replication version 12.0.4.xxx and later

Microsoft .NET Core Runtime 6.0 or later

Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for Nutanix AHV User Guide.

RHV Plug-in for Veeam Backup & Replication version 12.0.3.xxx and later

Microsoft .NET Core Runtime 6.0 or later

Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for RHV User Guide.

Kasten K10 Plug-in for Veeam Backup & Replication version 12.0.0.xxx and later

Microsoft .NET Core Runtime 6.0 or later

Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for Kasten K10 User Guide.

Supported Applications

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

Application

Requirement

Microsoft Active Directory

Veeam Backup & Replication supports backup of domain controllers for the following operating systems:

  • Microsoft Windows Server 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

Minimum supported domain and forest functional level is Windows 2008.

Microsoft Exchange

Veeam Backup & Replication supports backup of the following Microsoft Exchange versions:

  • Microsoft Exchange 2019
  • Microsoft Exchange 2016
  • Microsoft Exchange 2013

Microsoft SharePoint

Veeam Backup & Replication supports backup of the following versions of Microsoft SharePoint Server (virtualized either on VMware or Hyper-V platform):

  • Microsoft SharePoint Server Subscription Edition
  • Microsoft SharePoint 2019
  • Microsoft SharePoint 2016
  • Microsoft SharePoint 2013

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

Restore of Microsoft SharePoint data may require an available staging Microsoft SQL Server. To learn how to configure this server, see the Configuring Staging SQL Server section of the Veeam Explorers User Guide.

Microsoft SQL Server

Veeam Backup & Replication supports backup of the following Microsoft SQL Server versions:

  • Microsoft SQL Server 2022 (only for Windows)
  • Microsoft SQL Server 2019 (only for Windows)
  • Microsoft SQL Server 2017 (only for Windows)
  • Microsoft SQL Server 2016 SP2
  • Microsoft SQL Server 2014 SP3
  • Microsoft SQL Server 2012 SP4
  • Microsoft SQL Server 2008 R2 SP3
  • Microsoft SQL Server 2008 SP4

All editions of Microsoft SQL Server except LocalDB are supported.

The database whose logs you want to back up must use the Full or Bulk-logged recovery model. In this case, all changes of the Microsoft SQL Server state will be written to transaction logs, and you will be able to replay transaction logs to restore the Microsoft SQL Server. You can use the Microsoft SQL Server Management Studio to switch to one of these models. For more information, see Microsoft Docs.

Restore of Microsoft SQL Server data may require an available staging Microsoft SQL Server. To learn how to configure this server, see the Configuring Staging SQL Server section of the Veeam Explorers User Guide.

Oracle on Windows OS

Veeam Backup & Replication supports backup of the following Oracle Database versions on Microsoft Windows machines:

  • Oracle Database 21c

For supported operating systems, see Oracle documentation.

  • Oracle Database 19c

For supported operating systems, see Oracle documentation.

  • Oracle Database 18c

For supported operating systems, see Oracle documentation.

  • Oracle Database 12c Release 2

For supported operating systems, see Oracle documentation.

  • Oracle Database 12c Release 1

For supported operating systems, see Oracle documentation.

  • Oracle Database 11g Release 2

For supported operating systems, see Oracle documentation.

Oracle on Linux OS

Veeam Backup & Replication supports backup of the following Oracle Database versions on Linux machines:

  • Oracle Database 21c

For supported operating systems, see Oracle documentation.

  • Oracle Database 19c

For supported operating systems, see Oracle documentation.

  • Oracle Database 18c

For supported operating systems, see Oracle documentation.

  • Oracle Database 12c Release 2

For supported operating systems, see Oracle documentation.

  • Oracle Database 12c Release 1

For supported operating systems, see Oracle documentation.

  • Oracle Database 11g Release 2

For supported operating systems, see Oracle documentation.

Starting from version 12.1 (build 12.1.0.2131), Veeam Backup & Replication supports the backup of Linux-based VMs with several Oracle homes of different versions.

Oracle Database configuration

Consider the following:

  • Automatic Storage Management (ASM) is supported for Oracle 11g and later; requires ASMlib present.
  • Oracle Real Application Clusters (RAC) are not supported within the image-level backup functionality. Use Veeam Plug-in for Oracle RMAN. For details, see the Veeam Plug-in for Oracle RMAN section of the Veeam Plug-ins for Enterprise Applications User Guide.
  • Oracle Database Express Edition (XE) is supported for Windows-based machines only.
  • Configurations with different versions of Oracle Database deployed on the same server are not supported. Use Veeam Plug-in for Oracle RMAN. For details, see the Veeam Plug-in for Oracle RMAN section of the Veeam Plug-ins for Enterprise Applications User Guide.
  • To create Oracle database backups, all Oracle servers that use Data Guard must be added to the backup job.
  • You can use Veeam Plug-in for Oracle RMAN to integrate RMAN with Veeam Backup & Replication repositories. For details, see the Veeam Plug-in for Oracle RMAN section of the Veeam Plug-ins for Enterprise Applications User Guide.

PostgreSQL

Veeam Backup & Replication supports backup of the following PostgreSQL versions on Linux machines:

  • PostgreSQL 16
  • PostgreSQL 15
  • PostgreSQL 14
  • PostgreSQL 13
  • PostgreSQL 12

 

Note

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

Veeam Explorers

Page updated 2/20/2024

Page content applies to build 12.1.1.56