Re: [Bacula-users] Bacula 5.2.13 ClientRunAfterJob

2015-03-24 Thread Peter Wood
Thank you for the replies. Seems that external script is the way to go. Thank you, On Sat, Mar 21, 2015 at 10:22 PM, Davide Franco wrote: > Hi Peter, > > As Kern mentioned, I'd mention a shell script instead of the whole command > in the Job definition. > I do this on "my jobs" and it work like

Re: [Bacula-users] Bacula 5.2.13 ClientRunAfterJob

2015-03-21 Thread Davide Franco
Hi Peter, As Kern mentioned, I'd mention a shell script instead of the whole command in the Job definition. I do this on "my jobs" and it work like a charm. Hope it will help you to solve your problem. Best regards Davide On Sat, Mar 21, 2015 at 8:28 PM, Kern Sibbald wrote: > Hello, > > Bac

Re: [Bacula-users] Bacula 5.2.13 ClientRunAfterJob

2015-03-21 Thread Kern Sibbald
Hello, Bacula does not run a shell when it executes a "command" as you are doing. Consequently shell characters such as * will be treated as themselves rather than shell characters (in this case a wild card). This is because such interpretation is done by the shell. So the solution is to e

Re: [Bacula-users] Bacula 5.2.13 ClientRunAfterJob

2015-03-19 Thread Dimitri Maziuk
On 03/19/2015 11:54 AM, Peter Wood wrote: > Thank you for the reply. > > Yes, I've done all the debug steps I can think of. > > Permissions is a good point though. The file permissions are 600 root:root. > Only root can remove the file. > > Bacula-fd process runs as root so I'm expecting it will

Re: [Bacula-users] Bacula 5.2.13 ClientRunAfterJob

2015-03-19 Thread Peter Wood
Thank you for the reply. Yes, I've done all the debug steps I can think of. Permissions is a good point though. The file permissions are 600 root:root. Only root can remove the file. Bacula-fd process runs as root so I'm expecting it will be able to remove the file, right? SELinux is disabled.

Re: [Bacula-users] Bacula 5.2.13 ClientRunAfterJob

2015-03-19 Thread Ana Emília M . Arruda
Hi Peter, Have you checked if the job falis or not? The Client Run After Jog do not runs if the job falis. You can use the bellow if you want that the script runs despite of the job falis or not: Run Script { RunsWhen = After RunsOnFailure = yes Commnad = "/bin/rm -f /backup/daily/mysql-Sl

[Bacula-users] Bacula 5.2.13 ClientRunAfterJob

2015-03-18 Thread Peter Wood
In Bacula 5.2.13 I use Client Run Before Job = "mysqldump " to dump the database before the backup starts. After it is complete I use Client Run After Job = "/bin/rm -f /backup/daily/mysql-Slave*" with the intend to remove the backup file due to lack of free space to keep more then one bac