Appendix A. Requirements for veeam-nosnap

You can install Veeam Agent for Linux using a veeam-nosnap package. This package allows Veeam Agent to operate without veeamsnap kernel module.

The veeam-nosnap package can be useful in the following cases:

  • You do not want to install kernel sources and compilers on your computer.
  • You want to use third-party tools to create data snapshots.
  • You want to perform bare metal restore, but Veeam Recovery Media does not work with your computer. In this case you can install the veeam-nosnap package on LiveCD of your choice and access the Veeam recovery UI.
  • You want to back up machines that are used as cluster nodes.

Before you install Veeam Agent using the veeam-nosnap package, consider the following limitations:

  • The veeam-nosnap package has an experimental support status. For details about experimental support, see this Veeam KB article.
  • The RAM-based changed block tracking (CBT) mechanism is not supported. As a result, if you plan to back up a significant amount of data, the backup will require greater time.
  • Veeam Agent can create a snapshot of LVM logical volumes and Btrfs subvolumes. To back up data that resides on other file systems and volumes, you can use only file-level backup in the snapshot-less mode. For details, see Snapshot-Less File-Level Backup.
  • For a successful backup, Veeam Agent requires unallocated extents on volume groups.
  • For a successful bare metal restore, all disks of the Veeam Agent computer you want to restore must be available in the backup.

System Requirements for veeam-nosnap

If you plan to use the veeam-nosnap package to install Veeam Agent, the protected Linux computer meet requirements listed in the table below. To learn about system requirements for Veeam Agent installed using the Veeam kernel module packages, see System Requirements.




CPU: x86-64 processor (i386 or later).

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. Containers and paravirtualized instances are not supported. Oracle VM virtual machines are supported with limitations.


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

Veeam Agent supports the 64-bit versions of the following distributions:

  • Debian 10.13 – 12.0
  • Ubuntu 16.04, 18.04, 20.04, 22.04, 22.10 and 23.04
  • RHEL 6.4 – 9.2
  • CentOS 7
  • Oracle Linux 6 – 9.2 (RHCK)
  • Oracle Linux 6 (starting from UEK R2) – Oracle Linux 9 (up to 5.15.0-

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

  • LVM.
  • Btrfs (for OSes that run Linux kernel 3.16 or later).

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.


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

Protected computer must have the following components installed:

  • perl
  • libacl
  • libattr
  • lvm2
  • libfuse
  • dmidecode
  • libmysqlclient
  • libpq5
  • 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)
  • tar (for file system indexing, log export and rotation)
  • gzip (for file system indexing, log export and rotation)

Considerations and Limitations


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.

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.

Appendix A. Requirements for veeam-nosnap NOTE

Consider the following:

  • During volume-level backup, data from shared disks, clustered file systems or clustered LVM will not be backed up.
  • To perform volume-level backup, Veeam Agent for Linux will create an LVM snapshot, which can cause instability of the cluster or cluster software. This can happen due to the failover conditions configured for the cluster. However, if the cluster instability is caused by creation of an LVM snapshot only during backup, please contact Veeam support for assistance.
  • 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.
  • 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.


Appendix A. Requirements for veeam-nosnap IMPORTANT

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

Backup Source

Any file systems and devices that are accessible from the host OS. To learn about limitations, see File System.

Backup Target

Backup can be performed to the following types of storage:

  • On-premises or cloud-based object 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 12 or later backup repository (including deduplication appliances).
  • Veeam Cloud Connect 12 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 or IPv6 addresses.