On 09/20/17 09:12, Matthias Koch-Schirrmeister wrote: > Am 20.09.2017 um 13:47 schrieb Josh Fisher: >> >> Yes. Job attributes, file metadata, etc. that is to be stored in the db, >> are spooled to a file in /var/spool/bacula while the fd is actively >> transmitting data. After data transmission is complete (or if the spool >> file becomes large enough?), Bacula reads the cached metadata from the >> file and updates the db in batch mode. This is used both to speed db >> updates and to prevent constant db updates from slowing down collection >> of the fd's data.. > > In OpenBSD it appears to be a binary file named > <devicename><jobname><date>.spool. I've found a 55 MB file of the failed > backup in /var/bacula, but the current job's spool file is already about > 65MB and counting.
I'm curious — what back-end DB are you using? The MySQL DB driver appears to be written to spool attribute data in a temporary table in the database itself, which makes "despooling" an operation of copying all the attribute data from the database to the database. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
