Hi, 22.04.2009 22:47, Benjamin Minshall wrote: > Arno Lehmann wrote: >> Alternatively, you could also create a "fake" autochanger (beware - >> work included:-) with three slots, where each slot actually represents >> a drive. Basically, you'd create a symlink pointing to the drive you >> actually want to use, and manage that link with the changer script you >> use. > > I see, so in this case, I would create a single-drive autochanger which > points to /dev/faketape and write a replacement script for mtx-changer > which changes the target of the /dev/faketape link to /dev/st[0-2] based > on the requested tape?
Yes, that's the idea. > Along those same lines, would it be possible to create a three drive > autochanger with three slots (or zero slots?) and still use Bacula's > internal tape management features? That should be possible, yes. > Since there are three loaded tapes > and three drives in the autochanger it should never request a tape to be > loaded, right? Well... a job in Bacula uses one storage device for all its lifetime, so if one tape is not sufficient, that latter approach won't help you. In other words, while you could use such a setup, you wouldn't gain anything by it. Arno > Thanks. > -- Arno Lehmann IT-Service Lehmann Sandstr. 6, 49080 Osnabrück www.its-lehmann.de ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
