Changing Retention Policy time caused full snapshot

[Pagrossman]

Hello,

we needed to change the retention policy on our repositories from 180 days to 5 years. Because we are using snapshot based repository, we didn't expect any problem (any additional network traffic, any longer backup job run, only change of number in setting). Unfortunately, always it performs "Incremental full backup". Why?
I understand increasing backup job time in retention policy for item based repository, but not for snapshot based repository.
Is it correct that increasing retention policy time can caused full backup?

Backup job before the change


Backup job after the change (few minutes after previous backup job above, look at on "transferred" items).

[nielsengelen]

Hi,

This is hard to say via the screenshot, it looks like we process the items as expected but the size looks small. I suspect that we are doing a verification with all the items to assure it matches the retention.

I would suggest to open a support case for more insight via logs and maybe a remote call. Can you let us know the case ID once u made one?

[Pagrossman]

This was only question about behavior, but it seems that I need to create a service ticket...

We only wanted to have current data longer... :-/

Yes, it seems that the backup job is doing a verification with all the items, but I don't understand why in the snapshot based retention policy...

[Polina]

Niels is correct in his guess - after the retention period change, we're verifying all the items. Only changed or missing items are downloaded though. This behavior is going to be fixed in the next versions/patches.

[Pagrossman]

Case #05138295

By the support, it is normal... I don't know why, but never mind...

[Mike Resseler]

@Pagrossman

As you see above from Polina, we indeed do this to verify if everything is ok. And that causes a very long backup, although not much is being downloaded because it is incremental. Our engineers are thinking how to solve this in future patches/ versions/ ...