On 08/18/2017 07:13 AM, muha...@assistanz.com wrote: > Helo Heitor, > >> "Use Volume Once" is an explicitly non-recommended directive by Kern >> himself. You should use "Maximum Volume Jobs=1" in the pool resource. > > Thank You for the above change,and this means only one job will run in that > pool?.
I believe so. A "volume" is a tape in a tape drive, if you want to write 50 "volumes" at once you need 50 "drives" -- devices. > >> Another way, if you want different backup jobs to ALWAYS write in different >> sets of volumes, is scheduling them to different pools. > > so instead of device we should maintain pools for all new backup jobs. Will > the increase in number of pools will not be an another problem, like 50 pools > for 50 jobs. I've hard time imagining a scenario in which that would be useful. I'm assuming you're backing up to disk, not to actual tapes. You may be able to get somewhere by spooling jobs (we use SSDs here), with a large enough spool drive you could potentially spool all 50 jobs in parallel. If you have bacula auto-create volumes, you may be able to get job id into volume label somehow... -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
