Mandi! Josh Fisher via Bacula-users
  In chel di` si favelave...

> 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.

Ok, doing some more test in real condition (and still arguing on why logs
row are not ordered by date...) i've splitted a job:

 root@lnfbacula:~# cat /var/log/bacula/bacula.log | grep '2251[67]' | sort
 21-Jun 20:00 cnpve3-sd JobId 22516: Volume "AAJ664L9" previously written, 
moving to end of data.
 21-Jun 20:00 lnfbacula-dir JobId 22516: Using Device "LTO9Storage0" to write.
 21-Jun 20:00 lnfbacula-dir JobId 22517: Start Backup JobId 22517, 
Job=VEN-CN-CNPVE3Sedi.2024-06-21_20.00.00_32
 21-Jun 20:00 lnfbacula-dir JobId 22517: Using Device "LTO9Storage0" to write.
 21-Jun 20:02 cnpve3-sd JobId 22516: Ready to append to end of Volume 
"AAJ664L9" at file=8.
 21-Jun 20:02 cnpve3-sd JobId 22516: Spooling data ...
 21-Jun 20:02 cnpve3-sd JobId 22517: Spooling data ...

Clearly job use the same schedule, so start at the same time.

 21-Jun 20:48 cnpve3-sd JobId 22516: User specified Device spool size reached: 
DevSpoolSize=257,699,937,020 MaxDevSpoolSize=257,698,037,760
 21-Jun 20:48 cnpve3-sd JobId 22516: Writing spooled data to Volume. Despooling 
144,990,358,762 bytes ...
 21-Jun 20:48 cnpve3-sd JobId 22517: User specified Device spool size reached: 
DevSpoolSize=257,699,937,020 MaxDevSpoolSize=257,698,037,760
 21-Jun 20:48 cnpve3-sd JobId 22517: Writing spooled data to Volume. Despooling 
112,709,578,258 bytes ...

OK; MaximumSpoolSize reached, both jobs stop.

 21-Jun 20:56 cnpve3-sd JobId 22517: Despooling elapsed time = 00:08:50, 
Transfer rate = 212.6 M Bytes/second
 21-Jun 20:56 cnpve3-sd JobId 22517: Spooling data again ...

One of the job start and complete spooling; when end the spooling, start
immediately to despool again.

 21-Jun 21:08 cnpve3-sd JobId 22516: Despooling elapsed time = 00:11:59, 
Transfer rate = 201.6 M Bytes/second
 21-Jun 21:08 cnpve3-sd JobId 22516: Spooling data again ...

The other, after the former end despooling, start the despooling.

So, for job 22517 the spooling start at 20:56, while for job 22516 at 21:08;
so for 12 minutes i've effectively TWO jobs running, one despooling and one
spooling...

 21-Jun 22:05 cnpve3-sd JobId 22516: User specified Device spool size reached: 
DevSpoolSize=257,698,889,378 MaxDevSpoolSize=257,698,037,760
 21-Jun 22:05 cnpve3-sd JobId 22516: Writing spooled data to Volume. Despooling 
128,134,307,647 bytes ...
 21-Jun 22:05 cnpve3-sd JobId 22517: User specified Device spool size reached: 
DevSpoolSize=257,699,937,966 MaxDevSpoolSize=257,698,037,760
 21-Jun 22:05 cnpve3-sd JobId 22517: Writing spooled data to Volume. Despooling 
129,565,630,319 bytes ...
 21-Jun 22:14 cnpve3-sd JobId 22516: Despooling elapsed time = 00:09:27, 
Transfer rate = 225.9 M Bytes/second
 21-Jun 22:14 cnpve3-sd JobId 22516: Spooling data again ...
 21-Jun 22:24 cnpve3-sd JobId 22517: Despooling elapsed time = 00:10:08, 
Transfer rate = 213.1 M Bytes/second
 21-Jun 22:24 cnpve3-sd JobId 22517: Spooling data again ...

 21-Jun 23:07 cnpve3-sd JobId 22516: User specified Device spool size reached: 
DevSpoolSize=257,698,889,378 MaxDevSpoolSize=257,698,037,760
 21-Jun 23:07 cnpve3-sd JobId 22516: Writing spooled data to Volume. Despooling 
161,555,952,974 bytes ...
 21-Jun 23:07 cnpve3-sd JobId 22517: User specified Device spool size reached: 
DevSpoolSize=257,699,937,966 MaxDevSpoolSize=257,698,037,760
 21-Jun 23:07 cnpve3-sd JobId 22517: Writing spooled data to Volume. Despooling 
96,143,984,992 bytes ...
 21-Jun 23:17 cnpve3-sd JobId 22516: Despooling elapsed time = 00:09:50, 
Transfer rate = 273.8 M Bytes/second
 21-Jun 23:17 cnpve3-sd JobId 22516: Spooling data again ...
 21-Jun 23:28 cnpve3-sd JobId 22517: Despooling elapsed time = 00:11:13, 
Transfer rate = 142.8 M Bytes/second
 21-Jun 23:28 cnpve3-sd JobId 22517: Spooling data again ...

the same schema repeated some times.

at some time one of the two jobs end, and so the other continue.

 22-Jun 18:51 cnpve3-sd JobId 22516: User specified Device spool size reached: 
DevSpoolSize=257,698,373,454 MaxDevSpoolSize=257,698,037,760
 22-Jun 18:51 cnpve3-sd JobId 22516: Writing spooled data to Volume. Despooling 
114,582,356,345 bytes ...
 22-Jun 18:58 cnpve3-sd JobId 22517: Despooling elapsed time = 00:09:51, 
Transfer rate = 242.1 M Bytes/second
 22-Jun 18:58 cnpve3-sd JobId 22517: Elapsed time=22:56:52, Transfer rate=26.32 
M Bytes/second
 22-Jun 18:58 cnpve3-sd JobId 22517: Sending spooled attrs to the Director. 
Despooling 1,526,278,711 bytes ...
 22-Jun 19:05 cnpve3-sd JobId 22516: Despooling elapsed time = 00:06:34, 
Transfer rate = 
 22-Jun 19:05 cnpve3-sd JobId 22516: Spooling data again ...


Sicerily, i hoped there's some more 'smart' way to manage despooling in
bacula; the only way to boost performance seems to me tune MaximumSpoolSize
so tapes it takes more or less the same time to despool of the other
tasks(to) to spool, so dead time interleaved can be minimized.

Seems an hard task. ;-)

-- 




_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to