The Job and File Retention just controls the size of the catalog database (and affects restores). The Volume Retention controls recycling.
Therefore I set File Retention = 50 years # let the Volume Retention of the pool control it Job Retention = 50 years # let the Volume Retention of the pool control it in the client definition and then control the recycling using Volume Retention in the pools. __Martin >>>>> On Wed, 10 Jan 2024 16:23:01 +0100, Marco Gaiarin said: > > Supposing to have some 'short rotation' retention for media (eg, 5 media > used one week once, volume retention at 28 days). > Suppose also to have job and file retention to 28 days. > > > But soppose also that i need to 'archive' some volume, changing status to > 'Archive'. Clearly in this way i can still restore data, but i still lost > metadata for that volume after 28 days (because job and file retention apply > anyway, right?). > > > I can set job and file retention to some (insane) limit like '6 years', > archive a volume and have access to the metadata? > I need to have '6 years' for both job and file, or file suffices? > > > OK, probably a better solution would be define a different pool with > different retention, but... this seems a quick and clear solution, if i've > understood well. > > > Thanks. > > -- > Berlusconi: "Da oggi sono a dieta" > Il Paese lo è già da 4 anni (Il Ruggito del Coniglio) > > > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
