Am 24.06.25 um 15:11 schrieb Marcin Haba:
ok ... so I don't have anything wrong that triggered that (?)
I don't know because we don't see your pruning settings in the
Director configuration.
AutoPrune = yes
is set for the Client
and for 2 Pools as well, but not for the pools with the Archive Tapes.
So my issue comes from that setting in the Client, I assume.
Can't remember setting this, but who knows ...
I still don't fully get it:
the volumes are in mode "Archive", so they should NOT yet been
overwritten (in fact they aren't: they are stored off-site).
And even then the related "file lists" in the database are pruned?
This depends on your pruning setting, specially on the AutoPrune
setting (and job/file retention directives as well).
That's really new to me.
Sure. I think that many users are not aware of that until they read
about it or until they try to restore and find no files to select for
restoring.
This is also well described in the Bacula documentation:
"As Bacula writes files to a Volume, it keeps a list of files, jobs,
and volumes in a database called the catalog. Among other things, the
database helps Bacula to decide which files to back up in an
incremental or differential backup, and helps you locate files on past
backups when you want to restore something. However, the catalog will
grow larger and larger as time goes on, and eventually it can become
unacceptably large.
Bacula's process for removing entries from the catalog is called
Pruning. The default is Automatic Pruning, which means that once a Job
record reaches a certain age (e.g. 30 days old) and a pruning occurs,
it will be removed from the catalog."
https://www.bacula.org/15.0.x-manuals/en/main/Automatic_Volume_Recycling.html#SECTION0031100000000000000000
understood, thanks!
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
