Am 01.04.20 um 17:41 schrieb Bernie Elbourn:
> 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
>> ======================================================================
>> 70172 Back Diff 120 36.70 M Backup-pc is running
>> 70173 Back Incr 0 0 Backup--pc is waiting on max Job jobs
>> ====
>>
>> Are there any pointers to trace why the duplicate job 70173 is not
>> cancelled?
>
> Obfuscation error.... both above should read Backup-pc - they were same name.
It is exactly same job configured?
I cannot see an error. By the way here my JobDefs configuration for my daily
jobs
which should work nearly as you expect:
34 JobDefs {
35 Name = "RotateJob"
36 Type = Backup
37 Level = Incremental
38 Schedule = "Cycle"
39 Max Start Delay = 1240000
40 Max Wait Time = 3600000
41 Max Run Time = 3600000
42 Spool Data = yes
43 Spool Attributes = yes
44 Messages = Standard
45 Pool = Daily
46 Storage = "Disk2"
47 Incremental Backup Pool = Daily
48 Differential Backup Pool = Weekly
49 Full Backup Pool = Monthly
50 Rerun Failed Levels = yes
51 Allow Duplicate Jobs = no
52 Cancel lower level duplicates = yes
53 Cancel Queued Duplicates = yes
54 Cancel Running Duplicates = no
55 Accurate = yes
56 Priority = 9
57 Allow Mixed Priority = yes
58 }
By the way against my meaning I remember it cancel also lower level
running jobs (Inc if Diff is started) althoug I should first finish
the Inc and then start the diff job. Only if the Inc is waiting in
the queue it should be cancel. I must check it again later.
Cheers,
Pierre
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
