A solution may be: Run the script but implement a procedure which tests, wether the two .exe files exist. If not you can assume your backup was successful but contains 0 bytes, in which case you don't let the script wipe the directory.
Hope I've understood what you're doing... Christoff Am Tue, 20 Jun 2006 17:12:33 +0100 schrieb Beren <[EMAIL PROTECTED]>: > I would make the script check which files to delete (based on the date > maybe?) so even if bacula stuffs up, you've got a failsafe in the > script. > > > On 16/06/06, Jeremy Koppel <[EMAIL PROTECTED]> wrote: >> >> >> >> >> I've been experimenting with the ClientRunAfterJob function lately to >> delete >> files from a temporary backup location on a remote client. The >> database on >> the client backs up 2 files nightly in its own format, then my >> ClientRunBeforeJob script compresses these into self-extracting .exe >> files. >> The Bacula job is set to back up just those 2 files, then run the second >> script to wipe the directory. >> >> >> >> Seems to work great, except that last night the 2 .exe files failed to >> generate (my own goof), but the ClientRunAfterJob script ran anyway, >> even >> though the job failed, deleting the good backup without actually >> backing it >> up (I'm in test mode, so nothing critical was lost yet). How would I >> tell >> Bacula not to run that script unless the backup is completely >> successful? >> >> >> >> >> >> --Jeremy Koppel >> >> >> _______________________________________________ >> Bacula-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> >> >> > > > _______________________________________________ > Bacula-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/bacula-users _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
