How to keep full backups until incrementals expire

[Frank V.]

Hi all,

we do full backups every second sunday of the month and daily
incremental backups in between. File and job rentention ist one month.
In this setup full backups get deleted when their retention period is
reached, although there are (newer) incremental backups that rely on it.
Which renders them kind of useless for us.
Is this per design or a misconfiguration on our side? Or did I
misunderstand something? How can I achieve that full backups will be
kept until all dependant incremental jobs also have reached their
retention date?

Regards,
Frank

[Philipp Storz]

Am 18.01.24 um 17:15 schrieb Frank V.:

> Hi all,
>
> we do full backups every second sunday of the month and daily incremental backups in between. File
> and job rentention ist one month.

Bareos disables job and file retention per default (these parameters are also deprecated) and only
uses pool based retention.

> In this setup full backups get deleted when their retention period is reached, although there are
> (newer) incremental backups that rely on it. Which renders them kind of useless for us.
> Is this per design or a misconfiguration on our side? Or did I misunderstand something? How can I
> achieve that full backups will be kept until all dependant incremental jobs also have reached their
> retention date?

It makes sense to have separate pools for data with similar retention periods. Usually, you have a
"full" and a "incremental" pool, where the full pool usually has a longer retention period than the
incremental pool.

This mechanism makes sure that your incrementals are recylced before your fulls.

--
Mit freundlichen Grüßen

Philipp Storz philip...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 63 06 93-92
http://www.bareos.com Fax: +49 221 63 06 93-10

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Geschäftsführer: Stephan Dühr, J. Steffens, P. Storz

[Frank V.]

This makes a lot of sense. I had just come to a similar realization
after reading another post in this list.

Thanks for the clarification!

Am 19.01.24 um 10:45 schrieb Philipp Storz:
>
> Achtung: Diese E-Mail stammt von einem externen Absender
> Öffne keine Anhänge/Links, es sei denn, du kennst den Absender und
> weißt, dass der Inhalt sicher ist.