VEEAM Backup Fails after Linux OS updates.

[JoeF]

I have been using VEEAM on my KDE NEON box to back it up to my Synology NAS for a long time now. I routinely swap the machine back and forth between linux and windows by using VEEAM to restore bare metal from backup vs dual booting. It's never had an issue until this month when I restored from backup and ran updates. It was already at VEEAM 2.x before and that worked fine but I think something has changed with the CIFS UTILS. Now every time I try to backup I get the following:

10:39:12 Job KDE NEON started at 2018-01-27 10:39:12 EST
10:39:12 [error] Failed to perform backup
10:39:12 [error] mount error(112): Host is down
10:39:12 [error] Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
10:39:12 [error] Exit code: [32]
10:39:12 [error] Failed to execute script command mount

When I look up that error I see a lot of people get around it by specifying the SMB protocol level on the command line. Not something I know how to do in Veeam if it is even possible. Nothing has changed on the NAS and to be sure I restored it and ran a backup and it worked fine. Ran the waiting updates and it now fails 100% again. Oddly when I browse to the device in the KDE GUI I can browse and work with the device and files just fine. I just cannot backup to it.

Does anyone have any ideas on this?

[JoeF]

And... SOLVED. Apparently it seems SMB1 protocol was removed which isnt a bad thing but for some reason my NAS had Min and Max SMB protocol versions set to 1. So I set Min to 2 and Max to 3 and viola! We're back in business.

[PTide]

Hi,

Thank you for getting back to us with the resolution!

[hbilke]

Reinstalled free veeam-Agent, rebooted but:

Code: Select all

mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Exit code: [32]
Failed to execute script command mount                 │
Unable mount device[//smbnas/backupshare] to [/tmp/veeam/smbnasbackupshare]. 
(shares etc edited)

Can access the share(s) from "thunar" (mount it via filemanagers like tux-commander et. al.)

Agent is 2.0.1.665
What to check/fix
Hints?

Thanx

[PTide]

Hi,

What is the SMB version that you use on your SMB server? The server using the older version of SMB protocol might be the reason.

Thanks