Hi,
I hate to reply to my own mail, but does nobody have an idea about
what I'm trying to do? ;)
If not, I'll submit an feature request. Because I think it is more
important to limit the number of concurent jobs on the drives, than on
the changer.
Ralf Gross schrieb:
>
> Hi,
>
> I have a 3 drive autochanger (bacula 2.2.8). Right now I configure
> each job to use one of the 3 drives, not the changer device.
>
>
> Storage {
> Name = Neo4100
> Address = ....
> SDPort = 9103
> Password = "wiped"
> Device = Neo4100
> Media Type = LTO4
> Autochanger = yes
> Heartbeat Interval = 5min
> Maximum Concurrent Jobs = 3
> }
>
> Storage {
> Name = Neo4100-LTO4-D1
> Address = ....
> SDPort = 9103
> Password = "wiped"
> Device = ULTRIUM-TD4-D1
> Media Type = LTO4
> Maximum Concurrent Jobs = 1
>
> [2 more drives]
>
> And in the client's job config I then use
>
> Storage = Neo4100-LTO4-D1
> or
> Storage = Neo4100-LTO4-D2
>
>
> Now I would like to go back to the more typical bacula approach, where I use
> the changer device in the client's job config.
>
> But I don't want concurrent jobs running on each drive. I want that it's
> possible to run 3 jobs on the changer (one for each drive), but only one on
> each drive at the same time.
>
> I could achieve that with different Priorities, but then these jobs are
> blocking jobs which are using other storage devices.
>
> Any ideas?
>
> Ralf
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
