This is an archive version of the document. To get the most up-to-date information, see the current version.

System Requirements

Make sure that components in the Veeam Agent management infrastructure meet system requirements listed below.

Veeam Backup Server

To learn about system requirements for the Veeam backup server and other Veeam Backup & Replication components, see the System Requirements section in the Veeam Backup & Replication User Guide.

Veeam Agent Computer (Microsoft Windows)

A computer that you want to protect with Veeam Agent for Microsoft Windows must meet the following requirements:

Specification

Requirement

Hardware

CPU: x86-64 processor.

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

Disk Space: 200 MB for product installation.

Network: 1 Mbps or faster1.

System firmware: BIOS or UEFI.

Drive encryption: Microsoft BitLocker (optional)2.

1 High latency and reasonably unstable WAN links are supported.

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

OS

Both 64-bit and 32-bit (where applicable) versions of the following operating systems are supported1:

  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
  • Microsoft Windows Server Semi-Annual Channel (from version 1803 to version 20H2)
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2008 R2 SP12
  • Microsoft Windows 11 (version 21H2)
  • Microsoft Windows 10 Semi-Annual Channel (from version 1803 to version 21H2)3
  • Microsoft Windows 10 Long-Term Servicing Channel (versions 1507, 1607 and 1809)
  • Microsoft Windows 8.1      
  • Microsoft Windows 7 SP1

Each Veeam Agent computer that consumes a license installed in Veeam Backup & Replication must have a unique BIOS UUID.

1 Consider the following:

  • Starting from Veeam Backup & Replication 11a (build 11.0.1.1261), support of the following OS versions is added: Microsoft Windows Server 2022, Microsoft Windows 10 version 21H1. For Veeam Backup & Replication 11a (build 11.0.1.1261) with Cumulative Patch P20211211) installed, support of Windows 10 version 21H2 and Windows 11 version 21H2 is added.
  • Small Business Server, Server Essentials, and Server Storage editions of Microsoft Windows Server OSes are supported.
  • Server Core installations of Microsoft Windows Server OSes can be backed-up only by Veeam Agent backup jobs managed by the Veeam backup server.
  • Running Veeam Agent on Insider versions of Microsoft Windows Client and Server OSes is not supported. 

2 Veeam CBT driver is supported only if Microsoft Windows update KB3033929 is installed on the Veeam Agent computer.

3 Microsoft Windows 10 Education is supported starting from build 10586 and later.

File System

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

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

Microsoft SQL Database

Microsoft SQL Server 2012 SP4 Express LocalDB Edition.  

Microsoft SQL Server is installed within the Veeam Agent deployment process only if you added the target computer to the backup policy. To learn more, see Backup Policy.

Software

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

  • Microsoft .NET Framework 4.5.2
  • Microsoft SQL Server 2012 Management Objects1
  • Microsoft SQL Server System CLR Types1
  • Windows Universal C Runtime Library

1 The component is installed only together with Microsoft SQL Server.

Veeam Agent for Microsoft Windows works with only those hard drive types that are supported by the Microsoft Windows OS. Thus, Veeam Agent supports the 512 bytes and 4 KB sector hard drives only. Other hard drive types are not supported. To learn more, see this Microsoft article.

 

Veeam Agent Computer (Linux)

A computer that you want to protect with Veeam Agent for Linux must meet the following requirements:

 

Specification

Requirement

Hardware

CPU: x86 (starting from i386) or x64 processor.

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

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

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

System firmware: BIOS or UEFI.

Disk layout: MBR or GPT.

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

OS

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

Linux kernel version 2.6.32 or later is supported.

Both 64-bit and 32-bit versions (if applicable) of the following distributions are supported1:

  • Debian 9.0 – 11.1
  • Ubuntu 14.04, 16.04, 18.04, 20.04, 20.10, 21.04, 21.10
  • Ubuntu 22.04 (requires editing Veeam Agent configuration file on the Veeam backup server. For details, see this Veeam KB article)
  • RHEL 6.0 – 8.5
  • RHEL 8.6, 9.0 (requires updating Veeam Agent to version 5.0.2.4619. For details, see this Veeam KB article)
  • CentOS 7.0 – 8.5
  • Oracle Linux 6 – 8.5 (RHCK)
  • Oracle Linux 6 (starting from UEK R2) – Oracle Linux 8 (up to UEK R6 U2, kernel version 5.4.17-2102)
  • Oracle Linux 8.6, 9.0 (RHCK) (requires updating Veeam Agent to version 5.0.2.4619. For details, see this Veeam KB article)
  • SLES 11 SP4, 12 SP2 – 15 SP3
  • SLES for SAP 11 SP4, 12 SP2 – 15 SP3
  • SLES 15 SP4 (requires updating Veeam Agent to version 5.0.2.4619. For details, see this Veeam KB article)
  • Fedora 33, 34, 35
  • openSUSE Leap 15.2 – 15.3
  • openSUSE Leap 15.4 (requires updating Veeam Agent to version 5.0.2.4619. For details, see this Veeam KB article)
  • openSUSE Tumbleweed

1 Starting from Veeam Backup & Replication 11a (build 11.0.1.1261), support of the following OS versions is added: Debian 11, Ubuntu 21.04, RHEL 8.4, CentOS 8.4, Oracle Linux 8.4 (RHCK), Oracle Linux UEK R6 U1, UEK R6 U2 (up to kernel version 5.4.17-2102), SLES 15 SP3, SLES for SAP 15 SP3, Fedora 33, 34, openSUSE Leap 15.3. For Veeam Backup & Replication 11 (build 11.0.1.1261) with Cumulative Patch P20211211) installed, support of the following OS versions is added: Ubuntu 21.10, RHEL 8.5, CentOS 8.5, Oracle Linux 8.5 (RHCK), Fedora 35.

 

File System

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

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

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

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

Data that resides on other file systems and volumes (including NFS and SMB shares) can be backed up using the snapshot-less mode. For details, see the Snapshot-Less File-Level Backup section in the Veeam Agent for Linux User Guide.

Software

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

Protected computer must have the following components installed:

  • dkms
  • gcc
  • make
  • perl
  • linux-headers (for Debian-based systems)
  • kernel-headers (for RedHat-based systems)
  • kernel-devel (for RedHat-based systems)
  • libudev
  • libacl
  • libattr
  • lvm2
  • libfuse
  • libncurses5
  • dmidecode
  • libmysqlclient
  • libpq5
  • python3
  • efibootmgr (for UEFI-based systems)
  • isolinux (for Debian-based systems)
  • syslinux (for RedHat-based systems)
  • btrfs-progs (for backup of Btrfs file system)
  • mksquashfs (for custom Veeam Recovery Media)
  • unsquashfs (for custom Veeam Recovery Media)
  • wget (for custom Veeam Recovery Media)
  • xorriso (for custom Veeam Recovery Media with EFI support)
  • mlocate (for file system indexing)
  • tar (for file system indexing, log export and rotation)
  • gzip (for file system indexing, log export and rotation)

Considerations and Limitations (Linux)

OS

If a new version of a supported Linux distribution is released after the release of the current version of Veeam Agent, Veeam Agent may require a patch to support this new OS version. For details on Veeam Agent compatibility with Linux OS versions, see this Veeam KB article. Customers with a valid contract can request a patch from Veeam Support; for other customers, the support of the new Linux distribution will be provided with the next release of Veeam Agent.

  • To ensure proper functioning of the veeamsnap kernel module, verify that the Veeam Agent computer does not have any of the following modules installed: hcdriver, snapapi26, snapapi, snapper, dattobd, dattobd-dkms, dkms-dattobd, cdr or cxbf.
  • The Linux OS must be set up to receive software updates from the default repositories enabled in the OS after installation.
  • For cloud-based installations that use customized kernels (such as Linux distributions deployed from AWS Marketplace or Azure Marketplace), the veeamsnap kernel module has experimental support status. For details about experimental support, see this Veeam KB article.
  • Automatic Veeam Agent deployment from the Veeam backup console is not supported for the following distributions:
  • Fedora 33, 34, 35
  • openSUSE Tumbleweed

You need to install Veeam Agent for Linux directly on a target computer. For details, see the Installing Veeam Agent for Linux section in the Veeam Agent for Linux User Guide.

  • RHEL, CentOS, and Oracle Linux (RHCK) are supported up to certain kernel versions. For details, see this Veeam KB article.
  • Ubuntu 21.10 minimal install is not supported.

 

File System

Keep in mind that characters that you can use in the file name may be encoded in 2 bytes or more.

For the kernel version 4.13 or later, if a value of extended attribute exceeds the limit, Veeam Agent uses the ea_inodes feature. Backups created using the ea_inodes feature cannot be mounted on kernel versions up to 4.12.

  • BFQ I/O scheduler is not supported.
  • Sparse files are not supported. Veeam Agent backs up and restores sparse files as regular files.

Software

System Requirements IMPORTANT

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

For details, see the Installing Veeam Agent for Linux section in the Veeam Agent for Linux User Guide.

  • Version of the following packages varies according to the Linux kernel version that you use:
  • linux-headers (for Debian-based systems)
  • kernel-headers (for RedHat-based systems)
  • kernel-devel (for RedHat-based systems)
  • For openSUSE and SLES distributions, either of the following packages is required: libncurses5 or libncurses6.
  • The dmidecode package is required for Veeam Agent management — a valid BIOS UUID must be obtainable either from dmidecode | grep -i uuid or from /sys/class/dmi/id/product_uuid. Each Veeam Agent that consumes a license installed in Veeam Backup & Replication must have a unique BIOS UUID. If a valid UUID cannot be obtained, Veeam will generate it automatically.
  • The libmysqlclient package is required to process MySQL database system located on the Veeam Agent server. Package version varies according to the MySQL database system version that you use.
  • The libpq5 package is required to process PostgreSQL database system located on the Veeam Agent server.
  • The python3 package or another RPM package providing a /usr/bin/python3 binary is required for CentOS, RHEL 7.0 and later distributions if a pre-built binary kmod-veeamsnap package is to be installed.
  • The btrfs-progs package version 3.16 or later is required.
  • The lvm2 package version up to 2.03.12 is required. Later versions are not supported.

Veeam Agent Computer (IBM AIX)

A computer that you want to protect with Veeam Agent for IBM AIX must meet the following requirements:

Specification

Requirement

Hardware

Memory: 1 GB RAM. For information about RAM requirements for backup of a great number of files, see the RAM Requirements for Large-Scale Environments section in the Veeam Agent for IBM AIX User Guide.

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

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

OS

All versions of the IBM AIX operating system starting from IBM AIX 6.1 are supported.

Note:

  • IBM AIX 6.1 is supported starting from Technology Level 5 (TL 5).
  • Backup of a Virtual I/O Server (VIOS) is not supported.
  • Only GA versions of the IBM AIX OS that have been released before Veeam Agent for IBM AIX 3.0 are supported.

File System

All file systems supported by the supported operating systems.

Note:

  • Total size of all file systems included in a file-level backup must not exceed 218 TB. This limitation also applies to all file systems where files you plan to back up are located.
  • Sparse files are not supported. Veeam Agent backs up and restores sparse files as regular files.
  • JFS external snapshots are not supported.

Software

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

  • The tar utility is installed together with the product.
  • The mlocate utility is provided along with the product in the product installation media.
  • The gzip utility must be installed separately.

AIX Environment

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

Veeam Agent Computer (Oracle Solaris)

A computer that you want to protect with Veeam Agent for Oracle Solaris must meet the following requirements:

Specification

Requirement

Hardware

CPU: Oracle SPARC or Intel x86 processor.

Memory: 1 GB RAM. For information about RAM requirements for backup of a great number of files, see the RAM Requirements for Large-Scale Environments section in the Veeam Agent for Oracle Solaris User Guide.

Disk space: 150 MB free disk space for product installation.

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

OS

Oracle Solaris 10 – 11.4 operating systems on machines based on the SPARC and Intel x86 architecture are supported.

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

File System

All file systems supported by the supported operating systems.

Note:

  • Total size of all file systems included in a file-level backup must not exceed 218 TB. This limitation also applies to all file systems where files you plan to back up are located.
  • Sparse files are not supported. Veeam Agent backs up and restores sparse files as regular files.

Software

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

  • The tar utility is installed together with the product.
  • The mlocate utility is provided along with the product in the product installation media.
  • The gzip utility must be installed separately.

Veeam Agent Computer (macOS)

A computer that you want to protect with Veeam Agent for Mac must meet the following requirements:

Specification

Requirement

Hardware

The protected macOS computer must meet the following hardware requirements:

  • CPU: x64 or ARM Apple-branded hardware*
  • Disk Space: 200 MB free disk space for product installation
  • Network: 10 Mbps or faster network connection to a backup target

* On a macOS computer with the ARM Apple-branded hardware, the product is running using the Rosetta Translation Environment.

OS

Veeam Agent supports the following macOS versions:

  • Ventura 13.0
  • Monterey 12.0 – 12.6.X
  • Big Sur 11.0 – 11.6.X
  • Catalina 10.15.X
  • Mojave 10.14.X
  • High Sierra 10.13.6

File System

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

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

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

Consider the following:

  • Sortware RAID is not supported.
  • Total size of all file systems included in a file-level backup must not exceed 218 TB. This limitation also applies to all file systems where files you plan to back up are located.
  • Size of a file in a backup must not exceed 16 TB.
  • Name of a file in a backup must not be larger than 254 bytes.

Keep in mind that characters that you can use in the file name may be encoded in 2 bytes or more.

Backup Target

Backup can be performed to the following types of storage:

For Veeam Agent backup jobs managed by the backup server

For Veeam Agent backup jobs managed by Veeam Agent

System Requirements IMPORTANT

[For Veeam Agent for Microsoft Windows] We do not recommend targeting a backup job at the storage device with the exFAT file system. If the protected computer runs Microsoft Windows 10 or Microsoft Windows Server 2019 and later, this configuration may lead to the backup data corruption caused by the exFAT file system issue.

 

Network

Consider the following:

System Requirements TIP

For Veeam Agent computers that are included in a protection group for pre-installed Veeam Agents, only Veeam Backup & Replication server must be resolvable into IPv4 address.