Watch for FREE to expand your cloud and security skills
On-demand event
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
A Veeam Agent for Linux backup job fails with the following error:
Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0]
(The number of parameters listed in the error may vary depending on Veeam Agent for Linux version.)
This error occurs when the veeamsnap module cannot be loaded. The most common reasons are:
veeamsnap
kernel moduleThe veeamsnap module is available to be compiled using DKMS or as a precompiled module for select distros (kmod for RHEL/CentOS* or kmp for SLES/openSUSE).
For more information about installation requirements, please see: Veeam Agent for Linux - System Requirements.
*Precompiled veeamsnap kmod is not compatible with Oracle Linux.
veeamsnap
prerequisites for RHEL/CentOS 7.0+ are presentFor RHEL/CentOS 7.0+ using Veeam Agent for Linux version 4+, ensure that the python3 package is installed and working correctly. If it is not, install/fix it before proceeding with troubleshooting. Python3 is used to load the correct pre-compiled veeamsnap version into the kernel automatically.
Run the following commands to query if python3 is installed as a package:
rpm -q --whatprovides /usr/bin/python3
rpm -q --whatprovides python3
rpm -q --whatprovides /usr/bin/python3
python3-3.6.8-18.el7.x86_64
rpm -q --whatprovides python3
python3-3.6.8-18.el7.x86_64
veeamsnap
kernel module is installedUse the following command to determine if the veeamsnap module is installed:
rpm -qa | grep veeamsnap
If this command returns nothing, then the veeamsnap module is not installed.
Pre-compiled veeamsnap
kernel modules will be listed as:
kmod-veeamsnap
veeamsnap-kmp-default
dpkg-query -l | grep veeamsnap
veeamsnap
kernel module is loadedUse the following command to query the state of the veeamsnap module:
lsmod | grep veeamsnap
rmmod veeamsnap
veeamsnap
precompiled module compatibilityEach precompiled veeamsnap module is built for a specific version of RHEL/CentOS/SLES/openSUSE.
Use the examples below to check if the correct precompiled veeamsnap module is installed.
Check if the active kernel's major version matches one of the installed veeamsnap modules.
Example:
# uname -r
3.10.0-1160.25.1.el7.x86_64
# find /lib/modules | grep veeamsnap
/lib/modules/3.10.0-862.el7.x86_64/extra/veeamsnap.ko
/lib/modules/3.10.0-1062.el7.x86_64/extra/veeamsnap.ko
/lib/modules/3.10.0-1127.el7.x86_64/extra/veeamsnap.ko
/lib/modules/3.10.0-1160.el7.x86_64/extra/veeamsnap.ko
/lib/modules/3.10.0-123.el7.x86_64/extra/veeamsnap.ko
/lib/modules/3.10.0-229.el7.x86_64/extra/veeamsnap.ko
/lib/modules/3.10.0-327.el7.x86_64/extra/veeamsnap.ko
/lib/modules/3.10.0-514.el7.x86_64/extra/veeamsnap.ko
/lib/modules/3.10.0-693.el7.x86_64/extra/veeamsnap.ko
/lib/modules/3.10.0-957.el7.x86_64/extra/veeamsnap.ko
First, ensure that the kernel version in use corresponds with the OS version. Review SUSE KB#19587 for more information. If the kernel version does not correspond to the OS version, Veeam Agent for Linux and the veeamsnap
module may not load, or the wrong version may be installed.
The Veeam Agent for Linux user guide lists which version should be used with each SLES or openSUSE OS version.
Example:
# hostnamectl
Static hostname: testmachine
Transient hostname: testmachine
Icon name: computer-vm
Chassis: vm
Machine ID: 25433cc502ff0082e5f1ff835c01295b
Boot ID: 1296228f7483469b93db28713a2b40e0
Virtualization: vmware
Operating System: SUSE Linux Enterprise Server 12 SP3
CPE OS Name: cpe:/o:suse:sles_sap:12:sp3
Kernel: Linux 4.4.180-94.141-default
Architecture: x86-64
In this example, the kernel 4.4.180-94.141 is correct for the OS SLES12 SP3 - LTSS.
The Installing Veeam Agent for Linux in SLES user guide page indicates that this SLES OS version correlates to veeamsnap-kmp-default-5.0.0.4318_k4.4.73_5-2
If the "Failed to load module" error begins appearing after a kernel upgrade that does not change the release (version and SP), execute the following command to link the module to the new kernel and then try to rerun the job:
depmod -a
veeamsnap
moduleWhen using DKMS to compile the kernel module, ensure that the installed kernel-headers package matches the kernel in use. If the kernel-headers package is not installed, or the installed kernel-headers package does not match the kernel in use, you will need to install the matching kernel-headers package.
After installing/updating the kernel-headers package, reinstall Veeam Agent for Linux.
Examples of Matching kernel-headers and kernel:
# uname -r
5.4.0-77-generic
# dpkg-query -l | grep linux-headers
ii linux-headers-5.4.0-77 5.4.0-77.86 all Header files related to Linux kernel version 5.4.0
ii linux-headers-5.4.0-77-generic 5.4.0-77.86 amd64 Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
ii linux-headers-generic 5.4.0.77.80 amd64 Generic Linux kernel headers
# uname -r
4.14.35-1902.303.4.1.el7uek.x86_64
# rpm -qa | grep kernel-uek-devel
kernel-uek-devel-4.14.35-1902.303.4.1.el7uek.x86_64
veeamsnap
module with Secure BootIf Secure Boot is enabled, the kernel module may not be loaded due to system restrictions. In such a situation, review the following:
If the information in this article does not resolve the issue, please open a support case and include the following information.
Run each command as root, save the output, and attach it to the support case.
Note: Some commands may return an empty response, be sure to include these results.
(hostnamectl||uname -a)
cat /etc/*release
(rpm -qa||dpkg-query -l) | egrep -i '(veeam|dkms|kernel-headers|kernel.*devel|linux-image|linux-headers)' | sort
dkms status
mokutil --sb-state
mokutil --list-new
find /lib/modules -name '*veeam*' -exec ls -ld {} +
lsmod | grep -i veeam
modinfo veeamsnap
modprobe -vvv veeamsnap
Your feedback has been received and will be reviewed.
Please try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.