- Note:
- To make UEFI systems with Secure Boot work with the pre-built veeamsnap kernel module, you need to enroll the Veeam public key to the MOK list using the mokutil utility. The key is available in the veeamsnap-ueficert-x.x.x.x.x.noarch package residing on the Veeam repository. To enroll the key:
- Request the enrollment of the public key with the following command: mokutil --import veeamsnap-ueficert.crt
- Reboot the Veeam Agent computer and complete the enrollment in the UEFI console.
- Download the Veeam software repository installation package (veeam-release) from the download page, and save the downloaded package on the computer where you plan to install the product.
- Navigate to the directory where you have saved the veeam-release package and install the package with the following commands:
For CentOS / RHEL / Oracle Linux / Fedora
rpm -ivh ./veeam-release* && yum check-update |
For openSUSE / SLES
zypper in ./veeam-release* && zypper refresh |
For Debian / Ubuntu
dpkg -i ./veeam-release* && apt-get update |
- Install Veeam Agent for Linux packages from the Veeam software repository. To install Veeam Agent for Linux, you can use a package manager of your choice that works with software packages in your Linux distrobutions. For example, use the following commands:
For CentOS / RHEL / Fedora
- Note:
- For CentOS / RHEL If the dkms package was installed int he OS prior to the time when you install Veeam Agent for Linux, to install the product, use the following command: yum install kmod-veeamsnap veeam. With this command, the veeamsnap kernel module will be installed from the binary kmod-veeamsnap package. Otherwise, the veeamsnap module will be installed from the source RPM package using dkms.
For Oracle Linux
yum install veeamsnap yum install veeam |
For openSUSE 11.3–13.2, Tumbleweed
For openSUSE Leap 42.2, 42.3, 15, 15.1
zypper in veeamsnap-kmp-default zypper in veeam |
For SLES with Default kernel
zypper in veeamsnap-kmp-default zypper in veeam |
For SLES with Trace kernel
zypper in veeamsnap-kmp-trace zypper in veeam |
For SLES with Xen kernel
zypper in veeamsnap-kmp-xen zypper in veeam |
For SLES with PAE kernel
zypper in veeamsnap-kmp-pae zypper in veeam |
For Debian / Ubuntu
Managing Package Dependencies
The following dependency packages may require special handling in case you see installation errors:
- dkms package is not present in default repositories for some Linux distributions. You should obtain it from third-party repositories:
- EPEL repository (for CentOS / RHEL / Oracle Linux / Fedora)
- Packman repository (for openSUSE / SLES). To learn more, see Installing dkms in openSUSE / SLES.
- Extended kernels, such as kernel-pae, kernel-uek and other, require appropriate kernel-devel packages to be installed, for example, kernel-pae-devel, kernel-uek-devel, and so on.
Version of the kernel-devel package must match your current kernel version. To check your current kernel version, run the uname -r command.
[For RHEL and derivatives] If the yum package manager installs packages that do not match your current kernel version, you should either update your system or fetch older versions of the required packages from the CentOS Vault repository.
Installing dkms in openSUSE / SLES
In openSUSE / SLES systems, while installing the dkms package, you may see an error similar to the following:
Problem: nothing provides kernel-devel needed by dkms-2.2.0.3-14.1.noarch Solution 1: do not install dkms-2.2.0.3-14.1.noarch Solution 2: break dkms-2.2.0.3-14.1.noarch by ignoring some of its dependencies |
To install the dkms package, do the following:
- Make sure that you have an appropriate kernel-devel package installed and its version matches your kernel version. For example:
root@localhost:~> rpm -qa | grep kernel-default kernel-default-devel-3.0.101-91.1 kernel-default-3.0.101-91.1 |
- Install the dkms package ignoring dependencies:
zypper -n install --force dkms |
- Make sure that you have allowed unsupported modules. To learn more, see this SUSE webpage.