Why use CIFS - a Windows Share - for a Linux Box and it’s backup?
CIFS uses much more CPU resources than eg NFS, which is like a native language for UNIX/Linux. Speaking a foreign language is always harder than speaking your native tongue!
-> Try switching over to use NFS!
BTW: NEVER mount the Backup Share!
The Backup programm will do that.
If it’s already mounted, you’ll get an error - and no backup!
The reason you’re getting that message is that you’re combining a partial directory name (/etc/e-smith/events/actions/mount-, which doesn’t exist) with a command (config) that doesn’t live there, or in any of the actual directories that are similar to that. Why are you running the command that way? And what actual error do you get when the backup tries to run?
…or one that uses NFS for other purposes as well, and doesn’t have sufficiently-granular IP access controls. Or simple user preference–that’s valid too.
this is a time-out problem on CIF-shares.Sorry, I do not find the old thread - but when I started using Nethserver arround 2015 / 2016 I had exactly the same problem. I switched to NFS, Amazon S3 and a USB-Disk.
Do not use CIFs for regular backups - it is just fine for sending a few data …