On Tue, 2011-07-05 at 09:03 +0200, Uwe Mohn wrote: > I'd suggest using different prioritys for your virtual fulls since > bacula won't start a job with a higher bacula priority (means lesser > importance) > before a job with a lower bacula priority (means higher importance) has > terminated. For example the virtual Full you want to run first priority = 11 > for the second one priority = 12 and so on.
Very good idea. I thought about this and got to the conclusion that this method does not scale too well: I would have to add an additional (virtualFull) job for every client and coordinate all priorities of these jobs: I.e. If I create a new client I need to check for a new, not occupied "priority slot". All in all I think this would work, but I am not yet willing to give up in favor of a simpler solution I do not see. Thanks for your answer. Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum ---------------------------------------- Auf dem Huegel 69, D-53121 Bonn Tel: +49 (228) 525 359, Fax: +49 (228) 525 229 jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
