On 12/10/2021 1:55 am, Andrea Venturoli wrote:
On 12/10/21 07:06, Bill Arlofski via Bacula-users wrote:
Hello.
----8<----
If a pool doesn’t have maximum volumes defined then Bacula will prefer
to demand new volumes over forcibly purging older volumes.
----8<----
My interpretation of that sentence is heavily based on the word
"forcibly".
I.e.
_ Appropriate candidate volumes (with proper retention periods) should
be pruned/recycled;
_ in case none is available a new volume will be created (unless you
set maximum volumes);
_ failing that "the oldest Volume" will be *forcibly* purged/pruned
(if the appropriate directives are set).
I hope someone will correct me if I'm wrong.
Back on the original topic: I too have an installation where I keep
seeing new volumes while there are older ones that should be recycled.
That's one installation out of several and with a config almost
identical to the others.
So the problem is there, but I never had the chance to debug it
properly. Since it's a 9.6, I hope it will go away when (one day) I'll
upgrade it to 11.
I'm interested in any suggestion/test to perform, though.
BTW, one curious thing is that some of the "forgotten" volumes are
known, while others aren't present in the Catalog :-?
bye
av.
I've upgraded to 11, and the problem is still here. Also, I'm not
seeing any expirations/pruning of files.
I'm more than happy to give access to the system for someone<tm> to
look.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
