What to enter
Start with the protected data size in gigabytes. Add the estimated daily change rate, the number of daily restore points, weekly full copies, annual growth and any measured compression or deduplication saving.

Cloud planning · Free
Estimate the storage needed for a backup plan before choosing a service or budget. Adjust each assumption to match your workload.
Understand the estimate
Backup storage depends on more than today's dataset. Change rate, the number of retained copies and expected growth all affect the result.
Start with the protected data size in gigabytes. Add the estimated daily change rate, the number of daily restore points, weekly full copies, annual growth and any measured compression or deduplication saving.
The tool grows the initial dataset by your annual assumption, adds estimated daily changes and weekly full copies, then applies your chosen saving percentage. The result is an indicative retained capacity in gigabytes.
Real storage can differ because of retention rules, changed blocks, backup format, provider overhead and recovery copies. This estimates capacity, not backup service price, transfer fees or restore time.
Worked example
With 20% expected growth, 5% daily change, 30 daily restore points, four weekly full copies and 30% assumed savings, the simple model estimates about 5,460 GB retained. Replace those defaults with measurements from your own environment.
Estimate running costs separately with the cloud cost estimator. For an application JNIT develops or deploys, discuss backup and recovery requirements during planning.