Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
Post Reply
stevenfoo
Expert
Posts: 116
Liked: 3 times
Joined: Jun 26, 2009 3:11 am
Full Name: Steven Foo
Contact:

Failed to load module [veeamsnap] with parameters [zerosnapd

Post by stevenfoo »

Hi,

I have install the veeam 64 bit version into one of our linux server and I am testing to backup.

However I am getting the following error in the log file. Any idea to fixed that?

[10.02.2017 11:12:23] <140418135193344> lpbcore| >> |--tr:Failed to execute [modprobe].
[10.02.2017 11:12:23] <140418135193344> lpbcore| >> |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].
[10.02.2017 11:12:23] <140418135193344> lpbcore| >> |--tr:Unable to create snapshot.
[10.02.2017 11:12:23] <140418135193344> lpbcore| >> |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub21CResourcesServiceStubE].
[10.02.2017 11:12:23] <140418135193344> lpbcore| >> |--tr:Failed to create volume snapshot.
Mike Resseler
Product Manager
Posts: 8044
Liked: 1263 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by Mike Resseler »

Hi Steven,

It looks like something went wrong with the installation. Can you perform this command and let us know the output?

lsmod | grep veeam (or modprobe veeamsnap)

Thanks
Mike
stevenfoo
Expert
Posts: 116
Liked: 3 times
Joined: Jun 26, 2009 3:11 am
Full Name: Steven Foo
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by stevenfoo » 1 person likes this post

Issue resolved. Uninstall everything and reinstall again.
Mike Resseler
Product Manager
Posts: 8044
Liked: 1263 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by Mike Resseler »

Good to know. Thanks for letting us know

Cheers
Mike
stevenfoo
Expert
Posts: 116
Liked: 3 times
Joined: Jun 26, 2009 3:11 am
Full Name: Steven Foo
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by stevenfoo »

I have another server which I have install the veeam 64 bit agent. When I start veeam and configure it. It works fine.

However when I start the backup the error appears. Any ideas? I have already uninstall and reinstall the veeam.

The OS level is CentOS 6.8 64 bit.

09:24:32 Job PENFTP started at 2017-02-16 09:24:32 MYT
09:24:32 Preparing to backup
09:24:32 [error] Failed to create volume snapshot 00:00:01
09:24:33 [error] Failed to perform backup
09:24:33 [error] Child execution has failed. Exit code: [1]
09:24:33 [error] Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0]

Below is the detail information from job log:

Code: Select all

[16.02.2017 09:24:32] <139880717100896> cli    | Initializing new log filter.
[16.02.2017 09:24:32] <139880717100896>        | ====================================================================================
[16.02.2017 09:24:32] <139880717100896> lpb    | {
[16.02.2017 09:24:32] <139880717100896> lpb    |   Veeam Agent for Linux: veeamjobman.
[16.02.2017 09:24:32] <139880717100896> lpb    |   Version: 1.0.0.944
[16.02.2017 09:24:32] <139880717100896> lpb    |   PID: 4870
[16.02.2017 09:24:32] <139880717100896> lpb    |   uname
[16.02.2017 09:24:32] <139880717100896> lpb    |     sysname : Linux
[16.02.2017 09:24:32] <139880717100896> lpb    |     release : 2.6.32-642.6.2.el6.x86_64
[16.02.2017 09:24:32] <139880717100896> lpb    |     version : #1 SMP Wed Oct 26 06:52:09 UTC 2016
[16.02.2017 09:24:32] <139880717100896> lpb    |     machine : x86_64
[16.02.2017 09:24:32] <139880717100896> lpb    |   cpuinfo
[16.02.2017 09:24:32] <139880717100896> lpb    |     processor: 0
[16.02.2017 09:24:32] <139880717100896> lpb    |     vendor_id: GenuineIntel
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu family: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     model: 23
[16.02.2017 09:24:32] <139880717100896> lpb    |     model name: Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
[16.02.2017 09:24:32] <139880717100896> lpb    |     stepping: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     microcode: 1551
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu MHz: 1995.034
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache size: 6144 KB
[16.02.2017 09:24:32] <139880717100896> lpb    |     physical id: 0
[16.02.2017 09:24:32] <139880717100896> lpb    |     siblings: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     core id: 0
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu cores: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     apicid: 0
[16.02.2017 09:24:32] <139880717100896> lpb    |     initial apicid: 0
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu_exception: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpuid level: 10
[16.02.2017 09:24:32] <139880717100896> lpb    |     wp: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dtherm tpr_shadow vnmi flexpriority
[16.02.2017 09:24:32] <139880717100896> lpb    |     bogomips: 3990.06
[16.02.2017 09:24:32] <139880717100896> lpb    |     clflush size: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache_alignment: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     address sizes: 38 bits physical, 48 bits virtual
[16.02.2017 09:24:32] <139880717100896> lpb    |     power management:
[16.02.2017 09:24:32] <139880717100896> lpb    |     processor: 1
[16.02.2017 09:24:32] <139880717100896> lpb    |     vendor_id: GenuineIntel
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu family: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     model: 23
[16.02.2017 09:24:32] <139880717100896> lpb    |     model name: Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
[16.02.2017 09:24:32] <139880717100896> lpb    |     stepping: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     microcode: 1551
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu MHz: 1995.034
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache size: 6144 KB
[16.02.2017 09:24:32] <139880717100896> lpb    |     physical id: 1
[16.02.2017 09:24:32] <139880717100896> lpb    |     siblings: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     core id: 0
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu cores: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     apicid: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     initial apicid: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu_exception: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpuid level: 10
[16.02.2017 09:24:32] <139880717100896> lpb    |     wp: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dtherm tpr_shadow vnmi flexpriority
[16.02.2017 09:24:32] <139880717100896> lpb    |     bogomips: 3990.03
[16.02.2017 09:24:32] <139880717100896> lpb    |     clflush size: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache_alignment: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     address sizes: 38 bits physical, 48 bits virtual
[16.02.2017 09:24:32] <139880717100896> lpb    |     power management:
[16.02.2017 09:24:32] <139880717100896> lpb    |     processor: 2
[16.02.2017 09:24:32] <139880717100896> lpb    |     vendor_id: GenuineIntel
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu family: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     model: 23
[16.02.2017 09:24:32] <139880717100896> lpb    |     model name: Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
[16.02.2017 09:24:32] <139880717100896> lpb    |     stepping: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     microcode: 1551
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu MHz: 1995.034
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache size: 6144 KB
[16.02.2017 09:24:32] <139880717100896> lpb    |     physical id: 0
[16.02.2017 09:24:32] <139880717100896> lpb    |     siblings: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     core id: 2
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu cores: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     apicid: 2
[16.02.2017 09:24:32] <139880717100896> lpb    |     initial apicid: 2
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu_exception: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpuid level: 10
[16.02.2017 09:24:32] <139880717100896> lpb    |     wp: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dtherm tpr_shadow vnmi flexpriority
[16.02.2017 09:24:32] <139880717100896> lpb    |     bogomips: 3990.06
[16.02.2017 09:24:32] <139880717100896> lpb    |     clflush size: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache_alignment: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     address sizes: 38 bits physical, 48 bits virtual
[16.02.2017 09:24:32] <139880717100896> lpb    |     power management:
[16.02.2017 09:24:32] <139880717100896> lpb    |     processor: 3
[16.02.2017 09:24:32] <139880717100896> lpb    |     vendor_id: GenuineIntel
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu family: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     model: 23
[16.02.2017 09:24:32] <139880717100896> lpb    |     model name: Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
[16.02.2017 09:24:32] <139880717100896> lpb    |     stepping: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     microcode: 1551
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu MHz: 1995.034
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache size: 6144 KB
[16.02.2017 09:24:32] <139880717100896> lpb    |     physical id: 1
[16.02.2017 09:24:32] <139880717100896> lpb    |     siblings: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     core id: 2
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu cores: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     apicid: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     initial apicid: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu_exception: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpuid level: 10
[16.02.2017 09:24:32] <139880717100896> lpb    |     wp: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dtherm tpr_shadow vnmi flexpriority
[16.02.2017 09:24:32] <139880717100896> lpb    |     bogomips: 3990.03
[16.02.2017 09:24:32] <139880717100896> lpb    |     clflush size: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache_alignment: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     address sizes: 38 bits physical, 48 bits virtual
[16.02.2017 09:24:32] <139880717100896> lpb    |     power management:
[16.02.2017 09:24:32] <139880717100896> lpb    |     processor: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     vendor_id: GenuineIntel
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu family: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     model: 23
[16.02.2017 09:24:32] <139880717100896> lpb    |     model name: Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
[16.02.2017 09:24:32] <139880717100896> lpb    |     stepping: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     microcode: 1551
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu MHz: 1995.034
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache size: 6144 KB
[16.02.2017 09:24:32] <139880717100896> lpb    |     physical id: 0
[16.02.2017 09:24:32] <139880717100896> lpb    |     siblings: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     core id: 1
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu cores: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     apicid: 1
[16.02.2017 09:24:32] <139880717100896> lpb    |     initial apicid: 1
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu_exception: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpuid level: 10
[16.02.2017 09:24:32] <139880717100896> lpb    |     wp: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dtherm tpr_shadow vnmi flexpriority
[16.02.2017 09:24:32] <139880717100896> lpb    |     bogomips: 3990.06
[16.02.2017 09:24:32] <139880717100896> lpb    |     clflush size: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache_alignment: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     address sizes: 38 bits physical, 48 bits virtual
[16.02.2017 09:24:32] <139880717100896> lpb    |     power management:
[16.02.2017 09:24:32] <139880717100896> lpb    |     processor: 5
[16.02.2017 09:24:32] <139880717100896> lpb    |     vendor_id: GenuineIntel
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu family: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     model: 23
[16.02.2017 09:24:32] <139880717100896> lpb    |     model name: Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
[16.02.2017 09:24:32] <139880717100896> lpb    |     stepping: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     microcode: 1551
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu MHz: 1995.034
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache size: 6144 KB
[16.02.2017 09:24:32] <139880717100896> lpb    |     physical id: 1
[16.02.2017 09:24:32] <139880717100896> lpb    |     siblings: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     core id: 1
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu cores: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     apicid: 5
[16.02.2017 09:24:32] <139880717100896> lpb    |     initial apicid: 5
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu_exception: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpuid level: 10
[16.02.2017 09:24:32] <139880717100896> lpb    |     wp: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dtherm tpr_shadow vnmi flexpriority
[16.02.2017 09:24:32] <139880717100896> lpb    |     bogomips: 3990.03
[16.02.2017 09:24:32] <139880717100896> lpb    |     clflush size: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache_alignment: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     address sizes: 38 bits physical, 48 bits virtual
[16.02.2017 09:24:32] <139880717100896> lpb    |     power management:
[16.02.2017 09:24:32] <139880717100896> lpb    |     processor: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     vendor_id: GenuineIntel
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu family: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     model: 23
[16.02.2017 09:24:32] <139880717100896> lpb    |     model name: Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
[16.02.2017 09:24:32] <139880717100896> lpb    |     stepping: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     microcode: 1551
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu MHz: 1995.034
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache size: 6144 KB
[16.02.2017 09:24:32] <139880717100896> lpb    |     physical id: 0
[16.02.2017 09:24:32] <139880717100896> lpb    |     siblings: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     core id: 3
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu cores: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     apicid: 3
[16.02.2017 09:24:32] <139880717100896> lpb    |     initial apicid: 3
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu_exception: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpuid level: 10
[16.02.2017 09:24:32] <139880717100896> lpb    |     wp: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dtherm tpr_shadow vnmi flexpriority
[16.02.2017 09:24:32] <139880717100896> lpb    |     bogomips: 3990.06
[16.02.2017 09:24:32] <139880717100896> lpb    |     clflush size: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache_alignment: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     address sizes: 38 bits physical, 48 bits virtual
[16.02.2017 09:24:32] <139880717100896> lpb    |     power management:
[16.02.2017 09:24:32] <139880717100896> lpb    |     processor: 7
[16.02.2017 09:24:32] <139880717100896> lpb    |     vendor_id: GenuineIntel
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu family: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     model: 23
[16.02.2017 09:24:32] <139880717100896> lpb    |     model name: Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
[16.02.2017 09:24:32] <139880717100896> lpb    |     stepping: 6
[16.02.2017 09:24:32] <139880717100896> lpb    |     microcode: 1551
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu MHz: 1995.034
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache size: 6144 KB
[16.02.2017 09:24:32] <139880717100896> lpb    |     physical id: 1
[16.02.2017 09:24:32] <139880717100896> lpb    |     siblings: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     core id: 3
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpu cores: 4
[16.02.2017 09:24:32] <139880717100896> lpb    |     apicid: 7
[16.02.2017 09:24:32] <139880717100896> lpb    |     initial apicid: 7
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     fpu_exception: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     cpuid level: 10
[16.02.2017 09:24:32] <139880717100896> lpb    |     wp: yes
[16.02.2017 09:24:32] <139880717100896> lpb    |     flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx tm2 ssse3 cx16 xtpr pdcm dca sse4_1 lahf_lm dtherm tpr_shadow vnmi flexpriority
[16.02.2017 09:24:32] <139880717100896> lpb    |     bogomips: 3990.03
[16.02.2017 09:24:32] <139880717100896> lpb    |     clflush size: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     cache_alignment: 64
[16.02.2017 09:24:32] <139880717100896> lpb    |     address sizes: 38 bits physical, 48 bits virtual
[16.02.2017 09:24:32] <139880717100896> lpb    |     power management:
[16.02.2017 09:24:32] <139880717100896> lpb    |   meminfo
[16.02.2017 09:24:32] <139880717100896> lpb    |     MemTotal:        8053884 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     MemFree:         6429780 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Buffers:           57596 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Cached:          1135860 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     SwapCached:            0 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Active:           755876 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Inactive:         616632 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Active(anon):     179296 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Inactive(anon):     3444 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Active(file):     576580 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Inactive(file):   613188 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Unevictable:           0 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Mlocked:               0 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     SwapTotal:       8191996 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     SwapFree:        8191996 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Dirty:                40 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Writeback:             0 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     AnonPages:        179124 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Mapped:            73996 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Shmem:              3684 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Slab:             126972 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     SReclaimable:      49900 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     SUnreclaim:        77072 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     KernelStack:        6560 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     PageTables:        28492 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     NFS_Unstable:          0 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Bounce:                0 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     WritebackTmp:          0 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     CommitLimit:    12218936 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     Committed_AS:     845660 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     VmallocTotal:   34359738367 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     VmallocUsed:      299136 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     VmallocChunk:   34359407032 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     HardwareCorrupted:     0 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     AnonHugePages:     47104 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     HugePages_Total:       0
[16.02.2017 09:24:32] <139880717100896> lpb    |     HugePages_Free:        0
[16.02.2017 09:24:32] <139880717100896> lpb    |     HugePages_Rsvd:        0
[16.02.2017 09:24:32] <139880717100896> lpb    |     HugePages_Surp:        0
[16.02.2017 09:24:32] <139880717100896> lpb    |     Hugepagesize:       2048 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     DirectMap4k:        7488 kB
[16.02.2017 09:24:32] <139880717100896> lpb    |     DirectMap2M:     8376320 kB
[16.02.2017 09:24:32] <139880717100896> lpb    | }
[16.02.2017 09:24:32] <139880717100896> lpbman | Main thread has started.
[16.02.2017 09:24:32] <139880717100896> lpbcore| Connecting to veeam service...
[16.02.2017 09:24:32] <139880717100896> lpbcore|   Configuration load.
[16.02.2017 09:24:32] <139880717100896> lpbcore|   Configuration load. ok.
[16.02.2017 09:24:32] <139880717100896>        |   Trying to connect to the endpoint [127.0.0.1:3500]
[16.02.2017 09:24:32] <139880717100896>        |   Connection status: system:0 ( Success ).
[16.02.2017 09:24:32] <139880717100896> net    |   Sending reconnect options: [disabled].
[16.02.2017 09:24:32] <139880717100896> lpbcore|   [DEV] Created [0x2e69ab0]
[16.02.2017 09:24:32] <139880717100896> lpbcore| Connecting to veeam service... ok.
[16.02.2017 09:24:32] <139880717100896> lpbcore| LpbManSession: Processing commands.
[16.02.2017 09:24:32] <139880717100896>        |   Trying to connect to the endpoint [127.0.0.1:3500]
[16.02.2017 09:24:32] <139880717100896>        |   Connection status: system:0 ( Success ).
[16.02.2017 09:24:32] <139880717100896> net    |   Sending reconnect options: [disabled].
[16.02.2017 09:24:32] <139880717100896> lpbcore|   Sending PID: [4870].
[16.02.2017 09:24:32] <139880717100896> lpbcore|   Sending Session UUID: [{81660a67-444a-4045-b479-42b3f004ac3d}].
[16.02.2017 09:24:32] <139880717100896> lpbcore|   Waiting for a command.
[16.02.2017 09:24:32] <139880717100896> lpbcore|   LpbManSession: Starting backup job.
[16.02.2017 09:24:32] <139880717100896> lpbcore|     Job UUID: [{741e2657-47b5-4714-9dc7-e0e06af5c61d}] (normal priority).
[16.02.2017 09:24:32] <139880717100896> lpbcore|   LpbManSession: Starting backup job. ok.
[16.02.2017 09:24:32] <139880717092608>        | Thread started. Thread id: 139880717092608, parent id: 139880717100896, role: Volume backup job execution
[16.02.2017 09:24:32] <139880717092608> lpbcore| BackupJobPerformer: Creating backup.
[16.02.2017 09:24:32] <139880717092608> lpbcore| WARN|Mount point [/dev] of device [devtmpfs] is already assigned to the device [devtmpfs].
[16.02.2017 09:24:32] <139880717092608> lpbcore|   Creating new backup.
[16.02.2017 09:24:32] <139880717092608> lpbcore| WARN|Directory with name:[penftp PENFTP] already exist.
[16.02.2017 09:24:32] <139880717092608> lpbcore| WARN|Directory with name:[penftp PENFTP_1] already exist.
[16.02.2017 09:24:32] <139880717092608> lpbcore| WARN|Directory with name:[penftp PENFTP_2] already exist.
[16.02.2017 09:24:32] <139880717092608> lpbcore| WARN|Directory with name:[penftp PENFTP_3] already exist.
[16.02.2017 09:24:32] <139880717092608> lpbcore|   New backup entry created, in repository path: [penftp PENFTP_4].
[16.02.2017 09:24:32] <139880717092608> lpbcore|   Enumerating backup objects.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Creating job objects filter.
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Record type: [Include], object type: [SimpleDisk], value: [{41c055a2-07c6-49f6-917a-3acfcd584064}]
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Record type: [Include], object type: [SimpleDisk], value: [00050493]
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Record type: [Include], object type: [SimpleDisk], value: [uHk13T-S6Xl-iwlG-mQHn-68IZ-h5oU-2Q9lCW/HlxsFc-Lgwv-AlAm-5in9-KKyV-Qnda-piYx26]
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Record type: [Include], object type: [SimpleDisk], value: [uHk13T-S6Xl-iwlG-mQHn-68IZ-h5oU-2Q9lCW/xSDbcu-cjJY-sRZj-1fAG-Ksi2-HEdl-A8Dqdi]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Creating job objects filter. ok.
[16.02.2017 09:24:32] <139880717092608> lpbcore| WARN|Mount point [/dev] of device [devtmpfs] is already assigned to the device [devtmpfs].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/proc]. Device number: [0:3].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/sys]. Device number: [0:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/dev]. Device number: [0:5].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/dev/pts]. Device number: [0:11].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/dev/shm]. Device number: [0:16].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/]. Device number: [253:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/selinux]. Device number: [0:14].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/proc/bus/usb]. Device number: [0:15].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/boot]. Device number: [8:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/data]. Device number: [253:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/proc/sys/fs/binfmt_misc]. Device number: [0:18].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/backup]. Device number: [0:19].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Mount point: [/root/.gvfs]. Device number: [0:20].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/dm-2]. Device number: [253:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/dvd]. Device number: [11:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/cdrom]. Device number: [11:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram9]. Device number: [1:9].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram8]. Device number: [1:8].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram7]. Device number: [1:7].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram6]. Device number: [1:6].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram5]. Device number: [1:5].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram3]. Device number: [1:3].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram4]. Device number: [1:4].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram0]. Device number: [1:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram14]. Device number: [1:14].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram10]. Device number: [1:10].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram2]. Device number: [1:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram12]. Device number: [1:12].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram13]. Device number: [1:13].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram11]. Device number: [1:11].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram1]. Device number: [1:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/ram15]. Device number: [1:15].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/root]. Device number: [253:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/vg_penftp/lv_home]. Device number: [253:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/vg_penftp/lv_swap]. Device number: [253:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/vg_penftp/lv_root]. Device number: [253:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/dm-1]. Device number: [253:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/dm-0]. Device number: [253:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/scd0]. Device number: [11:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-uuid/53f561a1-0c5a-404f-9b4d-eb4ecd0c84d6]. Device number: [253:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-uuid/99ffaeb7-a0b6-4a5a-89b0-2aa17d9476f3]. Device number: [253:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-uuid/e78efe39-4ce7-44d0-885e-93124595f952]. Device number: [253:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-uuid/3a230198-b1a0-45c8-8983-cfdab1fcb489]. Device number: [8:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:0:0]. Device number: [11:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0-part2]. Device number: [8:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:1:0-part1]. Device number: [8:17].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0-part1]. Device number: [8:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:1:0]. Device number: [8:16].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:00:1d.7-usb-0:7:1.0-scsi-0:0:0:0]. Device number: [8:32].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0]. Device number: [8:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/dm-uuid-LVM-uHk13TS6XliwlGmQHn68IZh5oU2Q9lCWBIgttffCCxx0UX6DzDxnVdMd1Q4SuxPq]. Device number: [253:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/dm-name-vg_penftp-lv_home]. Device number: [253:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/lvm-pv-uuid-58b4jm-PzoL-noWl-1A42-mnuQ-j8vv-M3ZAKl]. Device number: [8:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/lvm-pv-uuid-rYItJp-S2P0-3H7J-KlWI-PXnS-CBUi-1g3ReN]. Device number: [8:17].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/dm-uuid-LVM-uHk13TS6XliwlGmQHn68IZh5oU2Q9lCWxSDbcucjJYsRZj1fAGKsi2HEdlA8Dqdi]. Device number: [253:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/dm-name-vg_penftp-lv_swap]. Device number: [253:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/dm-uuid-LVM-uHk13TS6XliwlGmQHn68IZh5oU2Q9lCWHlxsFcLgwvAlAm5in9KKyVQndapiYx26]. Device number: [253:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/dm-name-vg_penftp-lv_root]. Device number: [253:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/ata-TEAC_DVD-ROM_DV28EV_]. Device number: [11:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/wwn-0x6001ec90e3d50600101b9bd504a61469-part2]. Device number: [8:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/scsi-36001ec90e3d50600101b9bd504a61469-part2]. Device number: [8:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/wwn-0x6001ec90e3d50600101b9bd504abf9f6-part1]. Device number: [8:17].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/scsi-36001ec90e3d50600101b9bd504abf9f6-part1]. Device number: [8:17].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/wwn-0x6001ec90e3d50600101b9bd504a61469-part1]. Device number: [8:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/scsi-36001ec90e3d50600101b9bd504a61469-part1]. Device number: [8:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/wwn-0x6001ec90e3d50600101b9bd504abf9f6]. Device number: [8:16].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/scsi-36001ec90e3d50600101b9bd504abf9f6]. Device number: [8:16].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/usb-Kingston_DataTraveler_R_8998011620080115142545E2-0:0]. Device number: [8:32].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/wwn-0x6001ec90e3d50600101b9bd504a61469]. Device number: [8:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/disk/by-id/scsi-36001ec90e3d50600101b9bd504a61469]. Device number: [8:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/sr0]. Device number: [11:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/sdc]. Device number: [8:32].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/sda2]. Device number: [8:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/sda1]. Device number: [8:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/sdb1]. Device number: [8:17].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/sdb]. Device number: [8:16].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/sda]. Device number: [8:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/253:2]. Device number: [253:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:9]. Device number: [1:9].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:8]. Device number: [1:8].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:7]. Device number: [1:7].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:6]. Device number: [1:6].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:5]. Device number: [1:5].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:3]. Device number: [1:3].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:4]. Device number: [1:4].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:0]. Device number: [1:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:14]. Device number: [1:14].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:10]. Device number: [1:10].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:2]. Device number: [1:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:13]. Device number: [1:13].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:12]. Device number: [1:12].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:11]. Device number: [1:11].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:1]. Device number: [1:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/1:15]. Device number: [1:15].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/253:1]. Device number: [253:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/253:0]. Device number: [253:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/11:0]. Device number: [11:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/8:2]. Device number: [8:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/8:17]. Device number: [8:17].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/8:1]. Device number: [8:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/8:16]. Device number: [8:16].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/8:32]. Device number: [8:32].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/8:0]. Device number: [8:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/7:7]. Device number: [7:7].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/7:6]. Device number: [7:6].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/7:2]. Device number: [7:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/7:0]. Device number: [7:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/7:4]. Device number: [7:4].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/7:3]. Device number: [7:3].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/7:5]. Device number: [7:5].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/block/7:1]. Device number: [7:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/mapper/vg_penftp-lv_home]. Device number: [253:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/mapper/vg_penftp-lv_swap]. Device number: [253:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/mapper/vg_penftp-lv_root]. Device number: [253:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/loop7]. Device number: [7:7].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/loop6]. Device number: [7:6].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/loop5]. Device number: [7:5].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/loop4]. Device number: [7:4].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/loop3]. Device number: [7:3].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/loop2]. Device number: [7:2].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/loop1]. Device number: [7:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found device: [/dev/loop0]. Device number: [7:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram0]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram1]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram2]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram3]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram4]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram5]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram6]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram7]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram8]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram9]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram10]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram11]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram12]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram13]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram14]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_ram15]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_loop0]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_loop1]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_loop2]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_loop3]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_loop4]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_loop5]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_loop6]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [DEV__dev_loop7]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     GPT type: [{28732ac1-1ff8-d211-ba4b-00a0c93ec93b}].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     GPT type: [{79d3d6e6-07f5-c244-a23c-238f2a3df928}].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found matching filter for object [{41c055a2-07c6-49f6-917a-3acfcd584064}/o1048576l524288000]. Record type: [Include], value: [{41c055a2-07c6-49f6-917a-3acfcd584064}]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Partition [/dev/sda1] with index [1] should be backed up.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found matching filter for object [{41c055a2-07c6-49f6-917a-3acfcd584064}/o525336576l298913366016]. Record type: [Include], value: [{41c055a2-07c6-49f6-917a-3acfcd584064}]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Partition [/dev/sda2] has usage type [raid] and will be skipped.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Detecting bootloader on device [/dev/sda].
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Device has GPT partition table.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No master boot record found on device.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found matching filter for object [00050493]. Record type: [Include], value: [00050493]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Found matching filter for object [00050493/o1048576l1198294827008]. Record type: [Include], value: [00050493]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Partition [/dev/sdb1] has usage type [raid] and will be skipped.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Detecting bootloader on device [/dev/sdb].
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Device has MBR partition table.
[16.02.2017 09:24:32] <139880717092608> lpbcore|       MBR gap area size: [1048064].
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Detected GRUB legacy.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No master boot record found on device.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No matching filters for object [00063bce]
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Detecting bootloader on device [/dev/sdc].
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Device has MBR partition table.
[16.02.2017 09:24:32] <139880717092608> lpbcore|       MBR gap area size: [1048064].
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Unknown bootloader detected.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     No master boot record found on device.
[16.02.2017 09:24:32] <139880717092608> lpbcore| ERR |No medium found
[16.02.2017 09:24:32] <139880717092608> lpbcore| >>  |Failed to probe device [/dev/sr0].
[16.02.2017 09:24:32] <139880717092608> lpbcore| >>  |An exception was thrown from thread [139880717092608].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Enumerating LVM volume groups...
[16.02.2017 09:24:32] <139880717092608> lpbcore|       LVM volume group: [vg_penftp].
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Enumerating logical volumes for LVM volume group: [vg_penftp].
[16.02.2017 09:24:32] <139880717092608> lpbcore|         Found matching filter for object [uHk13T-S6Xl-iwlG-mQHn-68IZ-h5oU-2Q9lCW/HlxsFc-Lgwv-AlAm-5in9-KKyV-Qnda-piYx26]. Record type: [Include], value: [uHk13T-S6Xl-iwlG-mQHn-68IZ-h5oU-2Q9lCW/HlxsFc-Lgwv-AlAm-5in9-KKyV-Qnda-piYx26]
[16.02.2017 09:24:32] <139880717092608> lpbcore|         Logical volume [lv_root] with ID [HlxsFc-Lgwv-AlAm-5in9-KKyV-Qnda-piYx26] should be backed up.
[16.02.2017 09:24:32] <139880717092608> lpbcore|         No matching filters for object [uHk13T-S6Xl-iwlG-mQHn-68IZ-h5oU-2Q9lCW/BIgttf-fCCx-x0UX-6DzD-xnVd-Md1Q-4SuxPq]
[16.02.2017 09:24:32] <139880717092608> lpbcore|         Logical volume [lv_home] with ID [BIgttf-fCCx-x0UX-6DzD-xnVd-Md1Q-4SuxPq] should not be backed up.
[16.02.2017 09:24:32] <139880717092608> lpbcore|         Found matching filter for object [uHk13T-S6Xl-iwlG-mQHn-68IZ-h5oU-2Q9lCW/xSDbcu-cjJY-sRZj-1fAG-Ksi2-HEdl-A8Dqdi]. Record type: [Include], value: [uHk13T-S6Xl-iwlG-mQHn-68IZ-h5oU-2Q9lCW/xSDbcu-cjJY-sRZj-1fAG-Ksi2-HEdl-A8Dqdi]
[16.02.2017 09:24:32] <139880717092608> lpbcore|         Logical volume [lv_swap] with ID [xSDbcu-cjJY-sRZj-1fAG-Ksi2-HEdl-A8Dqdi] should be backed up.
[16.02.2017 09:24:32] <139880717092608> lpbcore|         Logical volume [lv_swap] contains swap and will be excluded from snapshot.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     [1] LVM volume groups were detected.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Disk [/dev/sda] will be backed up.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     BIOS bootloader on [/dev/sdb] will be backed up.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Disk [/dev/sdb] will be backed up.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     LVM volume group [vg_penftp] will be backed up.
[16.02.2017 09:24:32] <139880717092608> lpbcore|   BackupJobPerformer: Taking snapshot.
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Adding disk backup object into snapshot set. Disk: [sda].
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Request to snapshot device: [8:1].
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Request to stop tracking device: [8:0].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Adding disk backup object into snapshot set. Disk: [sdb].
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Request to stop tracking device: [8:16].
[16.02.2017 09:24:32] <139880717092608> lpbcore|     Adding LVM volume group object into snapshot set. Volume group: [vg_penftp].
[16.02.2017 09:24:32] <139880717092608> lpbcore|       Device: [253:0].
[16.02.2017 09:24:33] <139880717092608> lpbcore| WARN|Method invocation was not finalized. Method id [0]. Class: [N10lpbcorelib11interaction17IResourcesServiceE]
[16.02.2017 09:24:33] <139880717092608> lpbcore| ERR |Child execution has failed. Exit code: [1].
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |--tr:Failed to execute [modprobe].
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |--tr:Unable to create snapshot.
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub21CResourcesServiceStubE].
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |--tr:Failed to invoke method [0] in class [N10lpbcorelib11interaction17IResourcesServiceE].
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |An exception was thrown from thread [139880717092608].
[16.02.2017 09:24:33] <139880717092608> lpbcore| ERR |Failed to execute thaw script with status: fail.
[16.02.2017 09:24:33] <139880717092608> lpbcore|   BackupJobPerformer: Taking snapshot. Failed.
[16.02.2017 09:24:33] <139880717092608> lpbcore|   Executing custom script: [/var/scripts/showbackup.sh]. Arguments: []
[16.02.2017 09:24:33] <139880717092608> lpbcore|     Executing custom script: [/var/scripts/showbackup.sh]. Arguments: []
[16.02.2017 09:24:33] <139880706602752>        | Thread started. Thread id: 139880706602752, parent id: 139880717092608, role: script output redirector to log
[16.02.2017 09:24:33] <139880685623040> cli    | Thread [Wait pid: 4884.].
[16.02.2017 09:24:33] <139880696112896>        | Thread started. Thread id: 139880696112896, parent id: 139880717092608, role: script output redirector to buffer
[16.02.2017 09:24:33] <139880685623040> cli    | Thread [Wait pid: 4884.]. ok.
[16.02.2017 09:24:33] <139880706602752>        | Thread finished. Role: 'script output redirector to log'.
[16.02.2017 09:24:33] <139880696112896>        | Thread finished. Role: 'script output redirector to buffer'.
[16.02.2017 09:24:33] <139880717092608> lpbcore|     Executing custom script: [/var/scripts/showbackup.sh]. Arguments: [] ok.
[16.02.2017 09:24:33] <139880717092608> lpbcore|   Executing custom script: [/var/scripts/showbackup.sh]. Arguments: [] ok.
[16.02.2017 09:24:33] <139880717092608> lpbcore| BackupJobPerformer: Creating backup. Failed.
[16.02.2017 09:24:33] <139880717100896> lpbcore| LpbManSession: Processing commands. ok.
[16.02.2017 09:24:33] <139880717092608> lpbcore| ERR |Job has failed.
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |Child execution has failed. Exit code: [1].
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |--tr:Failed to execute [modprobe].
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |--tr:Unable to create snapshot.
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub21CResourcesServiceStubE].
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |--tr:Failed to create volume snapshot.
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |Backup job has failed.
[16.02.2017 09:24:33] <139880717092608> lpbcore| >>  |An exception was thrown from thread [139880717092608].
[16.02.2017 09:24:33] <139880717092608>        | Thread finished. Role: 'Volume backup job execution'.
[16.02.2017 09:24:33] <139880717100896> lpbcore| [DEV] Destroyed [0x2e69ab0]
[16.02.2017 09:24:33] <139880717100896> lpbman | Application session has been finished.
nielsengelen
Product Manager
Posts: 5619
Liked: 1177 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by nielsengelen »

Can you run the following commands:
rpm -aq | grep kernel-devel
uname -a

Do these match? If not can you install the correct kernel headers (yum install kernel-devel) and then re-install veeam and veeamsnap?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
PTide
Product Manager
Posts: 6408
Liked: 724 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by PTide »

Hi,

I'd double-check if the veeamsnap module is loaded: lsmod | grep veeamsnap. Please also contact our support team and post your case ID.

Thanks
skochetkov
Influencer
Posts: 24
Liked: 5 times
Joined: Feb 12, 2015 12:36 pm
Full Name: Sergey Kochetkov
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by skochetkov »

Hello from Veeam Support.

Let me a little tediousness: veeamsnap is a DKMS module. DKMS modules have 4 states: not in a tree, added, built and installed. More info: http://www.linuxjournal.com/article/6896

In general, the said error message means that veeamsnap module hasn't been installed. You can check its status by running the following command
# dkms status

If the output looks like 'veeasnap added' this message means that module has been added, but hasn't been built and hasn't been installed. In the most cases, this status means that your OS doesn't have corresponding kernel-devel and kernel-headers for the current kernel. When you install them (missing packages) you can either re-install Veeam Agent for Linux in order to execute DKMS hooks which will rebuild and install veeamsnap or rebuild it manually by executing the following commands:

# dkms remove -m veeamsnap/1.0.0.944 --all
# dkms build -m veeamsnap -v 1.0.0.944
# dkms install -m veeamsnap -v 1.0.0.944

I hope my message is informative and helpful.
stevenfoo
Expert
Posts: 116
Liked: 3 times
Joined: Jun 26, 2009 3:11 am
Full Name: Steven Foo
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by stevenfoo »

Hi,

I follow your steps and get the following error during build. Any idea?

[root@penftp ~]# dkms status
veeamsnap, 1.0.0.944: added
[root@penftp ~]# dkms remove -m veeamsnap/1.0.0.944 --all

------------------------------
Deleting module version: 1.0.0.944
completely from the DKMS tree.
------------------------------
Done.
[root@penftp ~]# dkms build -m veeamsnap -v 1.0.0.944

Creating symlink /var/lib/dkms/veeamsnap/1.0.0.944/source ->
/usr/src/veeamsnap-1.0.0.944

DKMS: add completed.
Error! echo
Your kernel headers for kernel 2.6.32-642.6.2.el6.x86_64 cannot be found at
/lib/modules/2.6.32-642.6.2.el6.x86_64/build or /lib/modules/2.6.32-642.6.2.el6.x86_64/source.
skochetkov
Influencer
Posts: 24
Liked: 5 times
Joined: Feb 12, 2015 12:36 pm
Full Name: Sergey Kochetkov
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by skochetkov »

stevenfoo wrote: Your kernel headers for kernel 2.6.32-642.6.2.el6.x86_64 cannot be found at
/lib/modules/2.6.32-642.6.2.el6.x86_64/build or /lib/modules/2.6.32-642.6.2.el6.x86_64/source.
Hello. This message speaks for itself. Like I said in my previous message your system is missing kernel-headers package. Please install it using a packet manager and try to rebuild DKMS module.
https://helpcenter.veeam.com/docs/agent ... tml?ver=10

If it's more convenient, please open a support case via Customer Portal in order to resolve your installation issue.
stevenfoo
Expert
Posts: 116
Liked: 3 times
Joined: Jun 26, 2009 3:11 am
Full Name: Steven Foo
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by stevenfoo »

Manage to fixed it.

I created a link in /lib/modules and run dkms build -m veeamsnap -v 1.0.0.944 and dkms install -m veeamsnap -v 1.0.0.944
ln -s 2.6.32-642.3.1.el6.x86_64 2.6.32-642.6.2.el6.x86_64

This by pass 2.6.32-642.6.2.el6.x86_64 and uses 2.6.32-642.3.1.el6.x86_64.

The veeam backup run fine now. Thank you for the information.
skochetkov
Influencer
Posts: 24
Liked: 5 times
Joined: Feb 12, 2015 12:36 pm
Full Name: Sergey Kochetkov
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by skochetkov » 1 person likes this post

stevenfoo wrote:Manage to fixed it.

I created a link in /lib/modules and run dkms build -m veeamsnap -v 1.0.0.944 and dkms install -m veeamsnap -v 1.0.0.944
ln -s 2.6.32-642.3.1.el6.x86_64 2.6.32-642.6.2.el6.x86_64

This by pass 2.6.32-642.6.2.el6.x86_64 and uses 2.6.32-642.3.1.el6.x86_64.

The veeam backup run fine now. Thank you for the information.
Oh,I doubt that this configuration is officially supported. Summoning PTide into the thread.
PTide
Product Manager
Posts: 6408
Liked: 724 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by PTide »

Hi,

Correct, the abovementioned workaround is not supported, although it may work. If you use wrong kernel headers a memory corruption might eventually occur, so I would recommend installing proper headers.

Thanks.
davidbellido
Novice
Posts: 3
Liked: never
Joined: Feb 10, 2017 12:40 pm
Full Name: David
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by davidbellido »

stevenfoo wrote:Manage to fixed it.

I created a link in /lib/modules and run dkms build -m veeamsnap -v 1.0.0.944 and dkms install -m veeamsnap -v 1.0.0.944
ln -s 2.6.32-642.3.1.el6.x86_64 2.6.32-642.6.2.el6.x86_64

This by pass 2.6.32-642.6.2.el6.x86_64 and uses 2.6.32-642.3.1.el6.x86_64.

The veeam backup run fine now. Thank you for the information.
Please, could you post the commands that you executed?
Im not clear about how to create the link in /lib/modules

Thanks a lot
thalooka
Novice
Posts: 3
Liked: never
Joined: Mar 08, 2017 11:15 am
Full Name: Daniel
Contact:

[MERGED] Backup job fails instantly

Post by thalooka »

Hello there,

i just wanted to try Veeam Agent for Linux on my OpenMediaVault System. The Volume i want to Backup is Virutal. The device m127 is an Softwareraid where the Backup should be stored. Its running on an Debian 8.7 Jessie. I already tested reinstall since i had an error with LSB. I just installed lsb core n lsb_release n reinstalled veeam after that. Any help would be great since im pretty nooblike in Linux.

Code: Select all

[08.03.2017 12:22:45] <140216841950976> lpbcore|     No matching filters for object [DEV__dev_md127]
[08.03.2017 12:22:45] <140216841950976> dsk    | WARN|Failed to parse MBR layout. Disk size: 412090368, logical sector size: 2048, information: /dev/sr0
[08.03.2017 12:22:45] <140216841950976> dsk    | >>  |Partition table entry is out of disk bounds. Partition offset: 131072, length: 1648230400, type: 23
[08.03.2017 12:22:45] <140216841950976> lpbcore| ERR |Unsupported partition table type: [raw]. Device path: [/dev/sr0], size: [412090368], sector size: [2048]
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |An exception was thrown from thread [140216841950976].
[08.03.2017 12:22:45] <140216841950976> lpbcore|     Enumerating LVM volume groups...
[08.03.2017 12:22:45] <140216841950976> lpbcore|     [0] LVM volume groups were detected.
[08.03.2017 12:22:45] <140216841950976> lpbcore|     BIOS bootloader on [/dev/sda] will be backed up.
[08.03.2017 12:22:45] <140216841950976> lpbcore|     Disk [/dev/sda] will be backed up.
[08.03.2017 12:22:45] <140216841950976> lpbcore|   BackupJobPerformer: Taking snapshot.
[08.03.2017 12:22:45] <140216841950976> lpbcore|     Adding disk backup object into snapshot set. Disk: [sda].
[08.03.2017 12:22:45] <140216841950976> lpbcore|       Request to snapshot device: [8:1].
[08.03.2017 12:22:45] <140216841950976> lpbcore|       Request to stop tracking device: [8:0].
[08.03.2017 12:22:45] <140216841950976> lpbcore| WARN|Method invocation was not finalized. Method id [0]. Class: [N10lpbcorelib11interaction17IResourcesServiceE]
[08.03.2017 12:22:45] <140216841950976> lpbcore| ERR |Child execution has failed. Exit code: [1].
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |--tr:Failed to execute [modprobe].
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |--tr:Unable to create snapshot.
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub21CResourcesServiceStubE].
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |--tr:Failed to invoke method [0] in class [N10lpbcorelib11interaction17IResourcesServiceE].
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |An exception was thrown from thread [140216841950976].
[08.03.2017 12:22:45] <140216841950976> lpbcore| ERR |Failed to execute thaw script with status: fail.
[08.03.2017 12:22:45] <140216841950976> lpbcore|   BackupJobPerformer: Taking snapshot. Failed.
[08.03.2017 12:22:45] <140216841950976> lpbcore| BackupJobPerformer: Creating backup. Failed.
[08.03.2017 12:22:45] <140216882964352> lpbcore| LpbManSession: Processing commands. ok.
[08.03.2017 12:22:45] <140216841950976> lpbcore| ERR |Job has failed.
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |Child execution has failed. Exit code: [1].
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |--tr:Failed to execute [modprobe].
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0].
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |--tr:Unable to create snapshot.
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub21CResourcesServiceStubE].
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |--tr:Failed to create volume snapshot.
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |Backup job has failed.
[08.03.2017 12:22:45] <140216841950976> lpbcore| >>  |An exception was thrown from thread [140216841950976].
[08.03.2017 12:22:45] <140216841950976>        | Thread finished. Role: 'Volume backup job execution'.
[08.03.2017 12:22:45] <140216882964352> lpbcore| [DEV] Destroyed [0x3075f90]
[08.03.2017 12:22:45] <140216882964352> lpbman | Application session has been finished.
PTide
Product Manager
Posts: 6408
Liked: 724 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Failed to load module [veeamsnap] with parameters [zeros

Post by PTide »

Hi Daniel,

Please double-check if the module has been loaded:

Code: Select all

lsmod | grep veeam
Thanks
xenophore
Lurker
Posts: 1
Liked: never
Joined: Jun 21, 2019 10:21 am
Contact:

Re: Failed to load module [veeamsnap] with parameters [zerosnapd

Post by xenophore »

Hi there,

got the same problem, but it seems the kernel is not supported.

Code: Select all

dkms build -m veeamsnap -v 3.0.1.1046

Creating symlink /var/lib/dkms/veeamsnap/3.0.1.1046/source ->
                 /usr/src/veeamsnap-3.0.1.1046

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.0.0-15-generic -C /lib/modules/5.0.0-15-generic/build M=/var/lib/dkms/veeamsnap/3.0.1.1046/build.....(bad exit status: 2)
ERROR (dkms apport): kernel package linux-headers-5.0.0-15-generic is not supported
Error! Bad return status for module build on kernel: 5.0.0-15-generic (x86_64)
Consult /var/lib/dkms/veeamsnap/3.0.1.1046/build/make.log for more information.

nielsengelen
Product Manager
Posts: 5619
Liked: 1177 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:

Re: Failed to load module [veeamsnap] with parameters [zerosnapd

Post by nielsengelen »

I notice you are using Kernel 5.0, this will be supported in the next update. For updates please follow the Kernel 5.0 topic: veeam-agent-for-linux-f41/linux-kernel-5-0-t58236.html
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
PTide
Product Manager
Posts: 6408
Liked: 724 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Failed to load module [veeamsnap] with parameters [zerosnapd

Post by PTide »

There is an experimental branch here. It is stable, however it is not officially supported yet. That is, if you're willing to try it and report how it works for you, then feel free to use it.

Thanks!
Post Reply

Who is online

Users browsing this forum: No registered users and 11 guests