> [It would be appropriate to keep this conversation on-list]

Sorry, I should've hit "Reply to all"

> You should never have to.  PURGED and RECYCLED volumes will automagically
> be made appendable as needed.

I'd like for it to purge volumes older than two weeks so I know what
tapes I can use. Is it possible to forecast which tapes bacula will
purge/recycle?

> There's a good reason, and it rhymes like a carefully crafted poem.
> Did you read the section of the docs posted below?  If you did, you'd
> probably understand the rhyme and reason.

Step four of the recycling algorithm says "Try recycling any purged
Volumes." - This is very worrying. It should be "Try recycling any
purged volumes with InChanger=1"

> I suspect your pools are not set up optimally.

I just have the one pool:

Pool {
  Name = Daily
  Pool Type = Backup
  Recycle = yes                       # Bacula can automatically recycle Volumes
  AutoPrune = yes                     # Prune expired volumes
  Volume Retention = 12 days          #
#  Volume Use Duration = 23h
  Accept Any Volume = yes             # write on any volume in the pool
  Recycle Current Volume = Yes
}

> The only shortcoming I see at this time, is that Bacula has no knowledge
> of the availability of tapes.  It would be nice if there was a flag for
> "offsite" or similar to let Bacula know that a volume exists, but isn't
> available for backup (can be for restore, however).

The "Archive" status might be what you need. Although when you do a
restore from it, you've only got one shot at it before bacula purges
everything you've just spent hours merging in because it's outside of
the retention period.


>
> > On 16/06/06, Bill Moran <[EMAIL PROTECTED]> wrote:
> > > In response to "Dan Langille" <[EMAIL PROTECTED]>:
> > >
> > > > On 16 Jun 2006 at 14:25, Bill Moran wrote:
> > > >
> > > > >
> > > > > I'm responding to my own post and snipping all of it out.  If you 
> > > > > want the
> > > > > details follow the thread backwards, otherwise, read on.
> > > > >
> > > > > Did some refresher reading this morning, and this section of the docs 
> > > > > was
> > > > > particularly helpful:
> > > > > http://www.bacula.org/rel-manual/Automatic_Volume_Recycling.html
> > > > >
> > > > > The gist of it is that Bacula does not perform a pruning operation 
> > > > > unless
> > > > > it must do so to free up a volume.  In other words, as long as there 
> > > > > are
> > > > > volumes available, Bacula doesn't autoprune.
> > > > >
> > > > > Makes perfect sense why my rotation volumes never got recycled, there 
> > > > > were
> > > > > plenty of other volumes in the pool that had never been used.
> > > >
> > > > It also means that Bacula is following the strategy of "keep backups
> > > > as long as possible".  IMHO, that is The Right Thing To To(tm).
> > >
> > > I agree.  The problem was that Bacula wasn't aware of what was truly
> > > possible, which was a result of an inaccurate configuration on my part.
> > >
> > > --
> > > Bill Moran
> > > Collaborative Fusion Inc.
> > >
> > >
> > > _______________________________________________
> > > Bacula-users mailing list
> > > Bacula-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/bacula-users
> > >
>
>
> --
> Bill Moran
> Collaborative Fusion Inc.
>
> ****************************************************************
> IMPORTANT: This message contains confidential information and is
> intended only for the individual named. If the reader of this
> message is not an intended recipient (or the individual
> responsible for the delivery of this message to an intended
> recipient), please be advised that any re-use, dissemination,
> distribution or copying of this message is prohibited. Please
> notify the sender immediately by e-mail if you have received
> this e-mail by mistake and delete this e-mail from your system.
> E-mail transmission cannot be guaranteed to be secure or
> error-free as information could be intercepted, corrupted, lost,
> destroyed, arrive late or incomplete, or contain viruses. The
> sender therefore does not accept liability for any errors or
> omissions in the contents of this message, which arise as a
> result of e-mail transmission.
> ****************************************************************
>


_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to