On 03/04/2020 13:19, Gary R. Schmidt wrote:
And the reason it doesn't get cancelled is because they are *not* identical jobs, one is "Differential" and the other
is "Incremental."
You need to run the Differential, Incremental, and Full jobs at different priorities - that reflect how you want
things done - and set "Cancel Lower Level Duplicate = Yes" and "Allow Mixed Priority = Yes" in them all.
Hi,
Its an intriguing thought but the bacula 7 reference manual only mentions the
name...
"Allow Duplicate Jobs = <yes|no> A duplicate job in the sense we use it here
means a second or sub-
sequent job with the same name starts. This happens most frequently when the
first job runs longer
than expected because no tapes are available."
... it then goes on to explain options for lower or higher jobs without
reference to priority...
"Cancel Lower Level Duplicates = <yes|no> If Allow Duplicate Jobs is set to no
and this directive
is set to yes, Bacula will choose between duplicated jobs the one with the
highest level. For example,
it will cancel a previous Incremental to run a Full backup. It works only for
Backup jobs. The default
is no. If the levels of the duplicated jobs are the same, nothing is done and
the other Cancel XXX
Duplicate directives will be examined."
I am pretty sure that the configuration files are ok. I have now copied the configuration to another system, and on that
setup lower level duplicates are cancelled as expected rather than queued "max job jobs".
Have to say debugging this peculiarity is baffling me...
Rgs
Bernie
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
