How limit WASABI restore points (backup copy from forever incremental) / synthetic full possible?

[sysinfma]

In V12 we have set up daily backup copies from our local forever forward repository to Wasabi. A full backup and two incrementals have been uploaded so far.

Now we need to make sure that backups older than ~14 days should be removed from the Wasabi bucket.

What's the best way to achieve this?
Weekly active fulls should make it possible, but we would like to avoid having to upload a full backup (1.5 TB) every weekend.

Would synthetic fulls help/are they even possible – or what's the best option we have here?

Many thanks!

[veremin]

Can you tell us what copy mode and retention settings the backup copy job currently has, so we can advice on the required configuration? Thanks!

[tyler.jurgens]

Would synthetic fulls help/are they even possible – or what's the best option we have here?

Set the GFS policy on your backup copy job. That will essentially create a synthetic full backup on the date selected.

[sysinfma]

Retention policy: 60 days
GFS: 2 weekly, 4 monhtly, 1 yearly
Mode: Incremental with synthetic fulls on saturday
Active fulls: off

Many thanks!

[sysinfma]

Set the GFS policy on your backup copy job. That will essentially create a synthetic full backup on the date selected.

GFS with synthetic fulls is enabled – so I'm already safe?
I was/am not sure what this means for the backup copy to Wasabi. Will it really only upload the needed blocks to create a synthetic full in the Wasabi bucket then?

[tyler.jurgens]

I should say that with GFS restore points, these aren't the same as Synthetic fulls in the way they are with block storage. Veeam doesn't transform any backups as there are no backup chains in object storage.

However, GFS restore points are helpful to understand retention policies (in my mind) as well as setting backups to be immutable based on your GFS policies.

[sysinfma]

Well, that's exactly why I am asking here.

"Veeam doesn't transform any backups as there are no backup chains in object storage."
It doesn't transform backups, but it definitely reuses blocks of different backups/restore points - like on ReFS.

Can someone clarify the matter?