Is there a way to limit the number of queued Incremental jobs to 1, while still allowing other types (eg. Full or VirtualFull) to be queued up? Historically I've used these parameters to prevent new jobs from being queued up, when one is already running (in the Job or JobDefs definition):
> Maximum Concurrent Jobs = 1 > Allow Duplicate Jobs = no If a job is still running when the next job comes up on the schedule, that new job is then rejected with a "Duplicate job not allowed." That's the behavior I'd like, if the new job is an Incremental. But if it's something else (eg. Full or VirtualFull), I'd like it to be allowed to queue up, and wait for the incremental to finish (due to the "Maximum Concurrent Jobs = 1"), before running. Is this possible? Is my explanation clear? Thanks, Lloyd -- Lloyd Brown HPC Systems Administrator Office of Research Computing Brigham Young University http://marylou.byu.edu _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
