Fast cloned backup capacity when moved to object storage

[Nas]

Hi,

From VBR console, my current Windows ReFS repository capacity shows:
100TB used
70TB free
90TB total capacity

From the Windows repository explorer, it shows E: drive capacity is 20TB used. So fast clone is saving lot of physical storage usage in my case.

If I were to enable SOBR, with my Windows repository as performance tier and Azure blob storage as capacity tier. What would be the expected usage (TB) on my capacity tier assuming I choose copy all backups?

I understand there is no block cloning on object storage, so am I anticipating my existing backups to rehydrate beyond 20TB or maybe reach 100TB capacity usage once they copied over to capacity tier?

[HannesK]

Hello,
assuming that you are not using immutability, the storage consumption on object storage would be similar as on REFS / XFS.

With immutability the math is more complicated: see user guide. Then the space consumption formula is "retention period + immutability period + block generation period". Please note, that the storage consumption is massively reduced in V13 with "direct to object storage" (aka Backup Copy Job). The new formula is "retention period" + "block generation period".

http://calculator.veeam.com/ also should help to estimate.

Best regards
Hannes

[Nas]

Hi Hannes,

Thanks for replying, the capacity tier is immutable.
Referring to formula "retention period + immutability period + block generation period", in my case I set;
retention policy to 30 days
immutability period 30 days
azure default block generation period 10 days

Am I correct to assume that retention policy and immutability period always overlap?

So effectively, I should be forecasting for 40 days storage consumption as minimum and not 30 + 30 + 10, correct?

[vitalii.fesh]

No, you have to sum up retention and immutability. Check this out: https://helpcenter.veeam.com/docs/backu ... ml?ver=120