Hello,
Bacula has its own way of doing things by default, and in that way of
running Bacula, it works very well. In addition, you can *force* it to
work out of its normal design scope, and it will work, but you will have
more problems. In either creating 500 virtual devices or 1000 Pools you
are forcing Bacula to work outside its design parameters, so you are
likely to run into many problems, including performance problems.
Good luck,
Best regards,
Kern
On 21/08/2017 06:35, muha...@assistanz.com wrote:
Hi Kern and all,
Thank You so much for the response.
So its better to configure 500 virtual devices in the SD configuration, rather
than configuring more than 10,000 pool.
Either i need 500 virtual devices, because there is a chance of running 500
jobs at a time,so to separate the volume for each job i may need 500 virtual
devices already configured.
Regards,
Muhasin
----- Original Message -----
From: "Kern Sibbald" <k...@sibbald.com>
To: muha...@assistanz.com, "Dimitri Maziuk" <dmaz...@bmrb.wisc.edu>
Cc: "bacula-users" <bacula-users@lists.sourceforge.net>
Sent: Sunday, August 20, 2017 2:38:01 PM
Subject: Re: [Bacula-users] Jobs are writing to wrong volumes.
Hello,
There is no limitation on the number of Pools in Bacula, but the code
was written assuming a relatively small number of Pools (probably less
than say 10,000). Consequently when you use more Pools, you may find at
some point, probably well beyond what you are planning, that the Pool
access algorithms need to be adjusted. This was for example a problem
with having a huge number of Jobs (e.g. more than several thousand).
For Jobs, I rewrote the algorithms for accessing Job resources a number
of years ago, which essentially eliminates the performance problems with
the old linear algorithms.
Best regards,
Kern
On 19/08/2017 07:59, muha...@assistanz.com wrote:
Hi,
Now I have planned to use dedicated pool for each job, i think this will not
create a problem. Creating a total of 1000+ pools will create a problem in
bacula?. I do not see any limitations for number of pools creation in any doc.
Regards,
Muhasin C.M
Systems Engineer R & D
Assistanz Networks Pvt LTD
----- Original Message -----
From: "Dimitri Maziuk" <dmaz...@bmrb.wisc.edu>
To: "bacula-users" <bacula-users@lists.sourceforge.net>
Sent: Friday, August 18, 2017 11:04:37 PM
Subject: Re: [Bacula-users] Jobs are writing to wrong volumes.
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...
------------------------------------------------------------------------------
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
