Hi,
On 5/23/2007 11:24 AM, Adam Cécile wrote:
> I "may" have found my problem :
>
> Here is my old setup :
>
> ### SD config:
> Autochanger {
> Name = Dell-PV132T
> Device = ULTRIUM-TD3-1
> Device = ULTRIUM-TD3-2
> Changer Command = "/etc/bacula/scripts/mtx-changer %c %o %S %a %d"
> Changer Device = /dev/sg2
> }
> Device {
> Name = ULTRIUM-TD3-1
> Drive Index = 0
> Media Type = LTO3
> Archive Device = /dev/nst0
> AutomaticMount = yes;
> AlwaysOpen = yes;
> RemovableMedia = yes;
> Offline On Unmount = no;
> AutoChanger = yes
> }
>
> Device {
> Name = ULTRIUM-TD3-2
> Drive Index = 1
> Media Type = LTO3
> Archive Device = /dev/nst1
> AutomaticMount = yes;
> AlwaysOpen = yes;
> RemovableMedia = yes;
> Offline On Unmount = no;
> AutoChanger = yes
> }
>
> ### Director config
> Storage {
> Name = Autochanger
> Address = srv-mpp-lrs
> SDPort = 9103
> Password = "xxx"
> Device = Dell-PV132T
> Media Type = LTO3
> Autochanger = yes
> Maximum Concurrent Jobs = 2
> }
> Storage {
> Name = ULTRIUM-TD3-1
> Address = srv-mpp-lrs
> SDPort = 9103
> Password = "xxx"
> Device = ULTRIUM-TD3-1
> Media Type = LTO3
> Autochanger = yes
> Maximum Concurrent Jobs = 1
> }
>
> As you can see, in my director config "ULTRIUM-TD3-1" is defined. The
> aim of this trick is to be able to run jobs on one drive only.
Ok, that's understandable. I encountered a related problem myself, once...
> However, ULTRIUM-TD3-1 in director refers to a Device entry in sd, not
> an autochanger one. So I guessed, bacula ignore inchanger flag.
> Do you think I'm right ?
Yes.
> So I decided to define a second Autochanger ressources, with only on
> device associated on it. I hope this would fix the problem.
Uh... when you use both devices simultaneously, I'm not sure Bacula will
lock them as necessary.
I can only recommend to test this setup thoroughly.
> Regards, Adam.
>
I'm not sure there is an obvious solution to your demands.
Setting "Autoselect=No" in the SD device will keep the SD from
automatically using this tape drive, thus allowing you to use it for
manual jobs. This will, unfortunately, have the side effect that this
drive will not be used for concurrent jobs to the Autochanger :-(
I guess this problems needs another feature in Bacula :-)
What I imagine - without thorougly thinking this through - is that it
should be possible to address unique drives in an autochanger for jobs,
so that you can specify a drive to use but Bacula handles volume loading
etc.
This would be especially useful for manually starting jobs, I suppose,
but could also be used for scheduled ones.
A directive to use in the job resource, manual setup, and schedule like
"Use Drive = Drive number" would be helpful. I suppose this would
require another major rework of the reservation system, so I cold
imagine that Kern won't be too enthusiastic about implementing it soon :-)
Perhaps someone else can offer more ideas or experience - I don't have a
multi-drive autochanger here for testing purposes.
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
