On Tuesday 23 February 2010 19:09:49 Phil Stracchino wrote:
> On 02/23/10 06:32, Silver Salonen wrote:
> > I consider it a bug, but looks like devs do not. Any opinions?
> 
> I ran into this problem when I first upgraded to 3.0.3.  It turned out
> to be a configuration issue.  Make sure you have the desired level of
> concurrency enabled in ALL applicable resources (i.e, you need 
"Maximum
> Concurrent Jobs = 20" set for the SD both in your bacula-sd.conf file
> AND in your bacula-dir.conf file).  If you have different values set in
> different places, the *lowest* will end up being used.

I'm talking about same jobs running on the same device concurrently. This 
was not possible in Bacula < 5.0 at all.

I have all the correct limits set in every possible place and as I've written 
before - if any other limit would take effect, the jobs wouldn't be waiting 
with message "is waiting for storage ...".

--
Silver

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users