View Issue Details

IDProjectCategoryView StatusLast Update
0001063bareos-core[All Projects] Generalpublic2019-07-12 10:57
Reportercm@p-i-u.deAssigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status feedbackResolutionopen 
PlatformLinuxOSCentOSOS Version7
Product Version18.2.5 
Target VersionFixed in Version 
Summary0001063: Add option to set priority to schedule Resource
DescriptionCurrently it is still not possible to schedule a weeky and monthly based Pool Backup on fridays, because it happens that 2 Jobs overlap each other having a schedule like this
(Some month have 5 fridays others only 4 fridays)

Schedule {
  Name = "Default"
  Run = pool=Daily mon-thu at 22:30
  Run = pool=Weekly 1st-4th fri at 22:30
  Run = pool=Monthly last fri at 22:30
}

To solve this isssue it would be great to have priority keyword added to the scheduler similar like in the job resource. With this option it is possible to define which job should take precedence if more then one job match the scheduler criteria.

For example like this,
run Weekly but have Monthy take precedence if both would match

Schedule {
  Name = "Default"
  Run = pool=Daily mon-thu at 22:30
  Run = pool=Weekly 1st-4th fri at 22:30 priority = 20
  Run = pool=Monthly last fri at 22:30 priority = 10
}
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

arogge

arogge

2019-07-12 10:57

developer   ~0003450

you can work around this by scheduling monthly five minutes early and disallowing duplicate jobs.
While I think you're right that we need something like "every friday, but the last", I would assume that priority in this context would override the job's priority (like pool and level do) and not declare the priority of this schedule entry.

Can you update your proposal so we don't have this kind of ambiguity?

Issue History

Date Modified Username Field Change
2019-02-22 23:49 cm@p-i-u.de New Issue
2019-07-12 10:57 arogge Status new => feedback
2019-07-12 10:57 arogge Note Added: 0003450