Hi,
Tom Boyda wrote:
Looking into upgrading - will I be required to upgrade my windows
clients from 1.37.32 to be able to use 1.37.38 director and storage
daemon?
I *think* not:
#ver
goblin-dir Version: 1.37.38 (04 September 2005)
#status client=ork-fd
Connecting to Client ork-fd at ork:9102
ork-fd Version: 1.37.30 (14 July 2005) i586-pc-linux-gnu suse 7.1
...when it works with 1.37.30 I guess it would work with .32, too. for
some reason I didn't have such a combination running, but I do have a
.36 version client. No problems.
...
recycled, and thus never requested. Although, with current Bacula
status, this would not pose a problem it would work cleaner.
Would that be changing the "VolStatus" field to Archive?
Well, what I suggeste was to use a script which sets the VolStatus, and
of course you could set it it whatever you want. I'd use Archive for
offsite stored volumes.
Well, after about 90 days the old offsite tapes will come back and be
put into the changer and I would like those tapes to be recycled and
reused, if the tapes are marked Archive will bacula still honor the
file/job retention for the volume being returned to the changer?
No, it won't. I will only automatically consider Full, Used, Append,
Purged or Recycle status when looking for a tape.
But changing the Volume status when checking the drives in doesn't
require much effort - just another little script :-) By the way, with
barcodes and a barcode reader as well as a simple web-frontend this
could really be quite easy.
I am wondering when the tape will be marked "Used"?
Only when bacula actually decides it should use them for writing. That
is, if you remove them from the autochanger before the 3 days are over,
Bacula knows that there are other volumes better suited for use and
uses
those first.
Okay, so at the next monthly full backup bacula will look in the catalog
and see that Monthly01-001 has "Volume Use Duration" of 3 days and make
the Volume Status "Used" or "Archive" and use the next volume in the
Monthly01 pool. Is that correct?
Yes, but only when it decides that it could use that volume. If others
are found first - for example because they are in an autochanger slot
while Monthly01-001 is already unloaded - bacula will not have a closer
look at Monthly01-001 and so it won't mark it Used.
Will this be a problem if the tape is not in the changer and bacula
wants to change the tape status?
No, the status is purely a catalog thing.
What Am I doing wrong? Or what have I missed that "Volume Use
Duration"
is not marking the tapes as used?
Nothing, everything is all right...
Now, I imagine one could modify bacula to do how you want it to work,
but in your situation, I'd make things differently.
I just need to get a handle on how bacula wants to work and make my
schedule fit around bacula so that bacula will handle tape rotation and
recycling by itself with the least amount of intervention on my part or
the operators part.
I found that bacula does this quite well, although things like temporary
off-site storage need intervention. Of course you could also set a
longer retention time, for example 90 days, and then the tapes would not
be recycled while they are offsite.
Should I just mark the tapes used by hand?
Personally, I think "by hand" and "reliable backup" are rather
incompatible, so - No.
I agree.
Really I want our operator to pull the tapes and put them in the
offsite
box without my intervention. And when we get up to our cycle period
when
the "old" full monthly backup tapes return they will be put back into
the changer so they can be recycled and reused.
I'd do the following:
Create a script that scan the catalog and markes all tapes as Archive
which you will move offsite, in your case all Full backup tapes that
are
in Full or Append or Used state and in the loader. Send a list with the
tape names and slot number to the operator, requesting to remplace
these
tapes. Mark the slots affected as empty.
When you say "Mark the slots affected as empty" do you mean to have the
script changed the InChanger field to 0?
I set InChanger=0,Slot=0. With the development version, you'd probably
also have to consider the assigne StorageId.
Finally, create a script that uses baculas 'update slots' command to
re-scan the autochanger, and have that execute when the operator
acknowledges the tape change.
Or, if you have a library with mailslot or removable magazine, let your
script automatically eject the tapes that should be moved offsite.
Might take a day or two to get this working, but afterwards you don't
have to do hese things manually, and your operator only needs to
operate, not to think :-)
Thank you,
Tom.
----
Thomas Boyda
Consultant
Daou Systems, Inc.
[EMAIL PROTECTED]
276-739-2314
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
