On Wed, Feb 24, 2010 at 8:07 AM, Silver Salonen <sil...@ultrasoft.ee> wrote: > 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. > > Do I get it right, that you have multiple jobs using the same device > concurrently? >
I have had this work for over 5 years with bacula. Jobs need to go to the same volume however because a storage device can only load a single volume. I use tape mostly so I do not see this as a big issue. I have a multi-drive autochanger that takes care of using different volumes concurrently. John ------------------------------------------------------------------------------ Download Intel® 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
