On 24/07/2024 17:04, Radosław Korzeniewski wrote:
Hello,
pon., 1 lip 2024 o 23:03 Bill Arlofski via Bacula-users
<bacula-users@lists.sourceforge.net
<mailto:bacula-users@lists.sourceforge.net>> napisał(a):
It is generally recommended to stick to the same priority for your
normal backup
and Restore Jobs, and then set the small number of "special" jobs
(Admin, CopyControl, MigrationControl, Verify, etc) to
something else so they they do not run as the same time as "normal"
jobs.
Fully agreed. This "priority" parameter is misleading too. In most cases
users expect higher priority jobs to overrule lower priority.
But it happens on queue only, not at job runtime. As waiting for a job
in queue should be and in most cases is a very rare event this
"priority" does not work at all.
I found the priority option useful for separating "normal" jobs from
"special" ones, as Bill described above. Unless your Bacula is busy
working 24/7 doing backup jobs and lower priority jobs will never start.
best regards
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). :-)
Some of the differentials and fulls can take more than 24 hours to
complete, so I run them on different weekends.
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.
Cheers,
Gary B-)
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
