[LINUX] Kernel 5.16 and later, veeamsnap support

[bassopt]

Looks like it’s broken again using kernel 5.15.

[mikeely]

Seconded. It's 100% broken in 5.15.

[micoolpaul]

What's the error/output when trying to use this?

[PTide]

Effective today, the current versions is 5.0.2 (supports kernels up to 5.16).

Should you encounter any issues with kernels higher than 5.16, please report here or on our github.

Thanks!

[Obi]

The current Repository package for Debian/Ubuntu (veeam-release-deb_1.0.8_amd64.deb) **does not** create the repository file in /etc/apt/sources.list.d/ therefore installation fails with: "E: Unable to locate package veeam".

CORRECTION:

My previous post on Dec 30, 2021 5:41 pm can be ignored/deleted as the issue is on my end.

[PTide]

@Obi,

Would you expand a little bit on what exactly was not right?

Thanks!

[hxp]

Complete list of new features and enhancements > What's New in 5.0

veeam-agents-for-linux-mac-aix-solaris- ... 39579.html
https://www.veeam.com/veeam_agent_linux ... new_wn.pdf

The link returns 404.

[HannesK]

thanks, I will talk to the web team. for unknown reason https://www.veeam.com/veeam_agent_linux ... new_wn.pdf is linked now in helpcenter

UPDATE: Fixed

[philipraets]

Hi,

is there a timeline when veeam agent for linux 6 will be released? the kernel module fails to build on opensuse Tumbleweed with kernel 5.18.1 installed (kernel-default + kernel-devel + kernel-default-devel)

Code: Select all

DKMS make.log for veeamsnap-5.0.2.4567 for kernel 5.18.1-1-default (x86_64)
do 09 jun 2022 09:31:55 CEST
make: Entering directory '/usr/src/linux-5.18.1-1-obj/x86_64/default'
  CC [M]  /var/lib/dkms/veeamsnap/5.0.2.4567/build/log.o
  CC [M]  /var/lib/dkms/veeamsnap/5.0.2.4567/build/mem_alloc.o
  CC [M]  /var/lib/dkms/veeamsnap/5.0.2.4567/build/sparse_bitmap.o
  CC [M]  /var/lib/dkms/veeamsnap/5.0.2.4567/build/container.o
In file included from /var/lib/dkms/veeamsnap/5.0.2.4567/build/container.c:3:
/var/lib/dkms/veeamsnap/5.0.2.4567/build/stdafx.h:77:10: fatal error: linux/genhd.h: No such file or directory
   77 | #include <linux/genhd.h> // For basic block driver framework
      |          ^~~~~~~~~~~~~~~
compilation terminated.
In file included from /var/lib/dkms/veeamsnap/5.0.2.4567/build/mem_alloc.c:3:
/var/lib/dkms/veeamsnap/5.0.2.4567/build/stdafx.h:77:10: fatal error: linux/genhd.h: No such file or directory
   77 | #include <linux/genhd.h> // For basic block driver framework
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [/usr/src/linux-5.18.1-1/scripts/Makefile.build:289: /var/lib/dkms/veeamsnap/5.0.2.4567/build/container.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [/usr/src/linux-5.18.1-1/scripts/Makefile.build:289: /var/lib/dkms/veeamsnap/5.0.2.4567/build/mem_alloc.o] Error 1
In file included from /var/lib/dkms/veeamsnap/5.0.2.4567/build/log.c:3:
/var/lib/dkms/veeamsnap/5.0.2.4567/build/stdafx.h:77:10: fatal error: linux/genhd.h: No such file or directory
   77 | #include <linux/genhd.h> // For basic block driver framework
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [/usr/src/linux-5.18.1-1/scripts/Makefile.build:289: /var/lib/dkms/veeamsnap/5.0.2.4567/build/log.o] Error 1
In file included from /var/lib/dkms/veeamsnap/5.0.2.4567/build/sparse_bitmap.c:3:
/var/lib/dkms/veeamsnap/5.0.2.4567/build/stdafx.h:77:10: fatal error: linux/genhd.h: No such file or directory
   77 | #include <linux/genhd.h> // For basic block driver framework
      |          ^~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [/usr/src/linux-5.18.1-1/scripts/Makefile.build:289: /var/lib/dkms/veeamsnap/5.0.2.4567/build/sparse_bitmap.o] Error 1
make: *** [../../../linux-5.18.1-1/Makefile:1848: /var/lib/dkms/veeamsnap/5.0.2.4567/build] Error 2
make: Leaving directory '/usr/src/linux-5.18.1-1-obj/x86_64/default'

[HannesK]

Hello,
yes, Fedora and openSUSE Tumbleweed are supported up to kernel 5.15.7.

Veeam Agent for Linux V6 would be together with V12, which might be around end of this year.

Depending on what you need to back up, it might be a workaround just using NAS backup. NAS backup has no kernel dependencies and can back up files directly from a managed Windows / Linux server.

Best regards,
Hannes