> Uh. Oh. But why not simply move the media to the archive pool?
For search engines: it worked.
I can move a volume to a different pool:
> *update volume=SVPVE3_0001 pool=FVG-SV-SVPVE3ArchiveLTOPool
where more loose retention apply, then obviously re-apply retention
parameters itself
Mandi! Rob Gerber
In chel di` si favelave...
Thanks for your previous message, full of invaluable info!
> However, I have an idea. If you have some pool like 'Archive pool' and you
> set in that pool File, Job, and Volume retention to some very long period,
> like 1000Y, then if you migrate job
On 6/4/25 9:06 AM, Rob Gerber wrote:
>
*I think the migrated jobs should inherit the new pool's retention period.*
Hello Rob, everyone...
The above statement from Rob is 100% correct.
As a matter of fact, this is the general idea and typical use case... eg: We see people run backup jobs to di
Marco,
In my last email, I couldn't think of many good ways to extend the
retention of jobs and files after they had run.
However, I have an idea. If you have some pool like 'Archive pool' and you
set in that pool File, Job, and Volume retention to some very long period,
like 1000Y, then if you m
Marco,
In this email I will reference information from the bacula 15.x manual. See
link below.
https://www.bacula.org/15.0.x-manuals/en/main/Automatic_Volume_Recycling.html
>From the 15.x manual, PDF section 31.2, Pruning Directives:
AutoPrune = If AutoPrune is set to yes (default), Bacula will
