On Wed, Feb 24, 2010 at 2:14 PM, Phil Stracchino <ala...@metrocast.net> wrote: > On 02/24/10 08:07, Silver Salonen 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? > > Yes indeed. I back up all of my clients simultaneously, and the jobs > all run concurrently to the same storage device. >
The main problem is the OP wants to use a different volume for each job or group of jobs. 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
