On 9/8/23 17:45, Rob Gerber wrote:
Don't know if this helps, but file and job retention entries you put in
the pool will override any such entries on the client resource. So afaik
the last word on whether a job will be retained is the job retention
entry on a pool resource. Maybe define job and
Don't know if this helps, but file and job retention entries you put in the
pool will override any such entries on the client resource. So afaik the
last word on whether a job will be retained is the job retention entry on a
pool resource. Maybe define job and file retention on the pool and see wha
On 9/7/23 21:33, Ana Emília M. Arruda wrote:
Hello Andrea,
Hello.
You have 1 job per volume and automatic pruning and recycling enabled.
Correct.
If the only job in the volume is deleted from the Catalog, the recycling
algorithm will detect it and the volume will be marked as Purged a
Hello Andrea,
You have 1 job per volume and automatic pruning and recycling enabled. If
the only job in the volume is deleted from the Catalog, the recycling
algorithm will detect it and the volume will be marked as Purged and
reused. Is it happening with all volumes or only a few cases? Are you
m
On 9/2/23 12:30, Andrea Venturoli wrote:
Hello.
I've been using bacula for a long long time, but I can't seem to
understand why, in a specific installation, volumes are recycled before
I think they should.
The only difference from several other installation, is the use of S3
cloud plugin.
S
Hello.
I've been using bacula for a long long time, but I can't seem to
understand why, in a specific installation, volumes are recycled before
I think they should.
The only difference from several other installation, is the use of S3
cloud plugin.
So:
_ Bacula version is 11.0.6;
_ excerpt
