Description
We use Bacula for backup, after a backup on the client, Bacula runs a script that additionally presses the required data with a tar.
In the director’s settings in the job for the client, it looks like this:
Run Script {
Runs When=After
Runs On Client=yes
Runs On Success=yes
Runs On Failure=no
Fail Job On Error=no
Command="sh /home/test2.sh"
}Everything is great, the script runs after backup, but bacula does not consider the task completed until the script runs to the end, and this can take a long time, which is why I can create unnecessary queues in the director...
Tried to get around this with the standard Bashiv ampersand(&):
Command="sh /home/test2.sh&"
Nothing comes out, even tried to launch another script with an ampersand from the script, anyway bacula considers the task not completed until the script is finished...Oo
Of course, there are thoughts to create a script that launches a bakul, any file in tmp, and to check for the presence of this file using a crown script and run tar, but you don’t want to fence such crutches.There must be a way out!
Tell me, who faced with Bacula, how to solve this problem?
Description