Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
bdleo
Novice
Posts: 3 Liked: never
Joined: Oct 19, 2016 7:59 pm
Contact:
Post
by bdleo » Oct 19, 2016 8:08 pm
this post
Hello All,
I am trying to configure Veeam on RHEL 6 and i get the following error when trying to backup to a windows share folder.
I have proper network access to the share, veeam is able to create a folder with a job name but it fails to create the backup.
Code: Select all
2016-10-19 12:02:38 Job started at 2016-10-19 12:02:38
2016-10-19 12:02:38 Starting backup
2016-10-19 12:02:38 [error] Failed to create volume snapshot 00:00:02
2016-10-19 12:02:40 [error] Child execution has failed. Exit code: [1].
2016-10-19 12:02:40 [error] Failed to load module [veeamsnap] with parameters [deferiocache=0 debuglogging=0].
2016-10-19 12:02:40 [error] Failed to perform backup
i have attached my logs at
http://jmp.sh/JPQx0ib
Upon reviewing the logs i notice the following errors:
Code: Select all
[19.10.2016 11:20:37] <140283452159744> lpbcore| ERR |Child execution has failed. Exit code: [1].
[19.10.2016 11:20:37] <140283452159744> lpbcore| >> |--tr:Failed to execute [modprobe].
[19.10.2016 11:20:37] <140283452159744> lpbcore| >> |Failed to load module [veeamsnap] with parameters [deferiocache=0 debuglogging=0].
[19.10.2016 11:20:37] <140283452159744> lpbcore| >> |--tr:Unable to create snapshot.
[19.10.2016 11:20:37] <140283452159744> lpbcore| >> |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub21CResourcesServiceStubE].
[19.10.2016 11:20:37] <140283452159744> lpbcore| >> |An exception was thrown from thread [140283452159744].
I have tried uninstalling and reinstalling Veeam and Veeamsnap and updating the necessary dependencies.
thanks in advance
nielsengelen
Product Manager
Posts: 5796 Liked: 1215 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:
Post
by nielsengelen » Oct 20, 2016 6:57 am
this post
What is the output if you do modprobe veeamsnap and then lsmod | grep veeam ?
Seems the installation of the kernel module failed and therefor it won't work.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
bdleo
Novice
Posts: 3 Liked: never
Joined: Oct 19, 2016 7:59 pm
Contact:
Post
by bdleo » Oct 21, 2016 4:29 pm
this post
Code: Select all
[root@eclipsetest ~]# lsmod | grep veeam
[root@eclipsetest ~]# modprobe veeamsnap
FATAL: Module veeamsnap not found.
[root@eclipsetest ~]#
I figured that the modprobe module was missing, when i navigate to /etc/modprobe.d
i can not find 10-unsupported-modules.conf How can i install modprobe?
Mike Resseler
Product Manager
Posts: 8191 Liked: 1322 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:
Post
by Mike Resseler » Oct 23, 2016 8:09 am
this post
Hi,
The Veeamsnap module seems not to be installed... Could you try to install the solution again following the instructions here:
https://www.veeam.com/blog/veeam-backup ... lable.html
Is it possible that you installed the veeam-...rpm package and not the veeamsnap-...rpm package which should have been done first?
Thanks
Mike
bdleo
Novice
Posts: 3 Liked: never
Joined: Oct 19, 2016 7:59 pm
Contact:
Post
by bdleo » Oct 24, 2016 9:49 pm
this post
Fixed the issue.
After uninstalling veeam and veeamsnap, i re-installed kernel-devel and then was able to successfully install veemsnap.
Thanks!
Mike Resseler
Product Manager
Posts: 8191 Liked: 1322 times
Joined: Feb 08, 2013 3:08 pm
Full Name: Mike Resseler
Location: Belgium
Contact:
Post
by Mike Resseler » Oct 25, 2016 6:57 am
this post
Interesting...
So you actually had installed Veeamsnap first. But to get it fixed, you needed to reinstall kernel-devel... Where there are other packages that didn't work? I wonder if it was Veeam that did something wrong the first time you installed or it was already in a bad shape before that...
thanks for coming back to us with the solution!
Mike
PTide
Product Manager
Posts: 6551 Liked: 765 times
Joined: May 19, 2015 1:46 pm
Contact:
Post
by PTide » Oct 25, 2016 10:26 am
this post
Since kernel-devel is needed to compile kernel modules I suspect that the kernel module could not be compiled properly during the first attempt due to some problems with the kernel-devel package (wrong version for example) that is why reinstallation did the trick.
Users browsing this forum: No registered users and 19 guests