In the message dated: Tue, 19 Sep 2006 13:12:48 BST,
The pithy ruminations from Alan Brown on
<Re: [Bacula-users] Proper Autochanger configuration with different drives in s
ame changer> were:
=>
=> On Mon, 18 Sep 2006, Pietari Hyv=E4rinen wrote:
=>
=> > Hi!
=> > Our Autochcanger ( dell136T) is connected to four tape drives.
=> > Two of the are older LTO-2 and the rest are LTO-3 capable drives.
=> > How I define bacula-dir to understand that there are two of each
=> > drives in same autochanger?
=>
=> You have the bacula-sd definition right... BUT...
=>
=> Bacula's current state means you can only use LTO3 tapes in the LTO3=20
=> drives and LTO2 tapes in the LTO2 drives.
Wow.
=>
=> Bacula has no way of knowing that you can use LTO2 tapes in the LTO3=20
=> drives. I've been requseting that functionality for a while, as we have=20
=> always planned to install LTO3/LTO4 drives in our robot when hardware=20
=> upgrade time happens.
Thank you very much for bringing this up and giving an explanation.
We're about to be getting an LTO3 drive, and I was planning to continue to use
our stock of LTO2 tapes for incrementals, and add some LTO3 media for full
backups. This limitation of bacula may cause serious changes to that plan.
=>
=>
=> The main stumbling block is really in bacula-dir
=>
=> # Definition of LTO-2 tape storage autochanger
=> Storage {
=> Name =3D Autochanger
=> Autochanger =3D yes
=> Address =3D XXXXXX # N.B. Use a fully qualified name here
=> SDPort =3D 9103
=> Password =3D "supercalafragilisticexpialidocious"
=> Device =3D Autochanger # must be same as Device in=
=> Storage daemon
=> Media Type =3D LTO-2 # must be same as MediaType in=
=> Storage daemon
=> Maximum Concurrent Jobs =3D 15
=> }
=>
=> As you can see, the mediatype is locked into the changer entry and=20
=> currently the only way to define LTO3 jobs is to create another changer -=
=> =20
=> which will probably cause database issues with "update slots", etc.
Hmmm... What if you define all the media types as LTO3...does bacula check the
media type when loading a volume, or just the volume name?
If bacula loads an LTO2 tape into what it thinks is an LTO3 drive, will the
backup proceed normally, except that the data will reach EOT earlier than
expected?
Kern --
I will be able to use the LTO3 autochanger, and a new server (Linux,
RHEL4, x86_em64t, mysql5) that will eventually host Bacula, for beta
testing new versions, providing an additional platform to resolve this
issue, etc. Please contact me off the list if there are specific things
you'd like run there.
Thanks,
Mark
=>
=>
=> > We are using bacula version 1.38.11-3.
=> >
[SNIP!]
The information contained in this e-mail message is intended only for the
personal and confidential use of the recipient(s) named above. If the reader of
this message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified that you have
received this document in error and that any review, dissemination,
distribution, or copying of this message is strictly prohibited. If you have
received this communication in error, please notify us immediately by e-mail,
and delete the original message.
-------------------------------------------------------------------------
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
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
