The protected Linux-based endpoint must meet requirements listed in the table below.
The following system requirements apply to Veeam Agent for Linux operating in the standalone mode. To learn about system requirements for Veeam Agent managed by Veeam Backup & Replication, see the System Requirements section in the Veeam Agent Management Guide.
CPU: x86-64 processor (i386 or later).
Memory: 1 GB RAM.
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. Containers and paravirtualized instances are not supported. OVM is supported with limitations1.
1 Veeam Recovery Media version 3.0 does not support OVM virtual machines. Use a previous version of Veeam Recovery Media or contact Veeam Customer Support for workarounds.
Linux kernel 2.6.32 or later1 is supported.
Both 64-bit and 32-bit versions of the following distributions2 are supported:
1 As long as you use kernels supplied by your distribution. Consider the following limitations:
2 Only GA versions that have been released before the current version of Veeam Agent for Linux are supported.
3 Pre-built binary veeamsnap kernel module packages are not compatible with these distributions. Use the dkms packages instead.
4 Consider the following:
Veeam Agent for Linux supports consistent snapshot-based data backup for the following file systems1:
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 Snapshot-Less File-Level Backup.
1 Consider the following:
Important! Linux user account used to work with Veeam Agent for Linux must have the /bin/bash shell set as the default shell.
Protected computer must have the following components installed:
1 Not required for CentOS, RHEL and SLES distributions if a pre-built binary veeamsnap package is to be installed. For details, see Installing Veeam Agent for Linux.
2 For openSUSE Leap 15 and SLES distributions, either of the following packages is required: libncurses5 or libncurses6.
3 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.
Any file systems and devices that are accessible from the host OS1.
1 Limitations apply. For more information, see File System.
Backup can be performed to the following types of storage:
- Local (internal) storage of the protected computer (not recommended).
- Direct attached storage (DAS), such as USB, eSATA or Firewire external drives.
- Network Attached Storage (NAS) able to represent itself as SMB (CIFS) or NFS share. Requires cifs-utils or nfs-utils packages to be installed on the Veeam Agent for Linux computer, depending on a network storage type.
- Veeam Backup & Replication 9.5 Update 4 or later backup repository (except DataDomain DDboost, HPE StoreOnce).
- Veeam Cloud Connect 9.5 Update 4 or later cloud repository.
Consider the following:
- Veeam Agent for Linux should be able to establish a direct IP connection to the Veeam Backup & Replication server. Thus, Veeam Agent for Linux cannot work with Veeam Backup & Replication that is located behind the NAT gateway.
- Domain names of the Veeam Agent computer, Veeam Backup & Replication server and other servers in the Veeam backup infrastructure must be resolvable into IPv4 addresses.