Backup agent for Linux servers and workstations on-premises or in the public cloud
Post Reply
pleibling
Novice
Posts: 5
Liked: never
Joined: Dec 17, 2015 7:51 pm

Backup Failed (failed to create snapshot)

Post by pleibling » Jan 19, 2018 8:48 am

Hello,

i'm new in Veeam Agent for Linux and not an specialist for Linux.

I have an Problem with Backup - it failes with an Error "failed to create snapshot" in the Log.

My System is an Debian 8 on VMWare 6.5, open-vm-tools are installed.

I append the Log at the bottom - it seems to be a problem with the Snapshot. For this i removed veeam (apt-get remove veeam*) and install it new (apt-get install veeam*).

This is the installation log:

Code: Select all

Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Note, selecting 'veeamsnap' for regex 'veeam*'
Note, selecting 'veeam-release-deb' for regex 'veeam*'
Note, selecting 'veeam' for regex 'veeam*'
Die folgenden NEUEN Pakete werden installiert:
  veeam veeam-release-deb veeamsnap
0 aktualisiert, 3 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
Es müssen noch 0 B von 30,3 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 51,9 MB Plattenplatz zusätzlich benutzt.
Vormals nicht ausgewähltes Paket veeamsnap wird gewählt.
(Lese Datenbank ... 55398 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../veeamsnap_2.0.0.400_all.deb ...
Entpacken von veeamsnap (2.0.0.400) ...
Vormals nicht ausgewähltes Paket veeam wird gewählt.
Vorbereitung zum Entpacken von .../veeam_2.0.0.400_amd64.deb ...
Entpacken von veeam (2.0.0.400) ...
Vormals nicht ausgewähltes Paket veeam-release-deb wird gewählt.
Vorbereitung zum Entpacken von .../veeam-release-deb_1.0.1_amd64.deb ...
Entpacken von veeam-release-deb (1.0.1) ...
Trigger für systemd (215-17+deb8u7) werden verarbeitet ...
Trigger für man-db (2.7.0.2-5) werden verarbeitet ...
veeamsnap (2.0.0.400) wird eingerichtet ...
Loading new veeamsnap-2.0.0.400 DKMS files...
Building only for 3.16.0-4-amd64
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
veeam (2.0.0.400) wird eingerichtet ...
veeam-release-deb (1.0.1) wird eingerichtet ...
After installation i check with lsmod | grep 'veeam' - but it founds nothing.

Did i have to install the veeamsnap Module manually? If yes, how i can do it?

This is the Backup Log:

Code: Select all

[18.01.2018 15:37:38] <140310336378752> cli    | Initializing new log filter.
[18.01.2018 15:37:38] <140310336378752>        | ====================================================================================
[18.01.2018 15:37:38] <140310336378752> lpb    | {
[18.01.2018 15:37:38] <140310336378752> lpb    |   Veeam Agent for Linux: veeamjobman.
[18.01.2018 15:37:38] <140310336378752> lpb    |   Version: 2.0.0.400
[18.01.2018 15:37:38] <140310336378752> lpb    |   PID: 19558
[18.01.2018 15:37:38] <140310336378752> lpb    |   uname
[18.01.2018 15:37:38] <140310336378752> lpb    |     sysname : Linux
[18.01.2018 15:37:38] <140310336378752> lpb    |     release : 3.16.0-4-amd64
[18.01.2018 15:37:38] <140310336378752> lpb    |     version : #1 SMP Debian 3.16.51-3 (2017-12-13)
[18.01.2018 15:37:38] <140310336378752> lpb    |     machine : x86_64
[18.01.2018 15:37:38] <140310336378752> lpb    | }
[18.01.2018 15:37:38] <140310336378752> lpbman | Main thread has started.
[18.01.2018 15:37:38] <140310336378752> lpbcore| Connecting to veeamservice...
[18.01.2018 15:37:38] <140310336378752>        |   Closing socket device.
[18.01.2018 15:37:38] <140310336378752> lpbcore| Connecting to veeamservice... ok.
[18.01.2018 15:37:38] <140310336378752> lpbcore| No license installed.
[18.01.2018 15:37:38] <140310336378752> lpbcore| LpbManSession: Processing commands.
[18.01.2018 15:37:38] <140310336378752> lpbcore|   Sending PID: [19558].
[18.01.2018 15:37:38] <140310336378752> lpbcore|   Sending Session UUID: [{80b59be5-6242-468d-939f-50db9ce06917}].
[18.01.2018 15:37:38] <140310336378752> lpbcore|   Waiting for a command.
[18.01.2018 15:37:38] <140310336378752> lpbcore|   LpbManSession: Starting backup job.
[18.01.2018 15:37:38] <140310336378752> lpbcore|     Job UUID: [{4985d60e-d64b-44ff-9748-7c0ea8177a70}] (normal priority).
[18.01.2018 15:37:38] <140310336378752> lpbcore|     System information:
[18.01.2018 15:37:38] <140310336378752> lpbcore|       Running [lsb_release -a].
[18.01.2018 15:37:38] <140310336378752> lpbcore|         Distributor ID:Debian
[18.01.2018 15:37:38] <140310336378752> lpbcore|         Description:Debian GNU/Linux 8.10 (jessie)
[18.01.2018 15:37:38] <140310336378752> lpbcore|         Release:8.10
[18.01.2018 15:37:38] <140310336378752> lpbcore|         Codename:jessie
[18.01.2018 15:37:38] <140310336378752> lpbcore|       Running [cat /etc/*release].
[18.01.2018 15:37:38] <140310336378752> lpbcore|         PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
[18.01.2018 15:37:38] <140310336378752> lpbcore|         NAME="Debian GNU/Linux"
[18.01.2018 15:37:38] <140310336378752> lpbcore|         VERSION_ID="8"
[18.01.2018 15:37:38] <140310336378752> lpbcore|         VERSION="8 (jessie)"
[18.01.2018 15:37:38] <140310336378752> lpbcore|         ID=debian
[18.01.2018 15:37:38] <140310336378752> lpbcore|         HOME_URL="http://www.debian.org/"
[18.01.2018 15:37:38] <140310336378752> lpbcore|         SUPPORT_URL="http://www.debian.org/support"
[18.01.2018 15:37:38] <140310336378752> lpbcore|         BUG_REPORT_URL="https://bugs.debian.org/"
[18.01.2018 15:37:38] <140310336378752> lpbcore|       Running [lsblk].
[18.01.2018 15:37:38] <140310336378752> lpbcore|         NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
[18.01.2018 15:37:38] <140310336378752> lpbcore|         sda      8:0    0  100G  0 disk 
[18.01.2018 15:37:38] <140310336378752> lpbcore|         ├─sda1   8:1    0 95,9G  0 part /
[18.01.2018 15:37:38] <140310336378752> lpbcore|         ├─sda2   8:2    0    1K  0 part 
[18.01.2018 15:37:38] <140310336378752> lpbcore|         └─sda5   8:5    0  4,1G  0 part [SWAP]
[18.01.2018 15:37:38] <140310336378752> lpbcore|         sr0     11:0    1 1024M  0 rom  
[18.01.2018 15:37:38] <140310336378752> lpbcore|   LpbManSession: Starting backup job. ok.
[18.01.2018 15:37:38] <140310290929408>        | Thread started. Thread id: 140310290929408, parent id: 140310336378752, role: Volume backup job execution
[18.01.2018 15:37:38] <140310290929408> lpbcore| BackupJobPerformer: Creating backup.
[18.01.2018 15:37:38] <140310290929408> lpbcore|   Job information:
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Job name: [FULLBACKUP]. ID: [{4985d60e-d64b-44ff-9748-7c0ea8177a70}].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Job source:
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Included [All System]  .
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Job destination:
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Target repository [Repository_1] ID [{cfbed8be-6b11-498c-8bc8-756c641c237a}].
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Shared folder repository address: [192.168.123.123/backup].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Job options:
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Compression: [Lz4]
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Block size: [KbBlockSize1024]
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Retention max points: [7].
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Pre-freeze: []
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Post-thaw: []
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Pre-job: []
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Post-job: []
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Retry count: [0]
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Retry delay (ms): [600000]
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Indexing: File system indexing is disabled.
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Schedule: enabled daily at 6:0, days of week: sun,mon,tue,wed,thu,fri,sat.
[18.01.2018 15:37:38] <140310290929408> lpbcore|   Creating repository database accessor for local database.
[18.01.2018 15:37:38] <140310290929408> vmb    |   [SessionLog][info] Preparing to backup.
[18.01.2018 15:37:38] <140310290929408> lpbcore|   Creating new backup.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Resetting jobId for other backups produced by this job.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Creating directory [/tmp/veeam/192.168.123.123backup FULLBACKUP/].
[18.01.2018 15:37:38] <140310290929408> lpbcore|   New backup entry created, in repository path: [web FULLBACKUP].
[18.01.2018 15:37:38] <140310290929408> lpbcore|   Enumerating backup objects.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Creating job objects filter.
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Record type: [Include], object type: [AllSystem], value: []
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Creating job objects filter. ok.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys]. Device number: [0:14].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/proc]. Device number: [0:3].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/dev]. Device number: [0:5].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/dev/pts]. Device number: [0:11].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/run]. Device number: [0:15].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/]. Device number: [8:1].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/kernel/security]. Device number: [0:16].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/dev/shm]. Device number: [0:17].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/run/lock]. Device number: [0:18].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/fs/cgroup]. Device number: [0:19].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/fs/cgroup/systemd]. Device number: [0:20].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/fs/pstore]. Device number: [0:21].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/fs/cgroup/cpuset]. Device number: [0:22].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/fs/cgroup/cpu,cpuacct]. Device number: [0:23].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/fs/cgroup/devices]. Device number: [0:24].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/fs/cgroup/freezer]. Device number: [0:25].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/fs/cgroup/net_cls,net_prio]. Device number: [0:26].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/fs/cgroup/blkio]. Device number: [0:27].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/fs/cgroup/perf_event]. Device number: [0:28].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/dev/mqueue]. Device number: [0:13].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/dev/hugepages]. Device number: [0:30].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/sys/kernel/debug]. Device number: [0:6].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/run/rpc_pipefs]. Device number: [0:32].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Mount point: [/tmp/veeam/192.168.123.123backup]. Device number: [0:33].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/dvd]. Device number: [11:0].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/cdrw]. Device number: [11:0].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/cdrom]. Device number: [11:0].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/disk/by-uuid/88d31673-9411-4661-81cb-d0ea836d6e28]. Device number: [8:1].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/disk/by-uuid/e86ca11c-f08e-45bf-819c-1df6cb55fcb5]. Device number: [8:5].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/disk/by-id/ata-VMware_Virtual_IDE_CDROM_Drive_10000000000000000001]. Device number: [11:0].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:03:00.0-scsi-0:0:0:0-part1]. Device number: [8:1].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:03:00.0-scsi-0:0:0:0-part5]. Device number: [8:5].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:03:00.0-scsi-0:0:0:0-part2]. Device number: [8:2].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:03:00.0-scsi-0:0:0:0]. Device number: [8:0].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/block/8:1]. Device number: [8:1].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/block/8:5]. Device number: [8:5].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/block/8:2]. Device number: [8:2].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/block/11:0]. Device number: [11:0].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/block/8:0]. Device number: [8:0].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/sr0]. Device number: [11:0].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/sda5]. Device number: [8:5].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/sda2]. Device number: [8:2].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/sda1]. Device number: [8:1].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found device: [/dev/sda]. Device number: [8:0].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found matching filter for object [b55c7483]. Record type: [Include], value: []
[18.01.2018 15:37:38] <140310290929408> lpbcore|     No matching filters for object [b55c7483]
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found matching filter for object [b55c7483/o1048576l102977503232]. Record type: [Include], value: []
[18.01.2018 15:37:38] <140310290929408> lpbcore|     No matching filters for object [b55c7483/o1048576l102977503232]
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Partition [/dev/sda1] should be backed up.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found matching filter for object [b55c7483/o102979599360l4393534464]. Record type: [Include], value: []
[18.01.2018 15:37:38] <140310290929408> lpbcore|     No matching filters for object [b55c7483/o102979599360l4393534464]
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Found matching filter for object [b55c7483/o102979600384l4393533440]. Record type: [Include], value: []
[18.01.2018 15:37:38] <140310290929408> lpbcore|     No matching filters for object [b55c7483/o102979600384l4393533440]
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Partition [/dev/sda5] is swap.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Detecting bootloader on device [/dev/sda].
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Device has MBR partition table.
[18.01.2018 15:37:38] <140310290929408> lpbcore|       MBR gap area size: [1048064].
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Detected GRUB 2 (v1.97-1.99).
[18.01.2018 15:37:38] <140310290929408> lpbcore|     No master boot record found on device.
[18.01.2018 15:37:38] <140310290929408> lpbcore| ERR |No medium found
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |Failed to probe device [/dev/sr0].
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |An exception was thrown from thread [140310290929408].
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Enumerating LVM volume groups...
[18.01.2018 15:37:38] <140310290929408> lpbcore|     [0] LVM volume groups were detected.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     BIOS bootloader on [/dev/sda] will be backed up.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Disk [/dev/sda] will be backed up.
[18.01.2018 15:37:38] <140310290929408> lpbcore|   Computing backup estimated size.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Querying used space on sda.
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Partition sda1, size: 102977503232, used: 55601467392.
[18.01.2018 15:37:38] <140310290929408> lpbcore| WARN|Failed to get used space on device [sda5].
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Partition sda5, size: 4393533440, used: 4393533440.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Used space: 59995000832.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Overall data size used: 59995000832.
[18.01.2018 15:37:38] <140310290929408> lpbcore|   Taking snapshot.
[18.01.2018 15:37:38] <140310290929408> vmb    |     [SessionLog][processing] Creating volume snapshot.
[18.01.2018 15:37:38] <140310290929408> lpbcore|     Adding disk backup object into snapshot set. Disk: [sda].
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Request to snapshot device: [8:1].
[18.01.2018 15:37:38] <140310290929408> lpbcore|       Request to stop tracking device: [8:0].
[18.01.2018 15:37:38] <140310290929408> lpbcore| WARN|Method invocation was not finalized. Method id [1]. Class: [lpbcorelib::interaction::ISnapshotOperation]
[18.01.2018 15:37:38] <140310290929408> lpbcore| ERR |Child execution has failed. Exit code: [1].
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |--tr:Failed to execute [modprobe].
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |--tr:Failed to finish snapshot creation process.
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |--tr:Failed to execute method [1] for class [lpbcorelib::interaction::proxystub::CSnapshotOperationStub].
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |--tr:Failed to invoke method [1] in class [lpbcorelib::interaction::ISnapshotOperation].
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |An exception was thrown from thread [140310290929408].
[18.01.2018 15:37:38] <140310290929408> lpbcore| ERR |Failed to execute thaw script with status: fail.
[18.01.2018 15:37:38] <140310290929408> vmb    |     [SessionLog][error] Failed to create volume snapshot.
[18.01.2018 15:37:38] <140310290929408> lpbcore|   Taking snapshot. Failed.
[18.01.2018 15:37:38] <140310290929408> lpbcore| BackupJobPerformer: Creating backup. Failed.
[18.01.2018 15:37:38] <140310290929408> vmb    | [SessionLog][error] Failed to perform backup.
[18.01.2018 15:37:38] <140310290929408> vmb    | [SessionLog][error] Child execution has failed. Exit code: [1].
[18.01.2018 15:37:38] <140310290929408> vmb    | [SessionLog][error] Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].
[18.01.2018 15:37:38] <140310290929408> vmb    | [SessionLog][error] Processing finished with errors at 2018-01-18 15:37:38 CET.
[18.01.2018 15:37:38] <140310290929408> lpbcore| ERR |Child execution has failed. Exit code: [1].
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |--tr:Failed to execute [modprobe].
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |--tr:Failed to finish snapshot creation process.
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |--tr:Failed to execute method [1] for class [lpbcorelib::interaction::proxystub::CSnapshotOperationStub].
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |--tr:Failed to create volume snapshot.
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |Backup job has failed.
[18.01.2018 15:37:38] <140310290929408> lpbcore| >>  |An exception was thrown from thread [140310290929408].
[18.01.2018 15:37:38] <140310336378752>        |   Closing socket device.
[18.01.2018 15:37:38] <140310336378752> lpbcore| LpbManSession: Processing commands. ok.
[18.01.2018 15:37:38] <140310336378752>        | Closing socket device.
[18.01.2018 15:37:38] <140310290929408> lpbcore| JOB STATUS: FAILED.
[18.01.2018 15:37:38] <140310290929408>        | Thread finished. Role: 'Volume backup job execution'.
[18.01.2018 15:37:38] <140310336378752>        | Closing socket device.
[18.01.2018 15:37:38] <140310336378752>        | Closing socket device.
[18.01.2018 15:37:38] <140310336378752> lpbman | Application session has been finished.
Thanks a lot for your help :).

vmniels
Veeam Software
Posts: 2016
Liked: 443 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: Backup Failed (failed to create snapshot)

Post by vmniels » Jan 19, 2018 11:03 am

Hi, you are missing the kernel headers and therefor veeamsnap isn't installed/loaded. You should install these first via "apt-get install linux-headers-$(uname -r)" and afterwards re-install the veeam packages.
VCP-DCV
Veeam Certified Architect (VMCA)
http://foonet.be

pleibling
Novice
Posts: 5
Liked: never
Joined: Dec 17, 2015 7:51 pm

Re: Backup Failed (failed to create snapshot)

Post by pleibling » Jan 19, 2018 3:17 pm

Thanks a lot for your fast replay, this solves my Problem.

You make my Day vmniels :).

---
Pingback: https://www.leibling.de/2018/01/19/esxi ... -snapshot/

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests