There is an easier way to do it, just make sure that certain job always runs last. I did something similar with encryption (before it existed in Bacula) using "RunAfterJob" command placed in "BackupCatalog" job Just make sure that 1 - priority is the lowest (highest integer number) of all jobs 2 - Maximum Concurrent Jobs = 1 3 - RunAfterJob = "/etc/bacula/whatever_script.sh" 4 - Edit "/etc/bacula/whatever_script.sh" to your liking. Use FTP or even better SCP/SFTP to copy the data over to another server. Make sure these protocols support large file transfers (compiled with "-D_FILE_OFFSET_BITS=64" Cflag), otherwise the max transfer limit will be 2 Gig.
BTW, instead of using "BackupCatalog" job, you could create an admin job with same settings as above, I believe it is covered in the manual. Good luck James Harper wrote: > So what I'm after is something that will firstly only run once all the > nightly backups are done. I can do a time based best-guess on when the > backups will have been completed by, but that feels a little kludgy. I > could attach a 'run-after' to the job that I think will run last, but I > don't know if that is deterministic? Finally, I could have a cron job > that kicks off some time around when the backup will probably end, and > makes sure that the latest backup file is not in use (fuser) and has not > changed over a (say) 5 minute interval. > > After it has established that the backup has definitely completed, it > would then ftp the file up to the NAS. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
