On 6/10/22 05:31, Gestió Servidors wrote:
Hi,I would like to know how reconfigure my Bacula v11.0.6 to avoid this message when I run a job: 10-jun 13:15 myserver-sd JobId 5078: Job BackupCatalog.2022-06-10_13.14.28_06 is waiting. Cannot find any appendable volumes.
In this case, runnig backup is the “BackupCatalog” that has this pool configuration: Pool { Name = Default Pool Type = Backup Recycle = yes # Bacula can automatically recycle Volumes AutoPrune = yes # Prune expired volumes Volume Retention = 200 days LabelFormat = "Catalogo" Maximum Volume Jobs = 7 Maximum Volumes = 4 Recycle Oldest Volume = yes Purge Oldest Volume = yes Storage = BackupRAID5 }Pool “Catalogo” has now four volumes, all of them is “Used” status... but, I suppose that when a pool has reached its maximum volume number, Bacula must take one of the “used” volume and, then, change to “append” in an automatic way, because if I need to do this reconfiguration for each pool, it’s hard to me because I’m running backups of several servers.So, if pool is configured with “Recycle = yes” and “AutoPrune = yes” and it is only allowed 4 volumes (Maximum Volumes = 4) and “Recycle Oldest Volume = yes” with “Purge Oldest Volume = yes” too, why Bacula is waiting for a new appendable volume? Would it be automatic?
I would not recommend using the “Purge Oldest Volume = yes” setting. Even the main manual states: -----8<----"We highly recommend against using this directive, because it is sure that some day, Bacula will recycle a Volume that contains current data. The default is no."
-----8<----As described in the documentation. it should work the way you expect using these settings, and disregard the 200 day retention period, but the pruning/recycling algorithm is quite complex, and it is even possible that it may not be working as expected in the version of Bacula you are using.
I would recommend some changes to allow Bacula to better manage the volumes in this pool without the possibility of it purging a volume with valid data on it.
So, I would say remove the two options “Recycle Oldest Volume = yes” and “Purge Oldest Volume = yes”, and lower the "VolumeRetention" to something smaller that makes sense for your environment.
Then, in bconsole, reload the config, update the pool, and update the volumes already in the pool so that they inherit the new retention period:
* reload * update pool=Default * update volume fromallpools Hope this helps! Best regards, Bill -- Bill Arlofski w...@protonmail.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
