root@sv1cndmon:/var/tmp# dpkg -i veeamsnap_3.0.2.1185_all.deb
(Reading database ... 111052 files and directories currently installed.)
Preparing to unpack veeamsnap_3.0.2.1185_all.deb ...
Setting up veeamsnap (3.0.2.1185) ...
Loading new veeamsnap-3.0.2.1185 DKMS files...
Building for 4.19.0-6-amd64
Building initial module for 4.19.0-6-amd64
Done.
veeamsnap.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/dkms/
depmod...
Job for systemd-modules-load.service failed because the control process exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details.
DKMS: install completed.
root@sv1cndmon:/var/tmp#
Nov 13 17:12:07 sv1cndmon systemd[1]: Starting Load Kernel Modules...
-- Subject: A start job for unit systemd-modules-load.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit systemd-modules-load.service has begun execution.
--
-- The job identifier is 6193.
Nov 13 17:12:07 sv1cndmon systemd-modules-load[61186]: [b]Failed to find module '0821q'[/b]
Nov 13 17:12:07 sv1cndmon systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
8021q module is used for VLAN configuration and it is not related to Veeam Agent.
I would start with checking whether veeamsnap module has been installed (because I have a feeling that it actually has). Kindly check what's the output of
root@sv1cndmon:~# cat /etc/modules-load.d/modules.conf
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
0821q
bonding
-> so the module name ist wrong in this modules file
I changed this name and could install veeamsnap + veeam package now.
It wasn't a problem from veeam but rather a type of Debian 10.