On 10/31/2011 12:44 PM, Sébastien WENSKE wrote:
Hi John,
Yes, there are a lot of jobs that starts at the same time for the same pool.
50 jobs ----\ 3 file devices /--------> pool A
---> DISKCHANGER------
50 jobs ----/ 20 slots \--------> pool B
My goal is to have concurrent running jobs.
" Warning: Volume "F0005" wanted on "VT-0"
(/tmp/autochanger/drive0) is in use by device "VT-1""
Is it possible to tell the autoloader to takes an appendable or any other
available volume when I try to access an IN USE volume ?
Set "Maximum Volume Jobs = 1" in the Pool resource in bacula-dir.conf.
This means that a volume can only be assigned to a single job. Bacula's
volume selection is atomic, so even when jobs are started at the same
time and writing to the same pool, each job will be assigned a different
volume. Every job will have its own volume. Also leave "Prefer Mounted
Volumes = no", which allows more than one volume from the same pool to
be used at the same time.
Then for each virtual device associated with the Autochanger, set
"Maximum Concurrent Jobs = 1" in its Device resource configuration in
bacula-sd.conf. Job assignment is also atomic, so that ensures jobs
starting at the same time get assigned to different virtual devices. I'm
not sure that this setting is absolutely required when the devices
belong to an autochanger, but it doesn't seem to hurt anything.
**
------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook
in minutes. BlackBerry App World™ now supports Android™ Apps
for the BlackBerry® PlayBook™. Discover just how easy and simple
it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
