System Requirements for Linux Computers (nosnap Veeam Agent)
If you plan to use a nosnap package to install Veeam Agent, the protected Linux computer must meet the following system requirements:
[For nosnap Veeam Agent for Linux] CPU: x86 or x64.
[For nosnap Veeam Agent for Linux on Power] CPU: IBM POWER9 or POWER10.
Memory: 1 GB RAM or more. Memory consumption varies depending on the backup type and the total amount of backed-up data.
Disk Space: 100 MB free disk space for product installation.
Network: 10 Mbps or faster network connection to a backup target.
Disk layout: MBR or GPT.
Important! Check considerations and limitations that apply to the list of supported OSes.
Nosnap Veeam Agent for Linux supports the 64-bit versions of the following distributions:
Veeam Agent supports 32-bit versions for RHEL 6 and Oracle Linux 6 distributions only.
Nosnap Veeam Agent for Linux on Power supports little endian versions of the following Linux distributions for IBM Power:
Important! Check considerations and limitations that apply to the list of supported file systems.
Veeam Agent for Linux supports consistent snapshot-based data backup for the following file systems:
[For nosnap Veeam Agent for Linux] BTRFS is supported only if it resides directly on a physical device with no additional abstraction layers (such as LVM, software RAID, dm-crypt and so on) below or above it.
[For nosnap Veeam Agent for Linux on Power] If BTRFS has additional abstraction layers (such as LVM, software RAID, dm-crypt and so on) above it, only file-level restore operations are supported. Instant Recovery, restore verification (SureBackup), bare metal recovery and volume-level restore are not supported.
Supported file systems that are not located on logical volumes, other file systems and network file systems like NFS or SMB shares can be backed up using the snapshot-less mode only. For details, see the Snapshot-Less File-Level Backup section in the Veeam Agent for Linux User Guide.
Important! Check considerations and limitations that apply to the list of supported components.
Protected computer must have the following components installed:
2 Nosnap Veeam Agent for Linux on Power does not require the following packages: dmidecode, efibootmgr, isolunux, mksquashfs, unsquashfs, wget and xorriso.
- Only GA versions of the supported distributions that have been released before the current version of Veeam Agent for Linux are supported.
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.
- The Linux OS must be set up to receive software updates from the default repositories enabled in the OS after installation.
- Veeam Agent for Linux does not back up volumes that reside on USB devices and SD cards.
- LVM volumes encrypted with dm-crypt software are not supported.
- Total size of all file systems must not exceed 218 TB. This limitation applies to all file systems where files you plan to back up are located.
- Size of a file included in a file-level backup must not exceed 16 TB.
- Name of a file must not be larger than 254 bytes.
Keep in mind that characters that you can use in the file name may be encoded in 2 bytes or more.
- Veeam Agent supports backup of extended attributes with the following limitations:
- Veeam Agent backs up extended attributes only with the following public namespaces: system, security, trusted, and user.
- All extended attribute names and values of a file must not exceed 4096 bytes (size of a default ext4 file system block). Veeam Agent does not back up attributes exceeding the limit.
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.
- Backup of file and directory attributes (for example, a — append only, c — compressed, and so on) is not supported.
- Each volume included in a backup must have a unique UUID.
- Consider the following about the backup of machines used as cluster nodes:
Consider the following:
- Backup of clustered file systems using a native file system snapshot is not supported. This includes snapshots created with the help of custom pre-job or post-job scripts.
- The following objects can be backed up only by snapshot-less file-level backup:
- Files on shared disks, clustered file systems or clustered LVM.
- Files on local file systems that are not hosted by LVM.
- Certain limitations for EMC PowerPath configuration apply. To learn more, see this Veeam KB article.
- Sparse files are not supported. Veeam Agent backs up and restores sparse files as regular files.
- Backup of pseudo file systems, such as /proc, /sys, tmpfs, devfs and others, is not supported.
Linux user account used to work with Veeam Agent for Linux must have the /bin/bash shell set as the default shell.
- [For nosnap Veeam Agent for Linux] 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. For details, see the MySQL Backup section in the Veeam Agent for Linux User Guide. 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. For details, see the PostgreSQL Backup section in the Veeam Agent for Linux User Guide.
- The btrfs-progs package version 3.16 or later is required.