Maybe because the first barrier is the fact you setup a different priority, when all other priority will have finished, then the P1 will be scheduled, and the countdown will start.
https://docs.bareos.org/master/Configuration/Director.html?highlight=priority#config-Dir_Job_Priority Maybe you want to try AllowMixedPriority (but playing with priority has never been a good idea ;-) On Friday, September 23, 2022 at 2:15:07 PM UTC+2 Łukasz Szczepanik wrote: > Hi, > > I have one of my job configured with MaxStartDelay = 3600 to be cancel if > it waits 1h for execution. Unfortunately it does not work. Anyone knows why > this option might not work ? > > Job { > Name = "backup-job" > Type = Backup > Messages = "Standard" > Storage = "Storage-01" > Pool = "Pool-01" > Client = "Client-01" > FileSet = "Fileset-01" > Schedule = "Cycle-01" > MaxStartDelay = 1 hours > Priority = 1 > RunAfterJob = "....." > RunBeforeJob = "....." > } > > There is no information about it in the log file. Just "status dir" shows > me: > > Running Jobs: > Console connected at 23-Sep-22 12:04 > JobId Level Name Status > ====================================================================== > 5418 Full client02-backup-job.2022-09-21_10.33.16_50 is running > 5580 Full client01-backup-job.2022-09-23_10.00.00_50 is waiting for > higher priority jobs to finish > ==== > -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/9f424b13-2042-401f-bb9a-16e82a016a9bn%40googlegroups.com.
