Dear Ana,
Thanks for the response. It took a few days to find this in the Inbox.
I see what you're saying. What else besides Max Volumes tells Bacula not to
label anymore. I kind of wanted it to manage that on its own, otherwise
I'll be changing that everytime I add a new client. Then of course
Hi Shon,
The question is that bacula needs more than just the "retention period" to
recycle volumes when you´re using disk volumes and automatic labeling. If
you don´t have a limit of volumes in your pool or something else that tells
bacula to not label any more volumes, just use an older one that
> did you remember to update your volumes after changing the pool
> definition? Depending on the size of your catalog, recycling can take
> quite a while, but still bacula should not create new volumes. I don't
> see a "maximum volumes" in your pool def, so basically the number of
> volumes in the
On Thu, Jul 11, 2013 at 10:01:24AM -0400, Mingus Dew wrote:
> Dear All,
> I am running Bacula Community Edition 5.2.13 on Solaris 10 x86. I am
> trying to understand why Bacula doesn't seem to recycle when I think it
> should.
> I have recently moved to a configuration where each Volume c
Hi Mingus,
When using disk volumes with automatic volume labeling, you have to tell
bacula when to stop labeling new volumes... You can do it limiting the
number of volumes in the pool. Also, you can try Recycle Oldest Volume =
yes. Pasted from
http://www.bacula.org/en/dev-manual/main/main/Basic_V
Dear All,
I am running Bacula Community Edition 5.2.13 on Solaris 10 x86. I am
trying to understand why Bacula doesn't seem to recycle when I think it
should.
I have recently moved to a configuration where each Volume contains
only a single Job. I had envisioned that when the Volume Reten
