On Fri, 28 Jul 2006, Kern Sibbald wrote: >> 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 there >> 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 don't mind it doing that. What I do mind is that it will demand that volume in preference to purged tapes already in the changer. In the case I'm thinking of, I had loaded the oldest purged tapes into the changer, but overnight pruning resulted in several other volumes becoming purged and therefore ending up as recycle candidates too. > I can think of two possible solutions: > > 1. Implement a new directive (horrors) that says recycle only InChanger > volumes. It's not such a bad idea, to be honest, as long as it's only InChanger and status = Purged > 2. Mark all volumes that are not in the changer as Disabled, then they will > not take part in the recycle algorithm -- at least when the code is finally > written, since currently very few of the SQL statements are Enable/Disable > aware (new feature of 1.39). Currently, you could change the VolStatus to > something like Archive or Read-Only. What I did was to change the Inchanger tapes to status recycle by hand. AB ------------------------------------------------------------------------- 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
