Please always copy the list.
Hopefully someone will explain it to you.
On Friday 28 July 2006 22:07, mark.bergman@... wrote:
> In the message dated: Fri, 28 Jul 2006 21:46:23 +0200,
> The pithy ruminations from Kern Sibbald on
> <Re: [Bacula-users] Maximum Concurrent Jobs for a device> were:
> => On Friday 28 July 2006 18:01, Alan Brown wrote:
> => > On Fri, 28 Jul 2006, Kern Sibbald wrote:
> => >
> => > > There are certain limitations in version 1.38.x, that are explained
> => > > release notes I think -- mainly, if a tape is in drive 2 and Bacula
> => > > writing on drive 1 and then wants to write on the tape that is in
> => it
> => > > will unload it from drive 2 and load it into drive 1 -- it works, but
> => not
> => > > optimal.
> => >
> => > One of the more annoying problems is that it will insist on recycling
> => > tapes which are not in the changer, then block on loading them, when
> => > are purged recycling-candidate tapes available in the changer.
> => Yes, this is probably to be expected since the current algorithm always
> => recycles the oldest volumes.
> => I can think of two possible solutions:
> => 1. Implement a new directive (horrors) that says recycle only InChanger
> => volumes.
> => 2. Mark all volumes that are not in the changer as Disabled, then they
> => not take part in the recycle algorithm -- at least when the code is
> => written, since currently very few of the SQL statements are
> => aware (new feature of 1.39). Currently, you could change the VolStatus
> => something like Archive or Read-Only.
> How is  different from ?
> 3. Enable bacula to report on the tapes that it will use in the future, so
> they can be manually loaded into the changer, eliminating the problem.
> (Not precisely a solution, but a work-around).
> => >
> => > AB
> => >
> Mark Bergman mark.bergman@...
> System Administrator
> Section of Biomedical Image Analysis 215-662-7310
> Department of Radiology, University of Pennsylvania
> 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.