Veeam Agent Installation for CentOS 8 Stream

• This will install the required packages for the Veeam agent, including a kmod-veeamsnap package; however, you will notice that there are still issues with the Linux kernel module for veeamsnap. If we inspect the files installed with kmod-veeamsnap, and compare it with our current kernel version, we can see that the kernel module is not installed for our version. The difference is very minute.

• From this, we can see that the kernel module was installed for 4.18.0-477.10.1.el8_7.x86_64, but our current kernel is 4.18.0-500.el8.x86_64.

• Without this kernel module, our agent based Veeam backups will fail.

• We can confirm that this module has not loaded by running lsmod, and grepping for Veeam. We will see that grep returns 0 lines of output.

• Fortunately, the difference in these kernel versions is small enough that the veeamsnap.ko file will still work for us.

• First, we must create the /extra/ directory for our kernel version, then copy the kernel module to this directory.

Step 3: Insert module veeamsnap:

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 will need to create a file called /etc/modules-load.d/veeam.conf, and make sure that it has the name of the kernel module in it. We will also need to run depmod to add the loaded kernel module into the kernel module dependencies list.

Now, 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.

• This will install the required packages for the Veeam agent, including a kmod-veeamsnap package; however, you will notice that there are still issues with the Linux kernel module for veeamsnap. If we inspect the files installed with kmod-veeamsnap, and compare it with our current kernel version, we can see that the kernel module is not installed for our version. The difference is very minute.

• From this we can see that the kernel module was installed for 4.18.0-477.10.1.el8_7.x86_64, but our current kernel is 4.18.0-500.el8.x86_64.

• Without this kernel module, our agent based Veeam backups will fail.

• We can confirm that this module has not loaded by running lsmod, and grepping for Veeam. We will see that grep returns 0 lines of output.

• Fortunately, the difference in these kernel versions is small enough that the veeamsnap.ko file will still work for us.

• First, we need to create the /extra/ directory for our kernel version, then copy the kernel module over to this directory.

Step 3: Enrolling Veeam Kernel Module Key:

Install the package that contains the public key for pre-built Veeam kernel module by using the following command:

We will have the notification like this:

Reboot the computer to enroll the Veeam public key into the UEFI database.

During reboot, when prompted, press any key to perform MOK management.

At the first step of the wizard, 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].

Step 4: Insert module veeamsnap:

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 will need to create a file called /etc/modules-load.d/veeam.conf, and make sure that it has the name of the kernel module in it. We will also need to run depmod to add the loaded kernel module into the kernel module dependencies list.

Now, 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.