Veeam Agent Installation for CentOS 9 Stream
Last updated
HI GIO User Guide EN
Last updated
This document is for installing the Veeam Backup Agent Linux on CentOS 9 Stream.
OS: CentOS 9 Stream, running kernel 5.14.0-344.el9.x86_64
Veeam repository: veeam-release-el9-1.0.8-1.x86_64.rpm
Veeam Agent: veeam-6.0.3.1221-1.el9.x86_64
Step 1: Download Veeam repository:
The Veeam repository for Linux can be found at Index of /backup/linux/agent/rpm/el/9/x86_64/ . On this page, select "veeam-release-el9-1.0.8-1.x86_64.rpm".
Step 2: Install Veeam and dependencies:
This will download an RPM file. You will likely be unable to download this directly from this page to your Linux machine, as your server will likely not have a GUI or web browser. To get around this, it is best to download the RPM to your workstation and then use WinSCP or MobaXterm to copy the RPM file to your server via SSH.
Once the RPM is on your server, install it and its dependencies:
The modules bdevfilter and blksnap will be created in /lib/modules/$(uname -r)/extra
We can confirm that this module has not loaded by running lsmod, and grepping for blksnap. We will see that grep returns 0 lines of output.
Step 3: Insert modules bdevfilter and blksnap:
Important: If the server boots with Secure Boot, we can’t insert the module → Must run step 3 on Secure Boot below first.
We need to load the module into the currently running kernel using insmod:
At this point, our agent-based backups will run fine; however, the loaded module will not persist if we reboot. We must create a file called /etc/modules-load.d/bdevfilter.conf and/etc/modules-load.d/blksnap.conf , and make sure that it has the name of the kernel module. We must also run depmod to add the loaded kernel module to the kernel module dependencies list.
Once we reboot the CentOS server, the veeamsnap module will automatically be loaded as a kernel module.
And our agent-based backups will now work correctly.
Grand permission for 3 scripts:
# chmod u+x one-time-setup sign-modules dkms-sign-module
Create 2 files for signing modules to the UEFI database.
Run the file one-time-setup first and then reboot:
During the reboot, when prompted, press any key to perform MOK management.
At the wizard's first step, select Enroll MOK and press [Enter].
At the Enroll the key(s) step, select Yes and press [Enter].
Provide the password for the root account and press [Enter].
At the final step, select Reboot and press [Enter].
After that, sign 2 modules by running file sign-modules:
Step 4: Insert modules bdevfilter and blksnap:
We need to load the module into the currently running kernel using insmod:
At this point, our agent-based backups will run fine; however, the loaded module will not persist if we reboot. We must create a file called /etc/modules-load.d/bdevfilter.conf and/etc/modules-load.d/blksnap.conf , and make sure that it has the name of the kernel module. We must also run depmod to add the loaded kernel module to the kernel module dependencies list.
Once we reboot the CentOS server, the veeamsnap module will automatically be loaded as a kernel module.
And our agent-based backups will now work correctly.
The Veeam repository for Linux can be found at Index of /backup/linux/agent/rpm/el/9/x86_64/ . On this page, select "veeam-release-el9-1.0.8-1.x86_64.rpm".
Download 3 scripts from the link: Make DKMS sign kernel modules on installation, with full script support and somewhat distro independent and put it in the directory just created:
