Hello Larry,
On 12/8/21 15:08, Larry Rosenman wrote:
I have a bunch of volumes that bacula seems to have forgotten about. Can you
explain why?
Also, what SQL/etc can I do to fix it?
Attached are a DB list for the volumes, and the ls -l.
Normally the information about the pruning/recycling is printed in the
debug trace file, something with
setdebug trace=1 level=100 tags=volume,sql dir
It should give give you the different traces and SQL commands that
are used to list volumes and jobs and prune them. You might look them
and check why the records are not properly sent back. (Recycle=No,
VolumeRetention=0, incorrect Pool, incorrect status, etc...)
Then it depends on your different settings, for example, I have seen
that you are using a Volume Retention = 0, that means the recycling
algorithm is disabled for your volume, it might explain why you cannot
achieve what you want. In recent Bacula versions, the pruning
algorithm has bee reviewed to not prune jobs that are necessary to
restore to the last restore point. So, you might need to run a Full
or a Differential backup to get rid of a chain of Incremental jobs
for example. If you don't want to use that feature, the Volume Retention
is the last variable that is checked for a volume, set it to 2 hours,
and after 2 hours, a Full/Used volume in a Pool A should be recycled
when a new job in Pool A requires a volume.
Hope it helps!
Best Regards,
Eric
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
