JobBytes is the number of bytes sent from the FD (client) to the SD. If you are using Bacula's software compression (the compression option in the Fileset), then that will be the size after compression.
Bacula's software compression is always done in the FD. You can control concurrency of backups using the various "Maximum Concurrent Jobs" options. __Martin >>>>> On Wed, 7 Feb 2018 12:02:56 +0000, Adam Weremczuk said: > > Hi all, > > Last night a tape filled so I'm spending most of today investigating the > cause and ensuring the next run completes fine. > When executing "list jobname=" from the console I'm presented with 2 > columns: JobFiles and JobBytes. > > Is JobBytes expected to show the volume read from the client or written > to the tape? > In the latter the count is after compression, right? > > On that note: Is compression always performed on the server or can it be > done on clients? > It could make sense to iterate over all clients first and instruct them > to start compressing. > Then they start reporting as ready to the director and data transfers begin. > > Please advise. > > Regards > Adam > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
