Help Center
Choose product document...
Veeam Agent for Linux 3.0
User Guide

System Requirements

The protected Linux-based endpoint must meet requirements listed in the table below.

System Requirements Note:

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.

 

Specification

Requirement

Hardware

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.

OS

Linux kernel 2.6.32 or later1 is supported.

Both 64-bit and 32-bit versions of the following distributions2 are supported:

  • Debian 6.0 – 9.73
  • Ubuntu 10.04 – 19.043
  • RHEL 6.0 – 8.04
  • CentOS 6.0 – 7.74
  • Oracle Linux 6 (starting from UEK R1) – Oracle Linux 7 (up to UEK R4 U7)3
  • Oracle Linux 6 – 7.6 (RHCK)3
  • Fedora 23 – 303
  • openSUSE 11.3 – 13.2, 42.0 – 42.1, Tumbleweed3
  • openSUSE Leap 42.2 – 42.3, Leap 15.0 – 15.1
  • SLES 11 SP4 – 15 SP1
  • SLES for SAP 11 SP4 – 15 SP1

1 As long as you use kernels supplied by your distribution. Consider the following limitations:

  • Fedora is supported up to kernel 5.1.11, inclusive.
  • openSUSE Tumbleweed is supported up to kernel 5.1.7, inclusive.
  • Linux kernel 2.6.32-754.6.3 in CentOS / RHEL and Oracle Linux (RHCK) is not supported.

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:

  • Pre-built binary veeamsnap kernel module packages require kernel 2.6.32-131.0.15 or later for CentOS / RHEL 6 (excluding 2.6.32-279.el6.i686) and kernel 3.10.0-123 or later for CentOS / RHEL 7.0 – 7.6. For other kernels, install the veeamsnap module using the veeamsnap-3.0.2.1185-1.noarch.rpm source RPM package available in the Veeam software repository.
  • RHEL and derivatives running kernel 3.10.0-1062 or later require Veeam Agent for Linux build 3.0.2.1190. RHEL / CentOS / Oracle Linux (RHCK) 6.10 and 7.6 are supported up to certain kernel versions. For details, see this Veeam KB article.

File System

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

  • Veeam Agent for Linux does not back up volumes that reside on USB devices and SD cards.
  • The veeamsnap module provides RAM-based changed block tracking (CBT) mechanism. Every time the module is unloaded or Veeam Agent for Linux computer is rebooted, CBT data is reset. As a result, Veeam Agent reads the entire data added to the backup scope to detect what blocks have changed since the last job session, and incremental backup requires greater time.
  • Backup of machines used as cluster nodes is not supported (that includes backup of machines that use shared disks, clustered file systems or clustered LVM).
  • Certain limitations for EMC PowerPath configuration apply. To learn more, see this Veeam KB article.
  • BFQ I/O scheduler is not supported.

Software

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:

  • dkms1
  • gcc1
  • make1
  • perl1
  • kernel-headers1
  • kernel-devel1
  • libudev
  • libacl
  • libattr
  • lvm2
  • libfuse
  • libncurses52
  • dmidecode3
  • efibootmgr (for UEFI-based systems)
  • isolinux (for Debian-based systems)
  • syslinux (for RedHat-based systems)

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.

Backup Source

Any file systems and devices that are accessible from the host OS1.

1 Limitations apply. For more information, see File System.

Backup Target

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.

Network

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.
Veeam Large Logo

User Guide

Veeam Agent Management Guide

Veeam Backup & Replication Documentation

Veeam ONE Documentation

Veeam Management Pack Documentation

Veeam Agent for Microsoft Windows Documentation