View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000230 | bareos-core | General | public | 2013-10-03 17:27 | 2013-10-11 16:36 |
Reporter | cm@p-i-u.de | Assigned To | maik | ||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | closed | Resolution | won't fix | ||
Platform | Linux | OS | Ubuntu | OS Version | 12.04 |
Summary | 0000230: Implement Next Job Directive, add an additional Way of Job processing | ||||
Description | I've suggested this a long time ago to the bacula-dev, but it found no interest, so I see if I have more luck with bareos. Currently we have a very static way of how jobs are scheduled and processed, you can control when a job is executed via the Priority and some Max (Run|Start Delay|etc.) Time directives. From time to time these parameters have to be adjusted as backup data grows or backup times increase because of other reasons. While this may not be a problem in the large enterprise where you have full time administrators, it is in the Small to Mid size companies where the whole IT is managed by external Administrators. So it would be very nice to have an alternative way to specify how and when jobs are executed. Therefore a "Next Job=" directive could be implemented where you define the next job to be executed in a Job Resource. The advantage is, that you could specify a Max Run time which applies to all jobs and have the jobs executed one after each other without caring about all the other directives needed that for example the second job waits for about 5 hours to be executed before being canceled. In this way it gets executed just after the first job has been finished and the only impacting factor is the Maximum Run time for all jobs. In Additional there should be some way to control if the job gets executed just if the prior job was finished successfully or not. Another possibility would be to implement a main directive which defines which jobs gets executed in what order and the condition which has to be met for that job to be executed. With this you'll have a flow based job processing. | ||||
Tags | No tags attached. | ||||
Sorry, Priority should be feature | |
This would mean fundamental change to our scheduler, which implies a lot of effort. You may use a workaround using "run after job scripts", so schedule the first job with Bareos and then trigger subsequent jobs by scripts. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2013-10-03 17:27 | cm@p-i-u.de | New Issue | |
2013-10-03 17:36 | cm@p-i-u.de | Note Added: 0000685 | |
2013-10-07 13:26 | mvwieringen | Severity | minor => feature |
2013-10-11 16:36 | maik | Note Added: 0000698 | |
2013-10-11 16:36 | maik | Status | new => closed |
2013-10-11 16:36 | maik | Assigned To | => maik |
2013-10-11 16:36 | maik | Resolution | open => won't fix |