On 01/04/2020 16:10, Bernie Elbourn wrote:
Oddly, jobs run sequentially as follows rather than duplicates being cancelled:
Running Jobs:
Console connected at 29-Mar-20 12:36
JobId Type Level Files Bytes Name Status
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
On 03/04/2020 03:58, Pierre Bernhardt wrote:
It is exactly same job configured?
A good thought but yes it is same simple job with no inherited defaults.
Some extra detail this time using sed to reliably obfuscate :-)
Running Jobs:
Console connected at 29-Mar-20 12:36
JobId Type Level
Oops...
On 01/04/2020 16:10, Bernie Elbourn wrote:
Hi,
Oddly, jobs run sequentially as follows rather than duplicates being cancelled:
Running Jobs:
Console connected at 29-Mar-20 12:36
JobId Type Level Files Bytes Name Status
Hi,
Oddly, jobs run sequentially as follows rather than duplicates being cancelled:
Running Jobs:
Console connected at 29-Mar-20 12:36
JobId Type Level Files Bytes Name Status
==
70172 Back Diff
Howdy,
The director is Debian Stretch running v7.4.4. The client is Windows 10
Professional also with v7.4.4. I am guessing the PC was doing some update or
other and VSS started for bacula but then was claimed by something else. Some
data was backed up but it would be useless for a restore
