Reducing size of long term storage repositories

[warnox]

Hi,

From what I can see, to keep GFS backups, each retention point ends up being a full backup. In some cases storing a full backup for each archival retention point seems somewhat unnecessary. If I have a server (or workstation) with a very small rate of change, which requires 200 GB of space for a full backup and I need to keep 12 monthly backups, that will require ~2.4TB of storage. Considering object storage for the repository (capacity tier), what is a potential solution here? Differential backups come to mind but will compression/dedupe help or will each VBK take up 200 GB?

Thanks for any input.

[HannesK]

Hello,
our object storage implementation is "incremental forever". That means it will only consume space for changed data. Similar like for REFS / XFS.

Please see the sticky forum FAQ: post338749.html#p338749

Best regards,
Hannes

[Gostev]

Incremental forever by default, that is.

We do provide an option to store GFS fulls as standalone (since some policies and regulations may require this) but it is not a default setting.

[warnox]

Thanks both, that makes sense.

Gostev, where can I find the option to for storing GFS' fulls as standalone?

[HannesK]

the standalone full option is available for archive tier. https://helpcenter.veeam.com/docs/backu ... ml?ver=110 -> the "Store archived backups as standalone fulls" checkbox

If you only use capacity tier (as you mentioned in the initial post), then the data will be stored "incremental forever"