Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
Post Reply
Iain_Green
Service Provider
Posts: 158
Liked: 9 times
Joined: Dec 05, 2014 2:13 pm
Full Name: Iain Green
Contact:
Contact Iain_Green

Failed to backup

Post by Iain_Green »

Not a linux expert in the slightest but have been asked to test the new veeam agent.
managed to install it thanks to some assistance from a colleague with more experience than I.

However every time i run the job it fails immediately. Below is out put from the log file I found.

Code: Select all

[13.01.2017 14:33:00] <140440828180224> net    |   Accepted incoming vRPC connection from '127.0.0.1:46684'.
[13.01.2017 14:33:00] <140440701486848>        | Thread started. Thread id: 140440701486848, parent id: 140440828180224, role: Client processor thread (127.0.0.1:46684)
[13.01.2017 14:33:00] <140440701486848> net    | Client connected...
[13.01.2017 14:33:00] <140440701486848> net    | Received reconnect options: [disabled].
[13.01.2017 14:33:00] <140440690996992>        | Thread started. Thread id: 140440690996992, parent id: 140440701486848, role: peer 127.0.0.1:46684
[13.01.2017 14:33:00] <140440701486848>        | Thread finished. Role: 'Client processor thread (127.0.0.1:46684)'.
[13.01.2017 14:33:00] <140440690996992> lpbcore| Starting proxystub protocol dispatch loop.
[13.01.2017 14:33:00] <140440828180224> net    |   Accepted incoming vRPC connection from '127.0.0.1:46685'.
[13.01.2017 14:33:00] <140440432469760>        | Thread started. Thread id: 140440432469760, parent id: 140440828180224, role: Client processor thread (127.0.0.1:46685)
[13.01.2017 14:33:00] <140440432469760> net    | Client connected...
[13.01.2017 14:33:00] <140440432469760> net    | Received reconnect options: [disabled].
[13.01.2017 14:33:00] <140440432469760> lpbcore| Starting new LPB session.
[13.01.2017 14:33:00] <140440432469760>        |   Closing socket device.
[13.01.2017 14:33:00] <140440432469760> lpbcore| Starting new LPB session. ok.
[13.01.2017 14:33:00] <140440432469760>        | Thread finished. Role: 'Client processor thread (127.0.0.1:46685)'.
[13.01.2017 14:33:00] <140440701486848>        | Thread started. Thread id: 140440701486848, parent id: 140440432469760, role: (async) LPBConfig session (127.0.0.1:46685)
[13.01.2017 14:33:00] <140440701486848> lpbcore| LpbCfgSession: Tcp loop.
[13.01.2017 14:33:07] <140440690996992> lpbcore|   Job execution service: starting worker (manager) process.
[13.01.2017 14:33:07] <140440690996992> lpbcore|     Starting manager process. Session UUID: [{37761cdf-16a8-428d-8e30-5d45cfa44ede}]. Logs path: [/var/log/veeam/Backup/Centos6_test/Session_20170113_143307_{37761cdf-16a8-428d-8e30-5d45cfa44ede}/Job.log]
[13.01.2017 14:33:07] <140440690996992> lpbcore|     JobMan has started. PID: [4193].
[13.01.2017 14:33:07] <140440690996992> lpbcore|     Manager started with PID [4193]. Waiting connection.
[13.01.2017 14:33:07] <140440432469760>        | Thread started. Thread id: 140440432469760, parent id: 140440690996992, role: Manager process [4193] shutdown handler.
[13.01.2017 14:33:07] <140440828180224> net    |   Accepted incoming vRPC connection from '127.0.0.1:46686'.
[13.01.2017 14:33:07] <140440817690368>        | Thread started. Thread id: 140440817690368, parent id: 140440828180224, role: Client processor thread (127.0.0.1:46686)
[13.01.2017 14:33:07] <140440817690368> net    | Client connected...
[13.01.2017 14:33:07] <140440817690368> net    | Received reconnect options: [disabled].
[13.01.2017 14:33:07] <140440732956416>        | Thread started. Thread id: 140440732956416, parent id: 140440817690368, role: peer 127.0.0.1:46686
[13.01.2017 14:33:07] <140440817690368>        | Thread finished. Role: 'Client processor thread (127.0.0.1:46686)'.
[13.01.2017 14:33:07] <140440732956416> lpbcore| Starting proxystub protocol dispatch loop.
[13.01.2017 14:33:07] <140440828180224> net    |   Accepted incoming vRPC connection from '127.0.0.1:46687'.
[13.01.2017 14:33:07] <140440680507136>        | Thread started. Thread id: 140440680507136, parent id: 140440828180224, role: Client processor thread (127.0.0.1:46687)
[13.01.2017 14:33:07] <140440680507136> net    | Client connected...
[13.01.2017 14:33:07] <140440680507136> net    | Received reconnect options: [disabled].
[13.01.2017 14:33:07] <140440680507136>        | Thread finished. Role: 'Client processor thread (127.0.0.1:46687)'.
[13.01.2017 14:33:07] <140440817690368>        | Thread started. Thread id: 140440817690368, parent id: 140440690996992, role: backup job retry handler
[13.01.2017 14:33:07] <140440817690368> lpbcore| Sending command [StartBackupJob] to manager with PID [4193]. Job ID: [{2790a668-4cd3-47d5-83af-fa718d08b720}]. Is high priority job: [false].
[13.01.2017 14:33:07] <140440732956416>        |   Trying to connect to the endpoint [10.0.13.59:10002]
[13.01.2017 14:33:07] <140440732956416>        |   Connection status: system:0 ( Success ).
[13.01.2017 14:33:07] <140440421979904> cli    | Thread [Establish connect to Vbr: 10.0.13.59:10002.].
[13.01.2017 14:33:07] <140440421979904> lpbcore|   Try Authenticate to backup server
[13.01.2017 14:33:07] <140440421979904> lpbcore|     Server negotiate flags: 0xe2898235. Windows version: 6.3.9600.15
[13.01.2017 14:33:07] <140440421979904> lpbcore|   Authenticated via NTLMV2.
[13.01.2017 14:33:07] <140440421979904> lpbcore|   Connected to VBR[POC-WIN12-VEEAM] version:[9.5.0.802]
[13.01.2017 14:33:07] <140440421979904> lpbcore|   VBRClient: Save license info.
[13.01.2017 14:33:07] <140440421979904> lpbcore|     Vbr UUID: [{948b083a-3014-4651-8010-3c2451024730}].
[13.01.2017 14:33:07] <140440421979904> lpbcore|     Is licensed? [true].
[13.01.2017 14:33:07] <140440421979904> lpbcore|     License mode: [Free].
[13.01.2017 14:33:07] <140440421979904> lpbcore|     Grace date: [2017-01-27 14:32:31] (1485527551).
[13.01.2017 14:33:07] <140440421979904> lpbcore|     Exp date: [9999-12-31 23:59:59] (253402300799).
[13.01.2017 14:33:07] <140440421979904> lpbcore|   VBRClient: Save license info. ok.
[13.01.2017 14:33:07] <140440421979904> cli    | Thread [Establish connect to Vbr: 10.0.13.59:10002.]. ok.
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Snapshot service: creating snapshot.
[13.01.2017 14:33:18] <140440732956416> lpbcore| WARN|Mount point [/dev] of device [devtmpfs] is already assigned to the device [devtmpfs].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Mount point: [/proc]. Device number: [0:3].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Mount point: [/sys]. Device number: [0:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Mount point: [/dev]. Device number: [0:5].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Mount point: [/dev/pts]. Device number: [0:11].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Mount point: [/dev/shm]. Device number: [0:15].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Mount point: [/]. Device number: [253:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Mount point: [/selinux]. Device number: [0:14].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Mount point: [/proc/bus/usb]. Device number: [0:16].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Mount point: [/boot]. Device number: [8:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Mount point: [/proc/sys/fs/binfmt_misc]. Device number: [0:17].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram9]. Device number: [1:9].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram8]. Device number: [1:8].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram7]. Device number: [1:7].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram6]. Device number: [1:6].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram5]. Device number: [1:5].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram4]. Device number: [1:4].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram3]. Device number: [1:3].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram2]. Device number: [1:2].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram15]. Device number: [1:15].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram1]. Device number: [1:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram13]. Device number: [1:13].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram14]. Device number: [1:14].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram11]. Device number: [1:11].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram12]. Device number: [1:12].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram0]. Device number: [1:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/ram10]. Device number: [1:10].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/dvdrw]. Device number: [11:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/dvd]. Device number: [11:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/cdrw]. Device number: [11:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/cdrom]. Device number: [11:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/root]. Device number: [253:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/vg_root/lv_swap]. Device number: [253:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/vg_root/lv_root]. Device number: [253:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/dm-1]. Device number: [253:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/dm-0]. Device number: [253:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-id/lvm-pv-uuid-ehGwbd-ZwKK-ZCx9-t133-E3YL-hGl4-7f364K]. Device number: [8:2].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-id/dm-uuid-LVM-fAlGk2VfYIltE7EYy8rcTM1xtLKLVUXr7JeLuda3t2lzt04oKPkcA38LR5etMVhD]. Device number: [253:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-id/dm-name-vg_root-lv_swap]. Device number: [253:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-id/dm-uuid-LVM-fAlGk2VfYIltE7EYy8rcTM1xtLKLVUXrFZMdAHy3sEJBebQjwSQEWD19anVJrqgO]. Device number: [253:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-id/dm-name-vg_root-lv_root]. Device number: [253:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-uuid/8b9fb018-d41d-4b2a-8e0b-1782099c9fa1]. Device number: [253:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-uuid/50b6b3bf-6423-4062-aae4-483668401936]. Device number: [253:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-uuid/dac78075-a0f5-463c-93d5-e182ef78ef06]. Device number: [8:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-path/pci-0000:03:00.0-scsi-0:0:0:0-part2]. Device number: [8:2].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-path/pci-0000:03:00.0-scsi-0:0:0:0-part1]. Device number: [8:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-path/pci-0000:03:00.0-scsi-0:0:0:0]. Device number: [8:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/disk/by-path/pci-0000:00:07.1-scsi-1:0:0:0]. Device number: [11:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/scd0]. Device number: [11:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/sr0]. Device number: [11:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/sda2]. Device number: [8:2].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/sda1]. Device number: [8:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/sda]. Device number: [8:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:9]. Device number: [1:9].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:8]. Device number: [1:8].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:7]. Device number: [1:7].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:6]. Device number: [1:6].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:5]. Device number: [1:5].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:4]. Device number: [1:4].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:3]. Device number: [1:3].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:2]. Device number: [1:2].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:15]. Device number: [1:15].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:1]. Device number: [1:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:13]. Device number: [1:13].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:14]. Device number: [1:14].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:11]. Device number: [1:11].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:12]. Device number: [1:12].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:0]. Device number: [1:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/1:10]. Device number: [1:10].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/253:1]. Device number: [253:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/253:0]. Device number: [253:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/8:2]. Device number: [8:2].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/8:1]. Device number: [8:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/8:0]. Device number: [8:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/11:0]. Device number: [11:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/7:7]. Device number: [7:7].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/7:6]. Device number: [7:6].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/7:5]. Device number: [7:5].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/7:4]. Device number: [7:4].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/7:0]. Device number: [7:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/7:3]. Device number: [7:3].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/7:2]. Device number: [7:2].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/block/7:1]. Device number: [7:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/mapper/vg_root-lv_swap]. Device number: [253:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/mapper/vg_root-lv_root]. Device number: [253:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/loop7]. Device number: [7:7].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/loop6]. Device number: [7:6].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/loop5]. Device number: [7:5].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/loop4]. Device number: [7:4].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/loop3]. Device number: [7:3].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/loop2]. Device number: [7:2].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/loop1]. Device number: [7:1].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Found device: [/dev/loop0]. Device number: [7:0].
[13.01.2017 14:33:18] <140440732956416> lpbcore| ERR |No medium found
[13.01.2017 14:33:18] <140440732956416> lpbcore| >>  |Failed to probe device [/dev/sr0].
[13.01.2017 14:33:18] <140440732956416> lpbcore| >>  |An exception was thrown from thread [140440732956416].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   Enumerating LVM volume groups...
[13.01.2017 14:33:18] <140440732956416> lpbcore|     LVM volume group: [vg_root].
[13.01.2017 14:33:18] <140440732956416> lpbcore|     Enumerating logical volumes for LVM volume group: [vg_root].
[13.01.2017 14:33:18] <140440732956416> lpbcore|   [1] LVM volume groups were detected.
[13.01.2017 14:33:18] <140440732956416> lpbcore| WARN|Snapshot storage type by default is stretch.
[13.01.2017 14:33:18] <140440732956416> vsnap  |   Checking whether veeamsnap kernel module is loaded.
[13.01.2017 14:33:18] <140440732956416> vsnap  |   Module is not loaded.
[13.01.2017 14:33:18] <140440732956416> vsnap  |   Loading kernel module veeamsnap with parameters [zerosnapdata=1 debuglogging=0].
[13.01.2017 14:33:18] <140440732956416>        |     Argument [modprobe].
[13.01.2017 14:33:18] <140440732956416>        |     Argument [veeamsnap].
[13.01.2017 14:33:18] <140440732956416>        |     Argument [zerosnapdata=1].
[13.01.2017 14:33:18] <140440732956416>        |     Argument [debuglogging=0].
[13.01.2017 14:33:18] <140440732956416> vsnap  |   Loading kernel module veeamsnap with parameters [zerosnapdata=1 debuglogging=0]. Failed.
[13.01.2017 14:33:18] <140440732956416> vsnap  |   Opening VeeamSnap control.
[13.01.2017 14:33:18] <140440732956416> vsnap  |   Closing VeeamSnap control.
[13.01.2017 14:33:18] <140440732956416> vsnap  |   Closing VeeamSnap control. ok.
[13.01.2017 14:33:18] <140440732956416> lpbcore| ERR |Child execution has failed. Exit code: [1].
[13.01.2017 14:33:18] <140440732956416> lpbcore| >>  |--tr:Failed to execute [modprobe].
[13.01.2017 14:33:18] <140440732956416> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].
[13.01.2017 14:33:18] <140440732956416> lpbcore| >>  |--tr:Unable to create snapshot.
[13.01.2017 14:33:18] <140440732956416> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub21CResourcesServiceStubE].
[13.01.2017 14:33:18] <140440732956416> lpbcore| >>  |An exception was thrown from thread [140440732956416].
[13.01.2017 14:33:20] <140440732956416>        |   Closing socket device.
[13.01.2017 14:33:20] <140440732956416> lpbcore| Starting proxystub protocol dispatch loop. ok.
[13.01.2017 14:33:20] <140440732956416>        | Closing socket device.
[13.01.2017 14:33:20] <140440732956416>        | Thread finished. Role: 'peer 127.0.0.1:46686'.
[13.01.2017 14:33:20] <140440432469760> lpbcore| Manager process [4193] has been shutdown.
[13.01.2017 14:33:20] <140440432469760>        | Thread finished. Role: 'Manager process [4193] shutdown handler.'.
[13.01.2017 14:33:20] <140440722466560> lpbcore| Cleaning up resources for job process [4193].
[13.01.2017 14:33:20] <140440817690368> lpbcore| ERR |Backup job has failed.
[13.01.2017 14:33:20] <140440817690368> lpbcore| >>  |Child execution has failed. Exit code: [1].
[13.01.2017 14:33:20] <140440817690368> lpbcore| >>  |--tr:Failed to execute [modprobe].
[13.01.2017 14:33:20] <140440817690368> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].
[13.01.2017 14:33:20] <140440817690368> lpbcore| >>  |--tr:Unable to create snapshot.
[13.01.2017 14:33:20] <140440817690368> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub21CResourcesServiceStubE].
[13.01.2017 14:33:20] <140440817690368> lpbcore| >>  |--tr:Failed to create volume snapshot.
[13.01.2017 14:33:20] <140440817690368> lpbcore| >>  |Backup job has failed.
[13.01.2017 14:33:20] <140440817690368> lpbcore| >>  |An exception was thrown from thread [140440732956416].
[13.01.2017 14:33:20] <140440817690368> lpbcore| Retry is disabled. Attempts counter '3', isRetriable flag 'false'.
[13.01.2017 14:33:20] <140440817690368>        | Thread finished. Role: 'backup job retry handler'.
[13.01.2017 14:33:20] <140440711976704>        | Closing socket device.
[13.01.2017 14:37:39] <140440690996992> lpbcore| Starting proxystub protocol dispatch loop. ok.
[13.01.2017 14:37:39] <140440690996992>        | Closing socket device.
[13.01.2017 14:37:39] <140440690996992>        | Thread finished. Role: 'peer 127.0.0.1:46684'.
[13.01.2017 14:37:39] <140440701486848> lpbcore| LpbCfgSession: Tcp loop. Failed.
[13.01.2017 14:37:39] <140440701486848> lpbcore| ERR |LpbCfgSession failed.
[13.01.2017 14:37:39] <140440701486848> lpbcore| >>  |read: End of file
[13.01.2017 14:37:39] <140440701486848> lpbcore| >>  |--tr:Cannot read data from the socket. Requested data size: [4].
[13.01.2017 14:37:39] <140440701486848> lpbcore| >>  |An exception was thrown from thread [140440701486848].
[13.01.2017 14:37:39] <140440701486848>        | Closing socket device.
[13.01.2017 14:37:39] <140440701486848>        | Thread finished. Role: '(async) LPBConfig session (127.0.0.1:46685)'.

Are you able to provide any pointers as to where my installation appears to have failed?
Many thanks

Iain Green
Top
nielsengelen
Product Manager
Posts: 5797
Liked: 1215 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:
Contact nielsengelen

Re: Failed to backup

Post by nielsengelen »

Did the installation go correctly? It looks like the veeamsnap module isn't loaded.

What do you get if you do "lsmod | grep veeam" or "modprobe veeamsnap" manually?

Also which distro are you using?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
Top
Iain_Green
Service Provider
Posts: 158
Liked: 9 times
Joined: Dec 05, 2014 2:13 pm
Full Name: Iain Green
Contact:
Contact Iain_Green

Re: Failed to backup

Post by Iain_Green »

Looks like it's missing as both commands come back as:

Code: Select all

grep: veeamsnap: No such file or directory
Many thanks

Iain Green
Top
Iain_Green
Service Provider
Posts: 158
Liked: 9 times
Joined: Dec 05, 2014 2:13 pm
Full Name: Iain Green
Contact:
Contact Iain_Green

Re: Failed to backup

Post by Iain_Green »

If I reinstall I get the following:

Code: Select all

root@generic-centos6 tmp]# yum install veeamsnap
Loaded plugins: fastestmirror, security
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: mirror.as29550.net
 * epel: epel.besthosting.ua
 * extras: anorien.csc.warwick.ac.uk
 * updates: anorien.csc.warwick.ac.uk
Package veeamsnap-1.0.0.944-1.noarch already installed and latest version
Nothing to do
Many thanks

Iain Green
Top
nielsengelen
Product Manager
Posts: 5797
Liked: 1215 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:
Contact nielsengelen

Re: Failed to backup

Post by nielsengelen »

Could you try to reinstall the whole package? I guess you are missing some files that can be loaded.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
Top
Iain_Green
Service Provider
Posts: 158
Liked: 9 times
Joined: Dec 05, 2014 2:13 pm
Full Name: Iain Green
Contact:
Contact Iain_Green

Re: Failed to backup

Post by Iain_Green »

I have installed the veeam again and tried again:

Code: Select all

[root@generic-centos6 ~]# yum install veeam
Loaded plugins: fastestmirror, security
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: mirror.as29550.net
 * epel: epel.besthosting.ua
 * extras: anorien.csc.warwick.ac.uk
 * updates: anorien.csc.warwick.ac.uk
Package veeam-1.0.0.944-1.el6.x86_64 already installed and latest version
Nothing to do
However still fails

Code: Select all

 Time            Action                                                                                                                                                                                                 Duration

      16:19:53        Job Centos6_test started at 2017-01-13 16:19:53 GMT
      16:19:54        Waiting for backup infrastructure resources availability                                                                                                                                               00:00:10
      16:20:04        Preparing to backup
      16:20:04        [error] Failed to create volume snapshot                                                                                                                                                               00:00:00
      16:20:04        [error] Failed to perform backup
      16:20:04        [error] Child execution has failed. Exit code: [1]
      16:20:04        [error] Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0]
Many thanks

Iain Green
Top
PTide
Product Manager
Posts: 6551
Liked: 765 times
Joined: May 19, 2015 1:46 pm
Contact:
Contact PTide

Re: Failed to backup

Post by PTide »

Hi,

Please contact support team directly, so they can investigate your case thoroughly, and post your case ID.

Thank you
Top
Post Reply

Return to “Veeam Agents for Linux, Mac, AIX & Solaris”



Who is online

Users browsing this forum: No registered users and 6 guests