Hello,
We have many recent posts on the forums regarding this topic, and instead of calculating manually, I recommend using the official calculator: https://www.veeam.com/calculators/simple/vbr/machines.
The primary consideration is whether you are using immutability. Without immutability, the calculation is straightforward, as previously discussed. With immutability, I suggest searching the forums for the latest updates. Notably, in V13, there is a change for "Direct to Object" storage, which reduces API calls. For Capacity Tier, API calls related to immutability will be further reduced in an upcoming release.
For Archive Tier, larger objects (hundreds of MB) are used, and the calculation differs. There may also be compute costs associated with creating these larger objects, particularly if Capacity Tier is in Azure. Additionally, it is possible to use Archive Tier without Capacity Tier.
Best regards,
Hannes
We have many recent posts on the forums regarding this topic, and instead of calculating manually, I recommend using the official calculator: https://www.veeam.com/calculators/simple/vbr/machines.
The primary consideration is whether you are using immutability. Without immutability, the calculation is straightforward, as previously discussed. With immutability, I suggest searching the forums for the latest updates. Notably, in V13, there is a change for "Direct to Object" storage, which reduces API calls. For Capacity Tier, API calls related to immutability will be further reduced in an upcoming release.
For Archive Tier, larger objects (hundreds of MB) are used, and the calculation differs. There may also be compute costs associated with creating these larger objects, particularly if Capacity Tier is in Azure. Additionally, it is possible to use Archive Tier without Capacity Tier.
Best regards,
Hannes
Statistics: Posted by HannesK — Sep 22, 2025 8:06 am
/english-betterindia/media/post_attachments/uploads/2022/05/Sustainable-home-10-1651667432.jpg)
