In the message dated: Fri, 07 Jul 2006 12:14:05 +0200,
Kern Sibbald used the subject line
<Re: [Bacula-users] Volume Location Management>
and wrote:
=> Hello Arno,
=>
=> Nice work. Your screen shots look really nice. It think this will be a
=> popular feature. My comments are below:
Yes, I like the look. I've been waiting until I feel more comfortable with
bacula, and my installation is more stable, but my next project was to begin
archiving certain backups. Being able to track volume locations will be a great
help.
=>
=> On Thursday 06 July 2006 23:51, Arno Lehmann wrote:
=> > Hi,
=> >
=> > as promised, but later than I wanted, I have some sort of a preview of
=> > the Volume Location Management I'm implementing.
=> >
=> > Basic outline:
=> > - Tag each volume with a Location.
=> > - The Location assigned to a volume can be changed in a web interface.
Will it also be possible to assign tags via bconsole? Is the web a front-end to
bconsole, or does it provide unique functionality? I like the look of the
web interface very much, but until it's able to do every CLI function, I'll
probably stick with gconsole and bconsole.
=> > - A volume can be (temporarily) disabled. This is intended for loading /
=> > unloading operations, so you can have a catalog representing the actual
=> > autochanger inventory and still swap volumes without Bacula stumbling.
=> > - Bacula, as of version 1.40 (or the current development version) will
=> > respect the Volume disabling AFAIK.
=> > - Bacula does *not* respect Location tags, for example it will requests
=> > volumes tagges as "off-site storage".
=>
=> The above is correct, but I would reword it a bit. Bacula simply does not
=> interprete the location tags because the meaning of those tags is defined by
=> the user and, as a consequence, Bacula has no idea what is off-site,
damaged,
=> with currier, in Europe, or any other such tag that you could define.
=>
=> As long as the volume is disabled or marked archived, Bacula will not use
=> those volumes (not totally tested yet, but this is the plan ...).
Makes sense. In that case, could each volume location (user defined) have an
association (set in the GUI) to a state that Bacula understands (disabled/
archived/active)? When users define volume locations, they would also specify
the default state for volumes in that location.
For example, when I move tapes off-site and change their volume location to
"vault" or "Fred's garage", they are also changed to "archived" and Bacula will
stop asking for those volumes, and the tapes that are tagged with the location
"remote datacenter" remain in an active state.
=>
[SNIP!]
=>
=> Best regards,
=>
=> Kern
Thanks,
Mark
----
Mark Bergman [EMAIL PROTECTED]
System Administrator
Section of Biomedical Image Analysis 215-662-7310
Department of Radiology, University of Pennsylvania
http://pgpkeys.pca.dfn.de:11371/pks/lookup?search=mark.bergman%40.uphs.upenn.edu
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.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
