Agent-based backup of Windows, Linux, Max, AIX and Solaris machines.
Post Reply
zimeon
Novice
Posts: 8
Liked: 2 times
Joined: May 26, 2018 5:55 pm
Contact:

Debian Trixie - CVbrOibScope: Unable to update OIB

Post by zimeon »

Found a possible but with Veeam B&R 12 (12.3.2.4165) and Debian 13 - Trixie that was working before with agent version (6.3.2.1207). I have the community edition, so no official support. Couldn't find any matching KB about this.
Postgresql server for Veeam B&R is version 16.9 (I know its not supported, perhaps it's not the root cause as it used to work). I've tried to create a new Full backup but to no avail. The agent was able to successfully backup the machine last month 16.9.2025, but I didn't catch it until now.

--- log snippets deleted by moderator ---
PetrM
Veeam Software
Posts: 4005
Liked: 688 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Debian Trixie - CVbrOibScope: Unable to update OIB

Post by PetrM »

Hi Mike,

Please provide a support case ID as requested when you create a new topic about a technical issue. As mentioned in the support policy:
Free license customers have support via web or email only on a best effort basis only.
We cannot troubleshoot technical issues effectively over the forum posts. All posts about technical issues without case ID will be eventually deleted by the forum moderator. You can also upload debug logs for our support as per the instruction of this KB.

Thanks!
zimeon
Novice
Posts: 8
Liked: 2 times
Joined: May 26, 2018 5:55 pm
Contact:

Re: Debian Trixie - CVbrOibScope: Unable to update OIB

Post by zimeon » 1 person likes this post

Opened a case now (Case #07861018). Didn't expect to be able to do that with community edition.
zimeon
Novice
Posts: 8
Liked: 2 times
Joined: May 26, 2018 5:55 pm
Contact:

Re: Debian Trixie - CVbrOibScope: Unable to update OIB

Post by zimeon »

Managed to figure this out. It was due to EFI boot manager having invalid data in it, and re-creating it solved the issue.

Code: Select all

:~$ efibootmgr -v
BootCurrent: 0001
Timeout: 5 seconds
BootOrder: 0001,0003
Boot0001* debian        HD(1,GPT,327e905f-22fc-4c0f-828b-e63c1d3064e2,0x800,0x100000)/File(\EFI\debian\shimx64.efi) File(.)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 5f 90 7e 32 fc 22 0f 4c 82 8b e6 3c 1d 30 64 e2 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 64 00 65 00 62 00 69 00 61 00 6e 00 5c 00 73 00 6    8 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 04 00 00 00 49 53 50 48
Boot0003  USB:          PciRoot(0x0)/Pci(0x14,0x0)4eac0881119f594d850ee21a522c59b20b80000049535048
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 7f ff 04 00
    data: 4e ac 08 81 11 9f 59 4d 85 0e e2 1a 52 2c 59 b2 0b 80 00 00 49 53 50 48

The problematic part was " File(.)" which shouldn't be there. To solve the issue, I first deleted the boot entry with "sudo efibootmgr -b 0001 -B", and then recreated it with sudo efibootmgr -c -d /dev/nvme0n1p1 -p 1 -L "debian" -l '\EFI\debian\shimx64.efi'. End result looking like this;

Code: Select all

:~$ efibootmgr -v
BootCurrent: 0001
Timeout: 5 seconds
BootOrder: 0000,0003
Boot0000* debian        HD(1,GPT,327e905f-22fc-4c0f-828b-e63c1d3064e2,0x800,0x100000)/File(\EFI\debian\shimx64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 5f 90 7e 32 fc 22 0f 4c 82 8b e6 3c 1d 30 64 e2 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 64 00 65 00 62 00 69 00 61 00 6e 00 5c 00 73 00 6    8 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0003  USB:          PciRoot(0x0)/Pci(0x14,0x0)4eac0881119f594d850ee21a522c59b20b80000049535048
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 7f ff 04 00
    data: 4e ac 08 81 11 9f 59 4d 85 0e e2 1a 52 2c 59 b2 0b 80 00 00 49 53 50 48
After that, a quick reboot and backups worked again.
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 1 guest