Hello, pon., 20 lis 2023 o 00:27 Justin Case <jus7inc...@gmail.com> napisał(a):
> Hi there, > > I realise that my short term pool will have more volumes than actually > necessary, as I started the backups earlier than on the day per month when > fulls are taken. So this pool will have at least two fulls in the first > month. In subsequent months there will only be the need for 1 full per > month. > > Now I had this thought: may I reduce the MaximumVolumes of that pool after > 2 months when the superfluous first full has been purged? Explicitly this > does mean I would set MaximumVolumes of the pool to a number that is lower > than the number of volumes currently help in this pool. How would Bacula > react? would it throw the oldest purged volumes into the Scratch pool? Or > what else? > MaximumVolumes parameter will prevent automatic volume labeling or moving existing volume from Scratch pool only. No other procedures will be performed when the number of volumes exceeds this limit. So, unless configured by different parameters it won't move volumes out of the pool automatically. If you set up a recycle pool in your pool configuration then Bacula will always put recycled volumes in this pool, regardless of MaximumVolumes set. It is an independent parameter. Setting both on your pool will allow you to automatically lower the number of volumes in the pool and maintain a maximum number of them. best regards -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
