Martin Simmons wrote:
>> Interesting. What is the largest number that behaves like this?
Stephan> looks like it's 199.
I suppose that makes sense in a warped kind of way :-)
;-)
>> Does returning 5 like you did initially always return in "Backup OK -- with
>> warnings" with "Non-fatal FD errors: 1"?
Stephan> as ClientRunAfterJob it does.
Ah, sorry, I misread your original post and was looking at ClientRunBeforeJob.
However, I still don't get any Non-fatal errors on FreeBSD with the
ClientRunAfterJob.
that means it always terminates with '*** Backup Error ***' when you
exit with e.g. 5?
In fact, it should be impossible because that number is
returned to the Director before the ClientRunAfterJob runs!
which number? Sorry, I may misunderstood something: but the Director
should not know the return code /before/ the ClientRunAfterJob runs?
(that would be an impressive piece of code - predicting the future ;-) )
Or do you mean that the return code of ClientRunBeforeJob is send to the
director before the ClientRunAfterJob is executed? That would make sense.
Stephan> hmmm, in my case not. Since I may have stored something that is not
Stephan> (entirely) useful.
Stephan> The background of this is that my ClientRunBeforeJob initiates a
Oracle
Stephan> database full export. The actual data is written to a FIFO pipe where
Stephan> bacula sucks the data from during the backup job. This works pretty
well
Stephan> so far.
Stephan> Finally I use the ClientRunAfterJob to parse the log file that oracle
Stephan> creates. Since sometimes the database is not /entirely/ exported. The
Stephan> dump might not contain everything we would need/want to restore. E.g.
Stephan> somebody could have locked a single table. Or oracle produced a
variety
Stephan> of other warnings. In that case it is necessary to run the export
again.
Stephan> Thus the backup job should fail and notify us this way.
Ah, I see. I don't know of any way to make that situation record a failed
job.
hmmm, from how I understood the manual it should work exactly like this?
It says:
Run After Job = <command>
The specified command is run as an external program after the
current job terminates. This directive is not required. The command
string must be a valid program name or name of a shell script. If
the exit code of the program run is non-zero, the current Bacula job
will terminate in error. Before submitting the specified command to
the operating system, Bacula performs character substitution as
described above for the Run Before Job directive.
An example of the use of this command is given in the Tips Chapter
of this manual. As of version 1.30, Bacula checks the exit status of
the RunAfter program. If it is non-zero, the job will be terminated
in error.
[...]
Client Run After Job = <command>
This command is the same as Run After Job except that it is run on
the client machine. Note, please see the notes above in Client Run
Before Job concerning Windows clients.
Stephan
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
