Hi tomasz, on 01.02.2008 12:56 you wrote: > bacula do not track or care about scripts running as before_backup > thingy if they are successful or not. > > bacula care about files to backup > > if 'external' script for some reason failed i does not mean it is > important for bacula.
Yes it does. Just a couple of days ago one of my Bacula backup jobs failed because the ClientRunBeforeScript contained a mistake. Bacula started the script, noticed that it didn't run successfully, and consequently didn't even try to back up any files from that client. So, obviously, Bacula *does* track and care if "Run Before" scripts are successful, and it *is* important to Bacula if such an external script failed for whatever reason, to the point that Bacula actually refuses to back up any files from the affected client. Note1: This is as it should be. If the "Run Before" script is of such a nature that the backup can proceed even if the script failed, then the script should just refrain from signalling its failure to Bacula. (It's easy: in shell terms, do "exit 0" instead of "exit $?".) Note2: I am aware that this wasn't Justin's problem. I just wanted to clear up the misconception. HTH T. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
