On 6/20/24 18:58, Bill Arlofski via Bacula-users wrote:
On 6/20/24 8:58 AM, Marco Gaiarin wrote:
Once that is hit, the spoofles are written to tape, during which active
jobs have to wait because the spool is full.
There's no way to 'violate' this behaviour, right?! A single SD process
cannot spool and despool at the same time?
An SD can be spooling multiple jobs wile *one* and only one Job spool
file is despooling to one drive.
Add another drive and and the same is still true, but the SD can now
be despooling two jobs at the same time while other jobs are spooling,
and so on as you add drives.
Except when the MaximumSpoolSize for the Device resource is reached or
the Spool Directory becomes full. When there is no more storage space
for data spool files, all jobs writing to that device are paused and the
spool files for each of those jobs are written to the device, one at a
time. I'm not sure if every job's spool file is written to tape at that
time, or if the forced despooling stops once some threshold for
sufficient space has been freed up. So, more accurately, other jobs
continue spooling IFF there is sufficient space in the spool directory.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
