>>>>> On Tue, 3 Apr 2012 17:23:10 +0200, Ward Poelmans said: > > On Tue, Apr 3, 2012 at 16:14, Martin Simmons <mar...@lispworks.com> wrote: > >>>>>> On Tue, 3 Apr 2012 09:39:48 -0400, John Drescher said: > >> > >> > Well, from the docs: "The Volume Retention record defines the length > >> > of time that Bacula will guarantee that the Volume is not reused > >> > counting from the time the last job stored on the Volume terminated." > >> > >> That is correct. > > > > Yes, it has been like this for a long time, but always seemed like a bug to > > me > > (at least a bug in docs -- the word "guarantee" is too strong). > > So, is there any way to make sure it does not recycle volumes until > the retention period is over other then increase the job retention > period?
I don't know of any direct way to do that while still pruning jobs. John Drescher is right though -- the job records are usually tiny compared to the file records. __Martin ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
