Backup Job fails

[pharao50]

Hello community,

Case #04485533

I'm really new to linux systems and try to get my veeam backup running. I am running the community edition of B&R, have a configured schedule for entire machine.

My Client system:
Debian 10.4 x64
kernel: 4.19.0-10-amd64
Patitioning: LVM

Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 8.8M 1.6G 1% /run
/dev/mapper/de1--wte13992--vg-root 23G 3.0G 19G 14% /
tmpfs 7.8G 0 7.8G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
/dev/nvme0n1p2 237M 49M 176M 22% /boot
/dev/nvme0n1p1 511M 5.2M 506M 1% /boot/efi
/dev/mapper/de1--vg-tmp 1.8G 7.2M 1.7G 1% /tmp
/dev/mapper/de1--vg-var 9.2G 1.2G 7.5G 14% /var
/dev/mapper/de1--vg-home 419G 102M 397G 1% /home
tmpfs 1.6G 0 1.6G 0% /run/user/1000


Hopefully you are able to help me anyway. Thank you for your help. regrads

[PTide]

Hi,

While you are waiting for the support team to respond, it would help if you could post the actual error that you get in the job session when it fails.

Thank you!

[pharao50]

True that would be helpful. I get these in my B&R action Log:

11/9/2020 11:01:34 AM :: Total size: 425,9 GB (101,2 MB used)
11/9/2020 11:01:39 AM :: Queued for processing at 09.11.2020 11:01:39
11/9/2020 11:01:39 AM :: Required backup infrastructure resources have been assigned
11/9/2020 11:01:43 AM :: Preparing to backup
11/9/2020 11:01:43 AM :: Failed to create volume snapshot
11/9/2020 11:01:43 AM :: Failed to take volume snapshot
11/9/2020 11:01:43 AM :: Failed to perform managed backup
11/9/2020 11:01:43 AM :: Child execution has failed. Exit code: [1].
11/9/2020 11:01:43 AM :: Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 snapstore_block_size_pow=14 change_tracking_block_size_pow=18 logdir=/var/log/veeam fixflags=0 logmaxsize=15728640].
11/9/2020 11:03:46 AM :: Processing finished with errors at 09.11.2020 11:03:46

[PTide]

Code: Select all

Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 snapstore_block_size_pow=14 change_tracking_block_size_pow=18 logdir=/var/log/veeam fixflags=0 logmaxsize=15728640]. 

Looks like the agent cannot load the veeamsnap module. Please check whether veeamsnap is installed

Thanks!

[pharao50]

I have installed it like the manual described it
FIrst I installed dkms and lvm2 as a dependency.
Afeter this I run:
dpkg -i ./veeam-release* && apt-get update
apt-get install veeam

If I check dksm status it says: veeamsnap, 4.0.1.2365: added

Is this what you meant?

[Natalia Lupacheva]

Hi,

​veeamsnap, 4.0.1.2365: added

means that module source is included in the kernel tree.
Please tae a look at this step by step guide to install veeamsnap correctly.
You might need to install linux-headers.

Thanks!

[pharao50]

Hi,

now I installed the Linux headers but still no success. I did:

apt-get install linux-headers-$(uname -r)

sudo dkms status
veeamsnap, 4.0.1.2365, 4.19.0-10-amd64, x86_64: installed

sudo dkms build -m veeamsnap -v 4.0.1.2365
Module veeamsnap/4.0.1.2365 already built for kernel 4.19.0-10-amd64/4

sudo dkms install -m veeamsnap -v 4.0.1.2365
Module veeamsnap/4.0.1.2365 already installed on kernel 4.19.0-10-amd64/x86_64

At the end I get same error message. Some more suggestions what I could do over here?

Thank you very much.

[PTide]

Do you have SecureBoot enabled by any chance?

Thanks!

[pharao50]

Hmm thats a good question. I guess so. Is this not possible? Btw. I am running this Debian Server on a Lenovo, ThinkCentre M920t if it is neccessary in any point

[PTide]

Totally possible.

Please check the note on the top of this page.

Thanks!

[pharao50]

Hey, I really missed this one. But it doesnt't work when I run

mokutil --import veeamsnap-ueficert.crt

I get this:

Failed to get file status, veeamsnap-ueficert.crt

Thanks

[Natalia Lupacheva]

Hi,

just a suggestion, could you check if the another veeamsnap is already loaded? (lsmod | grep veeam)

Thanks!

[pharao50]

Hi, for sure but if I run this command I get nothing back, so I guess there's no other instance running.

[PTide]

First of all, if you want to add a new key, you need to ensure that SecureBoot is actually enabled.

Secondly, since you use dkms version of the module, you need to sign the module by yourself and use your own public key instead of veeamsnap-ueficert.crt (which can be used only with pre-built binaries provided by Veeam).

Thirdly, the error that you get from mokutil might be related to the motherboard, please try importing the certificate manually using a USB stick. Also I guess it's worth reaching out to your distro community/support and ask what's wrong with mokutils.

Thanks!

[pharao50]

Okay, now I am really frustrated. Is it really that complicated to get this f*** Backup working? I was awaiting more from veeam!
Sorry but for this but can you provide a more detailed manual on how I can do this? You describe in your kb article import cert, yes great but for me useless information.
As it is a default debian blank distro I think its just your product which is not meant to work with this. If you can't help me out on this point I will have to search for a better backup solution. Sorry at this point veeam but even if it is a free to use product this is s****

[PTide]

In order to resolve technical issues you need to work with the support team. On this forum we can only help with the most common misconfig issues, suggest workarounds, and accept feature requests. We don't troubleshoot technical issues here.

So, my question is - how is it going with the support case? You've posted the case number, so apparently there must be some process going on, right? What's their response?

Meanwhile, let me break down what might be happening in you system. Let's assume that you use SecureBoot (which you haven't clarified yet, by the way):

The fact that you use Debain automatically means that you installed veeamsnap from source (veeamsnap_4.0.1.2365_all.deb package).

Therefore, the module that is installed in your system is not signed, thus your system won't let you load such module (we assume that SecureBoot is enabled)

In order to use a module that is not signed with SecureBoot you need to sign the module.
Here is an example of instruction how to do that on Debian 10. There are many HOWTOs on the Web describing how to automate the process (you need to sign modules every time yo upgrade your kernel).

Pending questions:

0. What did support say?
1. Is SecureBoot enabled?
2. What's your kernel version?

P.S. If you want to enjoy a pre-built binary signed version of veeamsnap, you need to install either RedHat-based distro, or SLES-based distro (SLED, for example) as we don't ship pre-built modules for Debian.

Thanks!

[pharao50]

Hi, sorry for my rough message yesterday but I am struggling with this for ages now.

The main thing is that I would like to use centos but I can't because of support of another application on this machine. They support Debain...
From veeam support I literally heared nothing back, another point why I am frustrated.

For installation I was using the package veeam-release-deb_1.0.7_amd64.deb as you can download it on the veeam page.

To finally answer your questions:
0. nothing
1. yes it is enabled
2. Kernel: Linux 4.19.0-10-amd64 as mentioned in an earlier post

Thanks

[PTide]

Got it, thank you very much. Now it's clear (from bullet #1) that the problem is that the kernel module is not signed. You need to sign the module and enroll the key in MOK.

Please see this article for details, especially this part as it will give you a better understanding of the problem:

Loading kernel modules that are not signed by a trusted key. By default, this will block out-of-tree modules including DKMS-managed drivers. However, you can create your own signing key for modules and add its certificate to the trusted list using MOK.

Good luck!

Thanks!