[bareos-users] ClientAfterJob returned non-zero status=208

2019-09-13 Thread Stefan Harbich
Hi, after backup of the catalog I try to start a script that fails with the following error message: 2019-09-13 17:16:24 bareos-sd JobId 594: Releasing device "FileStorage" (/media/usb/backups/storage). 2019-09-13 17:16:24 dsme01-fd JobId 594: shell command: run ClientAfterJob ".bvfs_update"

Re: [bareos-users] Re: Bareos active client network setup not working

2019-09-13 Thread Spadajspadaj
Firstly, let me say that - from the security point of view - it's usualy best idea to let the connection come from the director to the clients (you usually connect from safer zone to less safe one). Secondly -

[bareos-users] Re: Bareos active client network setup not working

2019-09-13 Thread Jörg Steffens
The first thing you should check is if the client is connected to the Director. For this, use the bconsole. In there use the command "status dir" It shows you the list of clients that are connected to the Director. Header is: Client Initiated Connections (waiting for jobs): If your client does

[bareos-users] Bareos active client network setup not working

2019-09-13 Thread John Saruni
Hi Listers, I am running Bareos (Director and FD) Version: 18.2.5. I have clients behind a NAT gateway. It is not feasible to configure 1:1 NAT for all the clients. A little research pointed me to a client initiated network connection model. My config files for this model are: 1.Director's