From: Jeremy M. <jm...@sc...> - 2012-03-01 07:42:52
|
Op 1/03/2012 3:19, Conrad Lawes schreef: > I have a unique requirement and I'm not sure if Bacula can do this. Here goes: > > I presently have 12 servers ( mixture of Windows and Linux) in my backup rotation. I plan to add a couple more clients soon. From Monday to Thursday, I do incremental backups to disk. On Friday a full weekly backup is started. This full backup is also written to disk. The full backup normally completes some time on Sunday evening. The end time varies depending on the amount data that is being backed up. On Sunday, I also have scheduled Copy job that archives the resent full backup to tape for offsite storage. The Copy Job takes 48-68 hours to complete. Our offsite storage provider picks up the tapes on Wednesday mornings. > > My problem is that sometimes the Copy-to-Tape job (D2T) starts BEFORE the Full backup (D2D) has completed. When this happens, I have to intervene and change the Copy Job schedule to later time to ensure that all the jobs in the full backup are captured. Instead of fiddling with the schedule settings to find the ideal time, I would like a flexible ( or scriptable??) scheduling option would start the Copy Job ONLY after the weekly full backup has completed. In so doing, I don't have to spend my Sunday evenings monitoring backup jobs. > > > Any suggestion? Maybe use different priorities for your weekly full and your copy jobs, and disallow the running of mixed priority jobs? Regards, Jeremy **** DISCLAIMER **** http://www.schaubroeck.be/maildisclaimer.htm |