Bacula 5.0.2. The documentation states that a ClientRunBeforeJob script that returns a non-zero status causes the job to be cancelled. This is not what appears to happen, however. Instead a fatal error is declared:
11-Aug 13:30 cbe-dir JobId 686: No prior Full backup Job record found. 11-Aug 13:30 cbe-dir JobId 686: No prior or suitable Full backup found in catalog. Doing FULL backup. 11-Aug 13:30 cbe-dir JobId 686: Start Backup JobId 686, Job=baxter_fs1b.2010-08-11_13.30.26_09 11-Aug 13:30 cbe-dir JobId 686: Using Device "Data1" 11-Aug 13:30 toe-fd JobId 686: shell command: run ClientRunBeforeJob "/etc/bacula/cbe_hanfs.sh /mnt/baxter/fs1" 11-Aug 13:30 toe-fd JobId 686: Error: Runscript: ClientRunBeforeJob returned non-zero status=1. ERR=Child exited with code 1 11-Aug 13:30 cbe-dir JobId 686: Fatal error: Bad response to ClientRunBeforeJob command: wanted 2000 OK RunBefore , got 2905 Bad RunBeforeJob command. 11-Aug 13:30 cbe-dir JobId 686: Fatal error: Client "toe-fd" RunScript failed. 11-Aug 13:30 cbe-dir JobId 686: Error: Bacula cbe-dir 5.0.2 (28Apr10): 11-Aug-2010 13:30:29 This causes alerts to be generated and leaves a failed job in the database. I don't see any obvious way to fix this; does anyone know how? Steve ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
