On 6/11/24 10:45 AM, Marco Gaiarin wrote:
Sorry, i really don't understand and i need feedback...
I've read many time that tapes are handled better as they are, sequential
media; so they need on storage:
Maximum Concurrent Jobs = 1
Hello Marco,If you are using DataSpooling for all of your jobs, this setting is somewhat redundant because Bacula will de-spool exactly one Job's Data Spool file at a time.
With DataSpooling enabled in all jobs, the only "interleaving" that you will have on your tapes is one big block of Job 1's de-spooled data, then maybe another Job 1 block, or a Job 2 block, or a Job 3 block, and so on, depending on which Job's DataSpool file reached the defined maximum Job Spool size at particular times throughout the backup window, or when one hits the total MaximumSpool size and begins de-spooling.
If, on the other hand, you have many clients and enough network bandwidth, you can disable Data Spooling, and increase the Ta
pe Drive's MaximumConcurrentJobs setting and Bacula will stream and interleave the data from all the concurrently running jobs.But, you can probably never really guarantee that all jobs will be streaming enough data concurrently to saturate the link to the Tape Drive, so using DataSpooling to *fast*, local, SSD, flash, or NVMe etc drives is probably a better and more consistent solution.
Hope this helps! Bill -- Bill Arlofski w...@protonmail.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
