Table of Contents
Overview
This article will provide a brief overview of how to estimate BaaS, Archive, and RIP usage using Veeam's backup capacity calculator.
Estimating Capacity
1. If you haven't already done so, use Veeam ONE or RVTools to gather necessary information on the production environment.
2. Open the Veeam Backup Capacity Calculator by clicking here.
3. Mody the source data information. For Source capacity (TB), use the production data size. If Veeam ONE reports were run, fill in the daily change rate and yearly growth from their applicable reports. Change Scope for growth (years) to 1, and uncheck REFS/XFS. If you have an estimate on compression/deduplication from an existing Windows or Linux repository, change Reduction (%) as well, otherwise leave it be.
4. Under Primary backup policy, set the retention period that will be stored. NOTE: For RIP to work correctly, at least 1 weekly must always be configured.
5. Uncheck Backup copy policy.
6. If Archive is going to be utilized, check Capacity tier enabled and configure the offload settings.
7. Now, click the Calculate button. BaaS consumption will be the full backup and incremental backup items under Backup combined and object storage consumption will be located under Object storage.
8. If RIP is going to be utilized, add the number of days that will be recycled to the Primary backup policy, remove GFS, uncheck Capacity tier, and re-run the calculation. The amount that the two Backup fields increases by will be the estimated RIP consumption.
9. Finally, round BaaS, RIP, and Archive each up to the next largest whole number.
Example
In the above screenshots, 6 TB of production data with a 7% daily change rate and 9% yearly growth were initially configured. Job retention was set at 14 days with 5 weeklies, 6 monthlies, and 1 yearly. Backups offload to archive after 14 days and a 14-day recycle bin was requested. In this case, BaaS consumption would be 9.27 TB, RIP would be 13.62 TB, and Archive would start at 4.69 TB but is estimated to grow to 15.44 TB by the end of the year. CyberFortress bills are based on rounding up to the next whole number of TB consumed, so consumption would be billed as 10 TB of BaaS, 14 TB of RIP, and 16 TB of Archive.