In response to "Dan Horne" <[EMAIL PROTECTED]>:
> > What happens if you define an autochanger resource and make
> > the two drives part of an autochanger? Even though there is
> > no _true_ autochanger, it seems to me that the logic would be
> > there to make it do what you want.
>
> I don't see how this would work, since an autochanger is a single
> physical device (eg: /dev/nsa0) whereas the two tape drives are two
> separate physical devices (/dev/nsa0 and /dev/nsa1). The autochanger
> setup would just send a signal to the single device to insert a new
> tape, but I need to be able to overflow onto a second physical device.
It doesn't have to be. Some autochangers have multiple drives, and they
present themselves as /dev/nsa0, /dev/nsa1 ... /dev/nsan. Bacula has
the capability to work with this type of configuration.
Again, I haven't tried it, so it still might not work, but not for the
reason you've stated. See below ...
> From what I can see, this can't be done currently. Logically, it seems
> that in order for this to work, bacula would need a new resource type in
> the Storage Daemon config. Possibly a "DevPool" resource. In Backup
> Exec, all devices in a pool needed to be the same, but because of the
> way bacula works it doesn't seem like this would be a necessity. A
> pseudo-example might look like this:
>
> DevPool {
> Name = "DevPool1"
> ...
> }
>
> Device (
> Name = "TapeDrive1"
> DevPool = "DevPool1"
> DevPoolPriority = 1
> ...
> }
>
> Device (
> Name = "TapeDrive2"
> DevPool = "DevPool1"
> DevPoolPriority = 2
> ...
> }
>
> That could create a device pool that could be referenced as a backup
> device in a job (the where), which would backup first to the lowest
> DevPoolPriority device. When that device is full, it will begin using
> the second lowest DevPoolPriority device, etc. Just sort of a wishlist
> sort of thing. Anyone else think this would be a good thing? It would
> save on having to purchase an autoloader if you already have multiple
> independent tape drives.
>
> I'll stop dreaming now.
No. Don't. I really _believe_ that what you want to do can be done with
the autochanger interface. Just replace "DevPool" with "Autochanger" and
roll with it. See the examples:
http://www.bacula.org/rel-manual/Storage_Daemon_Configuratio.html#SECTION000166000000000000000
--
Bill Moran
Collaborative Fusion Inc.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
