Hello, śr., 24 lip 2024 o 10:22 Gary R. Schmidt <g...@mcleod-schmidt.id.au> napisał(a):
> I found the "priority" option very useful for ensuring that jobs are > executed in a - to me - sensible order. > > Incremental jobs (48), then differential jobs (49), then full jobs (50). > Then catalogue backups (91). :-) > If you have a single schedule, so all your jobs start at the same time, then yes, it could work. But scheduling Incremental, Differential and Full at the same time, sounds weird and suboptimal. > > Some of the differentials and fulls can take more than 24 hours to > complete, so I run them on different weekends. > > If your full job is stuck and running long, then no other backup jobs can start. If your Differential and Full runs on every other weekend, alternating then why different priority? Just curious. > Fortunately it doesn't matter if they run into the next week. (No 24*7 > development here! ;-) (Bug fixes, that's different. :-( )) > > If you play with scheduling and priorities you can get quite useful > variations that avoid the, "Oh, no, it's full backup time, come back > next week/month/year!" pain. > Congrats! I wish I had a production system with less than hundreds (or thousands) of jobs per day. If one job with different priorities sneezes then the whole system is stuck. No luxury for such an event. R. -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
