As many ppl : I don't understand the retention policy rotation

[ONServ]

Hi,
I have an example from one of our free agent backup's client :

the USB disk is switched every day (yeah it add complexity).

Even with reading the doc https://helpcenter.veeam.com/docs/agent ... tml?ver=60 and other posts I still understand how I came with these chains.

Thanks for your light

ps : which file can be delete safely in this situation ?

[Gostev]

If you delete everything above 1906.vbk, you will have 4 latest restore points still available.

[DFEX]

We have a similar issue.
Ours is related to "periodic active fulls" (which "OnServ" does NOT use). The "*.vib"'s are accumulating endlessly as soon as we use the advance setting "periodic active full" (which is a good idea - at least in our opinion).
BTW: With our licenced Agent this is not a problem at all.

[ONServ]

If you delete everything above 1906.vbk, you will have 4 latest restore points still available.

THks but why does I get all of these full+increment stack ? How can I prevent this to happen again ?

[Gostev]

You mentioned this is a rotated drive, so perhaps when the time comes to remove certain backup files per their retention policy, the retention processing code simply cannot reach them.

[ONServ]

So how can we manage rotated drive ? is there any recommendation ?
Thanks

[Tempuser2024_]

Can confirm that this can be confusing.
Would add also that after updating Windows Agent to 6.1.0.349, app started to generate full backups instead of incrementals (automatically or by clicking "backup now").
There were threads found, where users mentioned that editing task can trigger this.

App was updated on 11.03.2024.
As solution for me, task had to be recreated.

[MiroslavKlose]

The same thing has never worked for me with backups to an external drive that i only connect to the pc when i actually want to back up my data. So i created my own "Veeam-Agent-Backup-Helper" script that solves this problem.

https://github.com/yeah-Buddyy/Veeam-Ag ... kup-Helper