Effect of doing active full backup on Capacity Tier upload.

[ConradGoodman]

Please clarify some things for me.

From the advice I've received here, only unique blocks of data are offloaded to the capacity cloud tier.

For example, I have a backup job with monthly active fulls to a standard repository

The backup job has a copy job on it, that goes to an SOBR with object storage.

When the backup job does an active full, all blocks are read from source and written fresh.

When the subsequent copy job writes to an SOBR, does it also do an active full, or just the changed blocks?

THis subsequent copy job also goes to capacity tier, will it upload the entire full backup agian or only changed blocks?

I think because it is forever forward incremental with synthetic fulls on both the copy job and capacity tier offload, it will be unique only?

[Gostev]

Only changed blocks will be transferred in both cases. This would be the case even if you enabled active fulls on the copy job though, so this is not dependent on the source job being forever forward incremental with synthetic fulls.