All versions since 1.38, at least up to 2.2.8. I have observed that if the director is not running at the time that a full backup is scheduled, then the next backup to be performed when the director
You're almost right. It's possible to almost get into that situation, but Bacula will detect and prevent it. Whenever an incremental or differential job runs, it checks the catalogue for a matching f
Ah yes, that is what is supposed to happen, but it doesn't always work. I just noticed a situation where five jobs were scheduled to do fulls on the 12th of each month, but for whatever reason the di
This behaviour is flawed for large backups. If repeat failed levels is enabled, then if an incremental is scheduled and the full is still running the increental will turn into a full - same with the
I have hit the same problem in my environment. Allthough not a perfect solution I set the concurrency of the client fd to 1 and set the Max Wait Time to 23 hours for the jobs. This makes sure I dont
I also believe there is a feature that prevents multiple instances of the same job from entering the queue. I do not recall if this is now implemented. -- Dan Langille -- http://www.langille.org/ --