Backup and Disaster Recovery · #55
Online Backup Repository Sizing Calculator
Estimates the space full and incremental backup chains need over the retention period.
- Data is processed in your browser and not sent to a server
Tool
What does this tool do?
Backup repositories are often bought with a rough rule like 'source × 2' and start filling up in the first year. The real need is driven by the number of fulls, daily incremental size, compression/deduplication and growth. The tool shows these four components separately.
How to use it
- Enter the source data (TB) and daily change rate.
- Enter compression + deduplication savings (%), retention (days) and full backup interval (days; 0 = forever incremental).
- Enter annual growth, years and working space headroom; press Calculate.
Fields
- Source data
- Total protected VMs/files (used space).
- Daily change
- Usually 2–5 %; higher for databases.
- Data reduction savings
- Compression + deduplication; 50 % = half.
- Retention (days)
- Restore points with daily backups.
- Full backup interval (days)
- 7 = weekly active/synthetic full; 0 = forever incremental.
- Annual growth
- Planning (years)
- Working space
- For merges, synthetic fulls and unexpected growth.
Worked example
| Input | Value |
|---|---|
| Source data | 20 |
| Daily change | 3 |
| Data reduction savings | 50 |
| Retention (days) | 30 |
| Full backup interval (days) | 7 |
| Annual growth | 20 |
| Planning (years) | 1 |
| Working space | 10 |
Expected result: 20 TB source, 3 % change, 50 % reduction, 30 days, weekly full: 6 fulls (60 TB) + 25 incrementals (7.5 TB) = 67.5 TB; with 20 % growth and 10 % working space 89.1 TB.
Weekly fulls are 89 % of the space. On a repository with ReFS/XFS block cloning synthetic fulls consume far less physical space; enter 0 as full interval to see the lower bound.
Second scenario
| Input | Value |
|---|---|
| Source data | 8 |
| Daily change | 2 |
| Data reduction savings | 40 |
| Retention (days) | 14 |
| Full backup interval (days) | 0 |
| Annual growth | 0 |
| Planning (years) | 0 |
| Working space | 10 |
Expected result: 8 TB, 2 % change, 40 % reduction, 14 days forever incremental: 4.8 + 14 × 0.096 = 6.14 TB; 6.76 TB with 10 % headroom.
Method and assumptions
Full = source × (1 − reduction). Incremental = source × change × (1 − reduction). With an interval > 0, fulls = ceil(retention / interval) + 1 and incrementals = retention − (fulls − 1); with 0, 1 full plus one incremental per retention day.
The result is multiplied by (1 + growth)years and working space is added.
Using the result and troubleshooting
Compare with the usable value from the RAID Capacity Calculator. Size long-term (monthly/yearly) GFS retention and immutable copies separately.
Limits and common mistakes
- Block cloning (ReFS/XFS) savings, GFS points and product metadata are not modelled; the change rate is constant.
Frequently asked questions
Where do I get the change rate?
From the ratio of incremental job size to source size in your backup software, or CBT/VSS reports. If unknown, 3–5 % is a reasonable start.
Related tools and service
- Immutable Backup Capacity CalculatorCalculates the extra capacity caused by locked backups living longer than retention.
- Backup Retention (GFS) CalendarShows which restore points a GFS retention rule keeps on a given date.
- Backup Window Bandwidth CalculatorCalculates the speed needed to move a data volume within a time window and the duration on an existing link.
Related service: Backup and Disaster Recovery