On Tuesday 23 February 2010 20:45:26 Martin Simmons wrote: > I think you have the concept backwards -- it is designed to prevent > concurrency on that device rather than allowing more of it. > > The default allows an unlimited number of jobs to be queued (or run > concurrently on a single volume). The new resource allows you to force jobs > to run on another "compatible drive" instead.
No, the default for devices has always been to allow only 1 job. In Bacula 5.0 there's a new directive for devices: "Maximum Concurrent Jobs". That should allow multiple jobs to run on the same device. > You seem to be using different volumes for each job, so they can't run > concurrently on the same device anyway. Actually I don't want to run the same job on the same device concurrently, but to run multiple different jobs on the same device. I use disk-based backups, so device in my case is a folder. With device allowing only 1 job to run, to be able to run different jobs concurrently into the same folder (aka device) I have to define separate devices for every job, which seems quite.. redundant. With device allowing multiple jobs concurrently I can define just one device (eg. pointing to /backup/silver) and run every job of the same client on that device. -- Silver > >>>>> On Tue, 23 Feb 2010 13:32:02 +0200, Silver Salonen said: > > > > I consider it a bug, but looks like devs do not. Any opinions? > > > > http://bugs.bacula.org/view.php?id=1508 > > > > -- > > Silver > > > > On Tuesday 16 February 2010 09:56:21 Silver Salonen wrote: > > > Hi. > > > > > > In 5.0 there is directive "Maximum Concurrent Jobs" for devices too, which > > > should mean that it's now possible to run multiple jobs simultaneously on > > the > > > same device and therefore on the same storage. Right? > > > > > > I have "Maximum Concurrent Jobs = 20" set for SD, for 'storage-silver' and > > for > > > 'device-silver'. > > > > > > I made a copy of a job 'silver-test', changing only its name to 'silver- > > > test2', so it uses the same fileset, same storage etc. > > > > > > When I run these jobs in parallel, I see the one ran a bit later waiting for > > > the 1st to end: > > > > > > ====================================================================== > > > 56776 Full silver-test.2010-02-16_09.49.31_41 is running > > > 56777 Full silver-test2.2010-02-16_09.49.31_43 is waiting on Storage > > > storage-silver > > > ==== > > > > > > Any clue why does it still wait on storage? > > > > > > -- > > > Silver ------------------------------------------------------------------------------ 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
