veeam stuck at the end of creating a job

[mvidalinc]

Hello,

I just installed Veeam Linux Backup Free on one of my servers (Debian 8 ). I created a job with NFS folder as destination on another of my servers (also Debian 8 ). But in the end of the configuration of the job, the software Veeam is stucked, "hanging" :



I re-tried several times, but same problem. 15 minutes and still stuck...
The NFS folder is working fine as I tested to mount it with no problem.

Can you help please ?

[mvidalinc]

Also stuck when I choose not to "start job now".

[PTide]

Hi,

Did you use GUI to connect to the NFS folder, or it was already mounted so you just selected "local" storage in the job options? Please also collect logs (use 'M' button to get to the Misc menu) and contact our support team directly (even though you have Free version) and post your case ID here.

Thanks

[mvidalinc]

My case ID : 02251723

Yes I used Veeam GUI to connect the NFS folder, but at first I also mounted the NFS folder manually before the veeam GUI, and the software stuck at the end of the creation of a job.
So I unmount the NFS folder and retried the veeam creation of a job, but same problem, software veeam stuck.

I can't export the logs with "M", I tried several times but there's no logs in the chosen folder.

[nielsengelen]

Can you try the export with:

Code: Select all

veeamconfig config grablogs --dir /root

This creates a file like veeam_logs_2017**********.tar.gz

[mvidalinc]

Error :

Code: Select all

veeamconfig config grablogs --dir /root
Error: Unknown argument: [--dir].

Ok with this command :

Code: Select all

veeamconfig config grablogs
--> veeam_logs_20170720_111805.tar.gz

[nielsengelen]

Seems the parameter was removed with update 1 . At least the export worked and you can send them to support now.

[mvidalinc]

Ok, done.

[mvidalinc]

Just for information, with a third server of mine, and the same NFS destination, it works with no problem.

[mvidalinc]

Ok it works now. The support person restart the veeam service in Linux and now it's ok.