Debian BTRFS restore fails - could not update UUID

Hi @maspiter -

Debian ‘Bookworm’ seems to not be yet supported for Veeam Linux Agent per Product Managers via this Forum thread:
https://forums.veeam.com/veeam-agents-for-linux-mac-aix-solaris-f41/agent-for-linux-terminates-on-debian-bookworm-t92896.html

Also note in the Forum post...they say VAL “should work”. Maybe follow the secondary links they talk about:
https://forums.veeam.com/veeam-agents-for-linux-mac-aix-solaris-f41/linux-agent-on-debian-t90746.html

and

https://helpcenter.veeam.com/docs/agentforlinux/userguide/installation_uefi_secure_boot.html?ver=60#importing-mok-for-dkms-kernel-module

..then see if that helps resolve your issue.

Thanks for your reply.

However, as per the page below it supports Debian Bookworm and BTRFS:

https://helpcenter.veeam.com/docs/agentforlinux/userguide/system_requirements.html?ver=60

I am not using Secure Boot. I think this is BTRFS related.

Ah yes. That Forum thread was from Dec last yr and up until Mar of this yr. VAL 6.1 came out end of May I believe.

I assume your Linux kernel is greater than 3.16? The VAL Sys Req’s state if using BTRFS, you need kernel > 3.16; and, you also are not running any abstracted layers on it either?..like LVM? The Guide says the below about that:
“BTRFS is supported only if it resides directly on a physical device with no additional abstraction layers (such as LVM, software RAID, dm-crypt and so on) below or above it.”

If all that is ok, you can maybe check the logs. See below for exporting logs.
https://helpcenter.veeam.com/docs/agentforlinux/userguide/logs_export.html?ver=60

Look at the green box about performing restore operations and where restore logs are located, if you use recovery media. Maybe try exporting the logs and see if anything definitive stands out. Otherwise, about the only thing I can suggest is contacting Veeam Support. Good idea especially if this is a bug...they can either provide a fix, or at least doing so reports it and a fix can be created (hopefully) for the issue.

Best.

Glad to hear you got the issue sorted @maspiter