Jeremy,
Thanks for the pointer. I did some reading on Bacula Job Priority settings and
discovered the following tidbit:
Bacula will not run jobs with differing priority levels simultaneously, even if
the SD is configured to run more than one job concurrently. For instance, if
you have 2 jobs scheduled to run at the same time but one Job has Priority=10
and the other has Priority=20, the SD will not run them at the same time even
if the Maximum Concurrent Job set is for 2 or higher. The SD will run the Job
with priority 10 first. It will start the 2nd Job ONLY AFTER the 1st Job has
terminated.
So in the end, the solution to my problem is quite simple: Just make sure that
the weekly full Backup Job and the Copy Job have different priority settings.
Now I can enjoy my Sunday evenings again.
Thanks to all for your responses.
Cheers!!.
________________________________________
From: Jeremy Maes [jma AT schaubroeck DOT be]
Sent: Thursday, March 01, 2012 2:42 AM
To: Conrad Lawes
Cc: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] Flexible Scheduling
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
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
