On 19/04/2020 20:49, Pierre Bernhardt wrote:
[SNIP]
For running jobs only that the running job with same level or higher will be
abortet the running.
For queued job it is ok, but for running job it should not start a new at same
level.
Better want to wait or want to cancel.
If there is a way that a higher job will wait for each running job has to been
finished
would be also welcome. So I can start a new full after a inc has to been
canceled.
But for queued jobs the behavior is exactly as expected and needed.
So any idea what I must change to have the effect on running jobs without
changing the
queued behavior?
Are your full/differential/incremental jobs running with different
priorities?
You haven't shown anything that sets them differently, there is no
priority difference between full/differential/incremental jobs unless
you set it.
Cheers,
Gary B-)
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
