Help with understanding retention with copy/move jobs in SOBRs

[teknomage]

I am trying to understand how the restore points are created and when where they reside in different configurations of SOBRs. Does anyone know of a good blog post or video that explains this well?

I'm looking for more explanations or descriptions of scenarios like the one below:

Example from Reddit: Scenario: move and copy. Backup retention 30days. Move mode set to move backups older than 14days. At 14days into the job, you will have 2 copies - local and cloud. On day 30, you will have 15days worth locally, and the full 30days in cloud.

Thanks.

[Moderator: Fix url formatting]

[david.domask]

Hi teknomage,

Capacity Tier with move will follow the behavior described here: https://helpcenter.veeam.com/docs/backu ... ver=120#vp

Move works with "inactive" backup chains as shown in the guide -- that is, assume you have the following backup files on repository:

VBK VIB VIB

This is a chain, a VBK and its dependent increments -- as it is the only chain, it is considered "active"; jobs will be writing and potentially transforming this chain. Active chains will not be considered for the Move operation until a new chain starts (periodic active or synthetic full).

VBK VIB VIB VBK VIB VIB

In this example, the green part of the chain is "inactive" -- there is a new backup chain, and the old chain will guaranteed not be transformed or changed, so it's eligible to be moved to capacity tier.

So from your example, it's not clear if periodic fulls are enabled or not. Without periodic fulls, the move operation will not be able to work on the chain, so it will remain on performance tier.

[vitalii.fesh]

Without periodic fulls, the move operation will not be able to work on the chain, so it will remain on performance tier.

It will also work with synthetic fulls (GFS), helping to preserve space on the object storage.