Re: [Bacula-users] Concurrent jobs pooled for no reason?

[Uwe S. <uwe...@ni...>]

On Fri, Jun 08, 2012 at 10:28:03AM +0200, Julien Cochennec wrote:
> Hi,
> New to this list and bacula newbie, here almost everything works great, 
> backup around 50 clients, except one thing.
> I followed this example 
> http://www.bacula.org/fr/dev-manual/Basic_Volume_Management.html#SECTION001220000000000000000.
> It's about concurrent disk jobs.
> The problem is that although I did separate devices, pools, full-pools, 
> diff-pools, inc-pools, storages, jobs so that everything should be 
> independent, Jobs are still waiting for the first one to end before they 
> begin, what did I miss? It looks like I'm very close but can't find the 
> reason why they still "pool".
> Do I have to do differents schedules too?
> I want jobs to begin all together, being independent.
> Thanks for your help, Bacula rocks!
> 
> 

Hello Julien, 

what are your settings for "Maximum Concurrent Jobs" for storage, sd,
director, fd's and so on? What exactly is Bacula waiting for (the
output of "stat dir" during a backup run should give you an idea
what's blocking). 

All the best & HTH, 

Uwe