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 Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users