Kern,

I mistyped the directive. It is "Accept Any Volume." Am I to understand that this is obselete, or did I merely accidentally refer to an old name? I read it in the manual:

*Accept Any Volume = <yes|no>*
   This directive specifies whether or not any volume from the Pool may
   be used for backup. The default is *yes* as of version 1.27 and
   later. If it is *no* then only the first writable volume in the Pool
   will be accepted for writing backup data, thus Bacula will fill each
   Volume sequentially in turn before using any other appendable volume
   in the Pool. If this is *no* and you mount a volume out of order,
   Bacula will not accept it. If this is *yes* any appendable volume
   from the pool mounted will be accepted.

   If your tape backup procedure dictates that you manually mount the
   next volume, you will almost certainly want to be sure this
   directive is turned on.

   If you are going on vacation and you think the current volume may
   not have enough room on it, you can simply label a new tape and
   leave it in the drive, and assuming that *Accept Any Volume* is
   *yes* Bacula will begin writing on it. When you return from
   vacation, simply remount the last tape, and Bacula will continue
   writing on it until it is full. Then you can remount your vacation
   tape and Bacula will fill it in turn.


...I have already read the manual, but I want to make sure that I am not confused. I see that I had misinterpreted this particular section, probably in part because of a paradigm shift from OmniBack. OmniBack has a very similar option (strict allocation) that when enabled means "Accept Any Volume = no." Also, from this blurb, it looks like this may not do what I want it to, because I don't want the user to be able to throw whatever tape in there they like, only the most appropriate one. It sounds like what I might need to do is go and run something once in awhile that says "recycle all recyclable volumes," however I think that the volume selection order still might rather have a blank appendable tape than a tape that has data and is ready to be recycled.

---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | | Ryan Novosielski - User Support Spec. III
|$&| |__| |  | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.| IST/AST - NJMS Medical Science Bldg - C630


Kern Sibbald wrote:

On Wednesday 24 August 2005 20:34, Ryan Novosielski wrote:
Can someone explain to me the use of Use Any Volume?

That directive is obsolete and if I am not mistaken not used anywhere.

The rest is in the manual, or I leave the list to respond.

What I want is for bacula to use the tape with the lowest ID that is writable. I definite
writable as any volume that is in a state that will allow it to be
written to (including a tape that contains data but whose retention time
has passed). I have 11 daily tapes, and after my full backup, I want
tape #1 to be used. However, Bacula often wants tape 10 or 11 as they
did not get used during the last cycle at all. If I want the drive to
take tape 1, I have to disable the higher numbered tapes.

Is there a way to do what I want without scripting? It's not readily
apparent.




-------------------------------------------------------
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

Reply via email to