One thing to keep in mind is that Bacula is designed to have multiple simultaneous jobs writing to multiple devices all at the same time. Jobs will wait without notification their turn.
However Bacula is not designed to deal with over committing your resources -- i.e. have multiple incompatible jobs waiting for a single tape drive or whatever.
What Bacula does is when a job starts, it attempts to reserve all the devices it will need (read/write) -- normally for Backup it is just one write drive. If all the devices are not available, it will back out the attempted reserve and wait. This allows other jobs to possibly obtain reservations on those devices, and thus prevents deadlocks.
If you are in a condition of over commitment (i.e. Bacula cannot reserve the needed devices), you are operating outside the design limits of Bacula. At that point, Bacula does its best to warn you even to the extent of being annoying that something is wrong, namely it cannot reserve the needed devices.
In general, this particular problem is resolved by doing proper scheduling so that you do not over commit your resources. I.e. schedule your jobs so that you do not have conflicting device demands.
Best regards,
Kern
On 2/11/20 6:07 PM, Radosław
Korzeniewski wrote:
Hello,
--pon., 10 lut 2020 o 14:50 Rao, Uthra R. (GSFC-672.0)[ADNET SYSTEMS INC] <uthra.r....@nasa.gov> napisał(a):
I have three Tape drives in the Tape Library. Say for example if two of the tape drives are busy running two different jobs from Pool A & B. If two more jobs are waiting to start from Pool C & D
First of all when designing a tape backup in Bacula you should consider lowering the number of defined Pools to the lowest acceptable level. This helps avoid resource shortage during the backup window. This is my recommendation based on multiple deployment experience.since only one Tape Drive is available the job from Pool C runs and the job from Pool D is still waiting for the Tape Drive and complains “ waiting to reserve a device” through email until a Tape drive become available to run the job.
I can fully understand that it complains about it as it cannot reserve the drive and has to wait. Could you explain what is your expected behavior in this case?
Thanks
Radosław Korzeniewski
rados...@korzeniewski.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
