Arch Linux User Repository

@cozzos84: Check your /etc/fstab. EFI-partition should be listed there. I think there were also detection problems depending on the FS profile (msdos vs. vfat).

Anyone have the same problem? [warn] Cannot find EFI boot manager entry for EFI System Partition GUID

Manjaro 6.9.8, EFI boot

Just try it ColdBrew. It cannot get worse ;)

It's a shame this is flagged, I'd love to help but I'm a novice to building packages!

Hello. 6.1.0.1498 is out with support for kernel versions up to 6.6. Tested it with 6.1 LTS and it worked fine. One note - libraries from 'veeam' package are now in a separate one called 'veeam-libs'.

Hello... i've Manjaro 6.6.1.

Installation of veeam ok but veeamsnap, all version, crash during dkms building.

DKMS make.log for veeamsnap-6.0.3.1221 for kernel 6.6.1-MANJARO (x86_64)
mer 15 nov 2023, 10:57:42, CET
make: ingresso nella directory «/home/sivens/Scaricati/00DELETE/linux-6.6.1»
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/log.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/mem_alloc.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/sparse_bitmap.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/container.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/container_spinlocking.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/queue_spinlocking.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/bitmap_sync.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/page_array.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/rangelist.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/rangelist_ex.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/rangevector.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/kernel_entries.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/blk_util.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/blk_direct.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/blk_redirect.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/blk_deferred.o
  CC [M]  /var/lib/dkms/veeamsnap/6.0.3.1221/build/defer_io.o
/var/lib/dkms/veeamsnap/6.0.3.1221/build/blk_util.c: In function ‘blk_dev_open’:
/var/lib/dkms/veeamsnap/6.0.3.1221/build/blk_util.c:37:15: error: too few arguments to function ‘blkdev_get_by_dev’
   37 |     blk_dev = blkdev_get_by_dev(dev_id, fmode, NULL);
      |               ^~~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/veeamsnap/6.0.3.1221/build/stdafx.h:63,
                 from /var/lib/dkms/veeamsnap/6.0.3.1221/build/blk_util.c:3:
./include/linux/blkdev.h:1482:22: note: declared here
 1482 | struct block_device *blkdev_get_by_dev(dev_t dev, blk_mode_t mode, void *holder,
      |                      ^~~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/veeamsnap/6.0.3.1221/build/stdafx.h:58:
/var/lib/dkms/veeamsnap/6.0.3.1221/build/blk_util.c: In function ‘blk_dev_close’:
./include/linux/fs.h:111:33: warning: passing argument 2 of ‘blkdev_put’ makes pointer from integer without a cast [-Wint-conversion]
  111 | #define FMODE_READ              ((__force fmode_t)0x1)
      |                                 ^~~~~~~~~~~~~~~~~~~~~~
      |                                 |
      |                                 unsigned int
/var/lib/dkms/veeamsnap/6.0.3.1221/build/blk_util.c:49:26: note: in expansion of macro ‘FMODE_READ’
   49 |     blkdev_put( blk_dev, FMODE_READ );
      |                          ^~~~~~~~~~
./include/linux/blkdev.h:1489:50: note: expected ‘void *’ but argument is of type ‘unsigned int’
 1489 | void blkdev_put(struct block_device *bdev, void *holder);
      |                                            ~~~~~~^~~~~~
make[2]: *** [scripts/Makefile.build:243: /var/lib/dkms/veeamsnap/6.0.3.1221/build/blk_util.o] Error 1
make[2]: *** Attesa per i processi non terminati....
make[1]: *** [/home/sivens/Scaricati/00DELETE/linux-6.6.1/Makefile:1913: /var/lib/dkms/veeamsnap/6.0.3.1221/build] Error 2
make: *** [Makefile:234: __sub-make] Error 2

Hello. Looks like initial 6.x versions were indeed unstable on various configurations to some extent, however I've recently tested 6.0.3.1221 release with the current Arch Linux LTS kernel (6.1.39 as of this moment) and it was a success. As @adlerweb said previously veeamsnap should now be replaced with blksnap. For source RPM files "el9" releases can be used.

Current 6.0.0 seems to fail with some configurations. On my arch system all jobs failed due to "BIOS boot partition size exceeds limit" - even tho I only use folder level backup without snapshots. My boot partition is a 512M RAID1 spanned over two disks.

Old 5.0.2 is still available, you can downgrade using the archived PKGBUILD (https://aur.archlinux.org/cgit/aur.git/tree/?h=veeam&id=289c6d2cc44718d7a633059b4b8acab540217915). Configuration database in /var/lib/veeam/ can not be downgraded and must be restored using a pre 6.x backup or deleted and jobs reconfigured.

Additionally: 6.0 now uses blksnap instead of veeamsnap, so deps might need updating: https://github.com/veeam/blksnap

Good news everyone: As of release 5.0.2, veeamsnap (and the veeam agent by extension) support Linux kernels up to and including 5.16. The AUR build has been updated to use the new 5.0.2 source and I have tested on my own machine on 5.10 LTS. Snapshotting works as it should.

Thanks!