Backup job fails - Modprobe?

Paulio · Post by **Paulio** » Jan 28, 2019 5:15 pm this post

Hi All

I seem to have got over one issue and run straight into another, although they might be related.
Previously I couldn't get veeamsnap to install although that seems to have gone OK in the end.

Then there was a missing dependency (lvm2) when trying to install veeam:

Code: Select all

bitnami@ubuntu:/tmp$ sudo apt-get install lvm2
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 lvm2 : Depends: libdevmapper-event1.02.1 (>= 2:1.02.74) but it is not going to be installed
        Depends: libreadline5 (>= 5.2) but it is not going to be installed
        Depends: watershed (>= 2) but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).


bitnami@ubuntu:/tmp$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  libdevmapper-event1.02.1 libreadline5 lvm2 watershed
Suggested packages:
  thin-provisioning-tools
The following NEW packages will be installed:
  libdevmapper-event1.02.1 libreadline5 lvm2 watershed
0 upgraded, 4 newly installed, 0 to remove and 182 not upgraded.
1 not fully installed or removed.
Need to get 0 B/622 kB of archives.
After this operation, 1,797 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package libdevmapper-event1.02.1:amd64.
(Reading database ... 98919 files and directories currently installed.)
Preparing to unpack .../libdevmapper-event1.02.1_2%3a1.02.77-6ubuntu2_amd64.deb ...
Unpacking libdevmapper-event1.02.1:amd64 (2:1.02.77-6ubuntu2) ...
Selecting previously unselected package libreadline5:amd64.
Preparing to unpack .../libreadline5_5.2+dfsg-2_amd64.deb ...
Unpacking libreadline5:amd64 (5.2+dfsg-2) ...
Selecting previously unselected package watershed.
Preparing to unpack .../archives/watershed_7_amd64.deb ...
Unpacking watershed (7) ...
Selecting previously unselected package lvm2.
Preparing to unpack .../lvm2_2.02.98-6ubuntu2_amd64.deb ...
Unpacking lvm2 (2.02.98-6ubuntu2) ...
Setting up libdevmapper-event1.02.1:amd64 (2:1.02.77-6ubuntu2) ...
Setting up libreadline5:amd64 (5.2+dfsg-2) ...
Setting up watershed (7) ...
update-initramfs: deferring update (trigger activated)
Setting up lvm2 (2.02.98-6ubuntu2) ...
update-initramfs: deferring update (trigger activated)
Setting up veeam (3.0.0.865) ...
Installing new version of config file /etc/veeam/veeam.ini ...
 Adding system startup for /etc/init.d/veeamservice ...
   /etc/rc0.d/K20veeamservice -> ../init.d/veeamservice
   /etc/rc1.d/K20veeamservice -> ../init.d/veeamservice
   /etc/rc6.d/K20veeamservice -> ../init.d/veeamservice
   /etc/rc2.d/S20veeamservice -> ../init.d/veeamservice
   /etc/rc3.d/S20veeamservice -> ../init.d/veeamservice
   /etc/rc4.d/S20veeamservice -> ../init.d/veeamservice
   /etc/rc5.d/S20veeamservice -> ../init.d/veeamservice
Processing triggers for libc-bin (2.19-0ubuntu6.7) ...
Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-164-generic

Then I installed veeam, which again, gave no indication of errors:

Code: Select all

bitnami@ubuntu:/tmp$ sudo dpkg -i ./veeam_3.0.0.865_amd64.deb
(Reading database ... 99050 files and directories currently installed.)
Preparing to unpack ./veeam_3.0.0.865_amd64.deb ...
Unpacking veeam (3.0.0.865) over (3.0.0.865) ...
Setting up veeam (3.0.0.865) ...
 System start/stop links for /etc/init.d/veeamservice already exist.
Processing triggers for ureadahead (0.100.0-16) ...

When I try starting the backup it almost immediately fails, and the log for the session is:

Code: Select all

[28.01.2019 15:41:16] <140432161662912> cli    | Initializing new log filter.
[28.01.2019 15:41:16] <140432161662912>        | ====================================================================================
[28.01.2019 15:41:16] <140432161662912> lpb    | {
[28.01.2019 15:41:16] <140432161662912> lpb    |   Veeam Agent for Linux: veeamjobman.
[28.01.2019 15:41:16] <140432161662912> lpb    |   Version: 3.0.0.865
[28.01.2019 15:41:16] <140432161662912> lpb    |   PID: 21085
[28.01.2019 15:41:16] <140432161662912> vmb    |   hostname: ubuntu
[28.01.2019 15:41:16] <140432161662912> vmb    |   uname
[28.01.2019 15:41:16] <140432161662912> vmb    |     sysname : Linux
[28.01.2019 15:41:16] <140432161662912> vmb    |     release : 3.13.0-164-generic
[28.01.2019 15:41:16] <140432161662912> vmb    |     version : #214-Ubuntu SMP Wed Dec 5 10:42:33 UTC 2018
[28.01.2019 15:41:16] <140432161662912> vmb    |     machine : x86_64
[28.01.2019 15:41:16] <140432161662912> lpb    | }
[28.01.2019 15:41:16] <140432161662912> lpbcore| Connecting to veeamservice...
[28.01.2019 15:41:16] <140432161662912>        |   Configuration load.
[28.01.2019 15:41:16] <140432161662912>        |   Configuration load. ok.
[28.01.2019 15:41:16] <140432161662912> lpbcore| Connecting to veeamservice... ok.
[28.01.2019 15:41:16] <140432161662912> lpbman | Main thread has started.
[28.01.2019 15:41:16] <140432161662912> lpbcore| No license installed.
[28.01.2019 15:41:16] <140432161662912> lpbcore| LpbManSession: Processing commands.
[28.01.2019 15:41:16] <140432161662912> lpbcore|   Sending PID: [21085].
[28.01.2019 15:41:16] <140432161662912> lpbcore|   Sending Session UUID: [{c03a2cb1-1cf7-44da-ab8c-46934fc20c4b}].
[28.01.2019 15:41:16] <140432161662912> lpbcore|   Waiting for a command.
[28.01.2019 15:41:16] <140432161662912> lpbcore|   LpbManSession: Starting backup job.
[28.01.2019 15:41:16] <140432161662912> lpbcore|     Job UUID: [{2924036c-925b-4dfd-9e4d-273da06ffafc}] (normal priority).
[28.01.2019 15:41:16] <140432161662912> lpbcore|     Is active full? [false].
[28.01.2019 15:41:16] <140432161662912> lpbcore|     Is snapshot required? [true].
[28.01.2019 15:41:16] <140432161662912> lpbcore|     System information:
[28.01.2019 15:41:16] <140432161662912> lpbcore|       Running [lsb_release -a].
[28.01.2019 15:41:16] <140432161662912> lpbcore|         Distributor ID:        Ubuntu
[28.01.2019 15:41:16] <140432161662912> lpbcore|         Description:   Ubuntu 14.04.4 LTS
[28.01.2019 15:41:16] <140432161662912> lpbcore|         Release:       14.04
[28.01.2019 15:41:16] <140432161662912> lpbcore|         Codename:      trusty
[28.01.2019 15:41:16] <140432161662912> lpbcore|       Running [cat /etc/*release].
[28.01.2019 15:41:16] <140432161662912> lpbcore|         DISTRIB_ID=Ubuntu
[28.01.2019 15:41:16] <140432161662912> lpbcore|         DISTRIB_RELEASE=14.04
[28.01.2019 15:41:16] <140432161662912> lpbcore|         DISTRIB_CODENAME=trusty
[28.01.2019 15:41:16] <140432161662912> lpbcore|         DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS"
[28.01.2019 15:41:16] <140432161662912> lpbcore|         NAME="Ubuntu"
[28.01.2019 15:41:16] <140432161662912> lpbcore|         VERSION="14.04.4 LTS, Trusty Tahr"
[28.01.2019 15:41:16] <140432161662912> lpbcore|         ID=ubuntu
[28.01.2019 15:41:16] <140432161662912> lpbcore|         ID_LIKE=debian
[28.01.2019 15:41:16] <140432161662912> lpbcore|         PRETTY_NAME="Ubuntu 14.04.4 LTS"
[28.01.2019 15:41:16] <140432161662912> lpbcore|         VERSION_ID="14.04"
[28.01.2019 15:41:16] <140432161662912> lpbcore|         HOME_URL="http://www.ubuntu.com/"
[28.01.2019 15:41:16] <140432161662912> lpbcore|         SUPPORT_URL="http://help.ubuntu.com/"
[28.01.2019 15:41:16] <140432161662912> lpbcore|         BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
[28.01.2019 15:41:16] <140432161662912> lpbcore|       Running [lsblk].
[28.01.2019 15:41:16] <140432161662912> lpbcore|         NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
[28.01.2019 15:41:16] <140432161662912> lpbcore|         fd0      2:0    1     4K  0 disk
[28.01.2019 15:41:16] <140432161662912> lpbcore|         sda      8:0    0    17G  0 disk
[28.01.2019 15:41:16] <140432161662912> lpbcore|         └─sda1   8:1    0  15.3G  0 part /
[28.01.2019 15:41:16] <140432161662912> lpbcore|         sr0     11:0    1  1024M  0 rom
[28.01.2019 15:41:16] <140432161662912> lpbcore|   LpbManSession: Starting backup job. ok.
[28.01.2019 15:41:16] <140432128345856>        | Thread started. Thread id: 140432128345856, parent id: 140432161662912, role: Volume backup job execution
[28.01.2019 15:41:16] <140432128345856> lpbcore| BackupJobPerformer: Creating backup.
[28.01.2019 15:41:16] <140432128345856> lpbcore|   Job information:
[28.01.2019 15:41:16] <140432128345856> lpbcore|     Job name: [FullBackup]. ID: [{2924036c-925b-4dfd-9e4d-273da06ffafc}].
[28.01.2019 15:41:16] <140432128345856> lpbcore|     Job source:
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Included [All System]  .
[28.01.2019 15:41:16] <140432128345856> lpbcore|     Job destination:
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Target repository [Repository_1] ID [{e97458fd-fd69-45af-8cea-f764145a262e}].
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Local repository path: [/mnt/Backup].
[28.01.2019 15:41:16] <140432128345856> lpbcore|     Job options:
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Compression: [Lz4]
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Block size: [KbBlockSize1024]
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Retention max points: [14].
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Pre-freeze: []
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Post-thaw: []
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Pre-job: []
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Post-job: []
[28.01.2019 15:41:16] <140432128345856> lpbcore|       IsSnapshotRequired: [true].
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Retry count: [3]
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Retry delay (ms): [600000]
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Indexing: File system indexing is disabled.
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Schedule: Enabled; Every Mon, Tue, Wed, Thu, Fri at 20:00.
[28.01.2019 15:41:16] <140432128345856> lpbcore|       Active full schedule: Disabled; Every 1 day of every month.
[28.01.2019 15:41:16] <140432128345856>        |   Creating child process: /usr/sbin/veeamagentid with arguments: /usr/sbin/veeamagentid, --log, /var/log/veeamagentid.log, /usr/sb$
[28.01.2019 15:41:16] <140432128345856> lpbcore|   Creating repository database accessor for local database.
[28.01.2019 15:41:16] <140432128345856> vmb    |   Found current backup for job, backup id {4a91b4c7-b3d3-4d02-a1d7-f6fccec7f2d7}.
[28.01.2019 15:41:16] <140432128345856> vmb    |   Reimporting backup [ubuntu FullBackup_4/FullBackup.vbm].
[28.01.2019 15:41:16] <140432128345856> vmb    |     Backup in repository [{e97458fd-fd69-45af-8cea-f764145a262e}].
[28.01.2019 15:41:16] <140432128345856> vmb    |     Importing backup [ubuntu FullBackup_4/FullBackup.vbm].
[28.01.2019 15:41:16] <140432128345856> vmb    |       Existing backup record will be removed from the database.
[28.01.2019 15:41:16] <140432128345856> vmb    |       Creating backup record: {4a91b4c7-b3d3-4d02-a1d7-f6fccec7f2d7} ubuntu FullBackup.
[28.01.2019 15:41:16] <140432128345856> vmb    |       Update encryption state.
[28.01.2019 15:41:16] <140432128345856> vmb    |     Update encryption state.
[28.01.2019 15:41:16] <140432128345856> vmb    |     Backup encryption state: Unencrypted
[28.01.2019 15:41:16] <140432128345856> vmb    |   [SessionLog][info] Preparing to backup.
[28.01.2019 15:41:16] <140432128345856> vmb    |   Found current backup for job, backup id {4a91b4c7-b3d3-4d02-a1d7-f6fccec7f2d7}.
[28.01.2019 15:41:16] <140432128345856> vmb    |   Reimporting backup [ubuntu FullBackup_4/FullBackup.vbm].
[28.01.2019 15:41:16] <140432128345856> vmb    |     Backup in repository [{e97458fd-fd69-45af-8cea-f764145a262e}].
[28.01.2019 15:41:16] <140432128345856> vmb    |     Importing backup [ubuntu FullBackup_4/FullBackup.vbm].
[28.01.2019 15:41:16] <140432128345856> vmb    |       Existing backup record will be removed from the database.
[28.01.2019 15:41:16] <140432128345856> vmb    |       Creating backup record: {4a91b4c7-b3d3-4d02-a1d7-f6fccec7f2d7} ubuntu FullBackup.
[28.01.2019 15:41:16] <140432128345856> vmb    |     Update encryption state.
[28.01.2019 15:41:16] <140432128345856> vmb    |     Backup encryption state: Unencrypted
[28.01.2019 15:41:16] <140432128345856> vmb    |   Found backup for job: [{4a91b4c7-b3d3-4d02-a1d7-f6fccec7f2d7}].
[28.01.2019 15:41:16] <140432128345856> vmb    |   BackupRepairAlg: checking whether latest restore point is corrupt.
[28.01.2019 15:41:16] <140432128345856> vmb    |   Backup contains no points.
[28.01.2019 15:41:16] <140432128345856> vmb    |   BackupRepairAlg: enumerating problems.
[28.01.2019 15:41:16] <140432128345856> vmb    |   BackupRepairAlg: enumerating problems. ok.
[28.01.2019 15:41:17] <140432128345856> lpbcore|   Enumerating backup objects.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Creating job objects filter.
[28.01.2019 15:41:17] <140432128345856> lpbcore|       Record type: [Include], object type: [AllSystem], value: []
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Creating job objects filter. ok.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Enumerating all block devices...
[28.01.2019 15:41:17] <140432128345856> lpbcore|       Ignored devices mask: [].
[28.01.2019 15:41:17] <140432128345856> lpbcore|       Skip filtering: [false].
[28.01.2019 15:41:17] <140432128345856> lpbcore|       Verbose logging: [false].
[28.01.2019 15:41:17] <140432128345856> lpbcore| ERR |Failed to create DeviceInfoEx for device: /dev/fd0
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |No such device or address
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |Failed to probe device [/dev/fd0].
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |An exception was thrown from thread [140432128345856].
[28.01.2019 15:41:17] <140432128345856> lpbcore| ERR |Failed to create DeviceInfoEx for device: /dev/sr0
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |No medium found
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |Failed to probe device [/dev/sr0].
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |An exception was thrown from thread [140432128345856].
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram0] (1:0) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram1] (1:1) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram2] (1:2) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram3] (1:3) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram4] (1:4) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram5] (1:5) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram6] (1:6) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram7] (1:7) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram8] (1:8) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram9] (1:9) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram10] (1:10) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram11] (1:11) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram12] (1:12) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram13] (1:13) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram14] (1:14) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/ram15] (1:15) with type [ram] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/loop0] (7:0) with type [loop] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/loop1] (7:1) with type [loop] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/loop2] (7:2) with type [loop] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/loop3] (7:3) with type [loop] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/loop4] (7:4) with type [loop] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/loop5] (7:5) with type [loop] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/loop6] (7:6) with type [loop] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Device [/dev/loop7] (7:7) with type [loop] is not supported for backup and WILL SKIPPED.
[28.01.2019 15:41:17] <140432128345856> lpbcore|       Found device: [/dev/sda]. Device number: [8:0]; Type: [scsi].
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Link: [/dev/sda].
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Link: [/dev/block/8:0].
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Link: [/dev/disk/by-id/wwn-0x5000c2947310f666].
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Link: [/dev/disk/by-id/ata-VMware_Virtual_IDE_Hard_Drive_00000000000000000001].
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Partition table type: [dos].
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Found device: [/dev/sda1]. Device number: [8:1]; Type: [scsi].
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Link: [/dev/sda1].
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Link: [/dev/block/8:1].
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Link: [/dev/disk/by-uuid/daecfb55-8ee7-4a7a-b958-f9c3db33e2ff].
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Link: [/dev/disk/by-id/wwn-0x5000c2947310f666-part1].
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Link: [/dev/disk/by-id/ata-VMware_Virtual_IDE_Hard_Drive_00000000000000000001-part1].
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Filesystem uuid: [daecfb55-8ee7-4a7a-b958-f9c3db33e2ff]; Type: [ext4]; Mount points: [/].
[28.01.2019 15:41:17] <140432128345856> lpbcore|     [2] block devices were detected.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Enumerating LVM devices...
[28.01.2019 15:41:17] <140432128345856> lpbcore|     [0] LVM volume groups were detected.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Enumerating BTRFS subvolumes...
[28.01.2019 15:41:17] <140432128345856> lpbcore|     [0] BTRFS subvolumes were detected.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Checking whether current system has stable btrfs driver version.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Kernel with unstable BTRFS module found.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Building backup objects.
[28.01.2019 15:41:17] <140432128345856> lpbcore|       Find root enumerated objects for backup.
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Find REO for backup of object [sda] (wwn-0x5000c2947310f666-LogicalDisk).
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Found REO for backup: [sda] (wwn-0x5000c2947310f666-LogicalDisk).
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Find REO for backup of object [sda1] (wwn-0x5000c2947310f666-part1).
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Found REO for backup: [sda] (wwn-0x5000c2947310f666-LogicalDisk).
[28.01.2019 15:41:17] <140432128345856> lpbcore|       Create disk backup object.
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Found filter for object [sda](0006ef76). Record type: [Include], value: []
[28.01.2019 15:41:17] <140432128345856> lpbcore|         No matching filters for object [0006ef76]
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Process primary partition [/dev/sda1] (0006ef76/o32256l16382967808).
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Is extended MBR partition.
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Found filter for object [sda1](0006ef76/o32256l16382967808). Record type: [Include], value: []
[28.01.2019 15:41:17] <140432128345856> lpbcore|           No matching filters for object [0006ef76/o32256l16382967808]
[28.01.2019 15:41:17] <140432128345856> lpbcore|           No matching filters for object [\]
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Partition [/dev/sda1] should be backed up.
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Detecting bootloader on device [/dev/sda].
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Detected GRUB legacy.
[28.01.2019 15:41:17] <140432128345856> lpbcore|           Device has MBR partition table.
[28.01.2019 15:41:17] <140432128345856> lpbcore|           MBR gap area size: [31744].
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Detected bootloader type: [GrubLegacy].
[28.01.2019 15:41:17] <140432128345856> lpbcore|         BIOS bootloader on [/dev/sda] will be backed up.
[28.01.2019 15:41:17] <140432128345856> lpbcore|         Disk [/dev/sda] will be backed up.
[28.01.2019 15:41:17] <140432128345856> lpbcore|   Computing backup estimated size.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Querying used space on sda.
[28.01.2019 15:41:17] <140432128345856> lpbcore|       Partition sda1, size: 16382967808, used: 5341839360.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Used space: 5341839360.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Overall data size used: 5341839360.
[28.01.2019 15:41:17] <140432128345856> lpbcore|   Taking snapshot.
[28.01.2019 15:41:17] <140432128345856> lpbcore|     Requesting snapshot for device sda1 [8:1].
[28.01.2019 15:41:17] <140432128345856> vmb    |     [SessionLog][processing] Creating volume snapshot.
[28.01.2019 15:41:17] <140432128345856> lpbcore| WARN|Method invocation was not finalized. Method id [1]. Class: [lpbcorelib::interaction::ISnapshotOperation]
[28.01.2019 15:41:17] <140432128345856> lpbcore| ERR |Child execution has failed. Exit code: [1].
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |--tr:Failed to execute [modprobe].
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 snapstore_block_size_pow=14 change_tracking_$
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |--tr:Failed to finish snapshot creation process.
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |--tr:Failed to execute method [1] for class [lpbcorelib::interaction::proxystub::CSnapshotOperationStub].
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |--tr:Failed to invoke method [1] in class [lpbcorelib::interaction::ISnapshotOperation].
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |An exception was thrown from thread [140432128345856].
[28.01.2019 15:41:17] <140432128345856> lpbcore| ERR |Failed to execute thaw script with status: fail.
[28.01.2019 15:41:17] <140432128345856> vmb    |     [SessionLog][error] Failed to create volume snapshot.
[28.01.2019 15:41:17] <140432128345856> lpbcore|   Taking snapshot. Failed.
[28.01.2019 15:41:17] <140432128345856> lpbcore| BackupJobPerformer: Creating backup. Failed.
[28.01.2019 15:41:17] <140432128345856> vmb    | [SessionLog][error] Failed to perform backup.
[28.01.2019 15:41:17] <140432128345856> vmb    | [SessionLog][error] Child execution has failed. Exit code: [1].
[28.01.2019 15:41:17] <140432128345856> vmb    | [SessionLog][error] Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 snapstore_block_size_pow=14 c$
[28.01.2019 15:41:17] <140432128345856> vmb    | [SessionLog][error] Processing finished with errors at 2019-01-28 15:41:17 GMT.
[28.01.2019 15:41:17] <140432128345856> lpbcore| ERR |Child execution has failed. Exit code: [1].
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |--tr:Failed to execute [modprobe].
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 snapstore_block_size_pow=14 change_tracking_$
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |--tr:Failed to finish snapshot creation process.
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |--tr:Failed to execute method [1] for class [lpbcorelib::interaction::proxystub::CSnapshotOperationStub].
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |--tr:Failed to create volume snapshot.
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |Backup job has failed.
[28.01.2019 15:41:17] <140432128345856> lpbcore| >>  |An exception was thrown from thread [140432128345856].
[28.01.2019 15:41:17] <140432161662912>        |   Closing socket device.
[28.01.2019 15:41:17] <140432161662912> lpbcore| LpbManSession: Processing commands. ok.
[28.01.2019 15:41:17] <140432161662912>        | Closing socket device.
[28.01.2019 15:41:17] <140432128345856> lpbcore| JOB STATUS: FAILED.
[28.01.2019 15:41:17] <140432128345856>        | Thread finished. Role: 'Volume backup job execution'.
[28.01.2019 15:41:17] <140432161662912>        | Closing socket device.
[28.01.2019 15:41:17] <140432161662912>        | Closing socket device.
[28.01.2019 15:41:17] <140432161662912> lpbman | Application session has been finished.

I found another forum topic that was addressing a very similar (I think) issue and the OP was asked to "...lsmod | grep veeam and if that results nothing do modprobe veeamsnap and see if that works fine"

I get:

Code: Select all

bitnami@ubuntu:/$ lsmod | grep veeam
bitnami@ubuntu:/$ sudo modprobe veeamsnap
modprobe: ERROR: could not insert 'veeamsnap': Exec format error

If I then " dmesg | grep veemsnap" I get nothing back.

Anyone got any ideas please?

Many thanks

Post by **PTide** » Jan 28, 2019 10:30 pm this post

Please check whether there is a module .ko file built for your currently running kernel. .ko files can be found under /lib/modules/<kernel version>/extra

Thanks

sunmoom · Post by **sunmoom** » Aug 20, 2020 4:48 am this post

I spent one day on the similar issue.

The reason can be that you have enabled secure boot.

run mokutil --sb-state to check status.

If it is secureboot enabled, run modprobe veeamsnap, it would tell you not permitted.

You then either turn off the secureboot, or sign the veeamsnap by yourself. I chose the latter one.

steps:
1. export USER="your name"
2. openssl req -new -x509 -newkey rsa:2048 -sha256 -keyout key.asc -out cert.der -outform der -nodes -days 4745 -subj "/CN=$USER/"
3. you may need install kernel-source for next step
/usr/src/linux-obj/…/scripts/sign-file sha256 ./key.asc ./cert.der $(modinfo -n veeamsnap)
4. mokutil --import cert.der
5. Reboot and follow instructions to Enroll MOK (Machine Owner Key). Here's a sample https://sourceware.org/systemtap/wiki/SecureBoot with pictures. The system will reboot one more time.

referred posts:
https://documentation.suse.com/sbp/all/ ... ec-signing
https://askubuntu.com/questions/760671/ ... 310#768310

Hope it helps.

R&D Forums

Backup job fails - Modprobe?

Re: Backup job fails - Modprobe?

Re: Backup job fails - Modprobe?

Who is online