Agent for Linux terminates on Debian Bookworm

[RandomTrooper]

This seemed so simple, yet the backup dies without much to go on...


This is Debian Bookworm headless with 6.1.0-18-amd64 kernel.

Installed with blksnap. The interface loads and I can create a backup profile, but “run now” falters immediately.

Appreciate any suggestions.

[rovshan.pashayev]

Hello @RandomTrooper

That sounds like a technical issue. Please provide a support case ID for this issue, as requested when you click New Topic.
Support can only help if you upload logs https://www.veeam.com/kb1832

Without case number, the topic will eventually be deleted by moderators.

Meanwhile I can suggest you to make sure if you have Secure Boot enabled or not. If enabled you will need make sure that MOK Enrollment is done. Please check this similar topic here: veeam-agents-for-linux-mac-aix-solaris- ... 90746.html

Best regards,
Rovshan.

[RandomTrooper]

My success with entering a support case has been 0%, as I am a "free' user, so I didn't see the value here (would there be a section on this forum for "free" users, that I've overlooked?).

However, the Secure Boot reference you provided looks interesting, so I will spend my time there to seek out a possible solution. My present situation is to image with Clonezilla which requires me to pull the server offline (which I'd like to avoid).

Thanks for your reply.

[sdriesmans]

Hello,

it seems that the Veeam agent for Debian bookworm is not yet supported ?

A client has the latest version of Debian bookworm installed, being 12.5.
Will the latest nosnap agent work on that version ?

Or when will there be a supported version of the agent ?

Many thanks in advance for your replies !

Best regards.

[rovshan.pashayev]

Hello,

Correct, as you mentioned, VAL does not support Debian 12.5 yet.

Nevertheless both veeam (with veeamsnap or blksnap modules) and veeam-nosnap agent should work.
Just follow the steps in the topic which I mentioned previously.
Also here is User Guide https://helpcenter.veeam.com/docs/agent ... nel-module regarding SecureBoot in Debian.

[sdriesmans]

@rovshan.pashayev

Thanks for your reply !

Is that secure boot option only for physical systems with UEFI ?

Our client has a virtual machine on which I need to install the agent on, in which I succeeded yesterday.
Does the MOK need to be imported as well on a virtual machine ?

Best regards

[sdriesmans]

It seems that the servers of my client do not have secure boot enabled on their virtual systems :

# mokutil --sb-state
EFI variables are not supported on this system
#

So I'm pretty sure I can ignore these mok-related informations.

Best regards

[rovshan.pashayev]

Hello,

Answer to your previous question: MOK enrollment is required for any system, physical or virtual, that has EFI Secure Boot enabled.

[sdriesmans]

@rovshan.pashayev

Ok, clear to me.

But when the "mokutil --sb-state" returns "EFI variables are not supported on this system", I can be sure that secure boot is not activated ?

Best regards

[rovshan.pashayev]

Hello,

"EFI variables are not supported on this system" output means, that machine runs on BIOS firmware.