Disaster Recovery Capacity Needs Estimator

The Disaster Recovery Capacity Needs Estimator estimates the future replicated recovery capacity after applying expected data growth and an additional resilience or operational overhead factor. It is designed for infrastructure planning where the raw protected workload is not the same as the final capacity that must be provisioned.

The main result is the provisioned capacity estimate at the end of the planning horizon. The breakdown separates organic growth from added overhead, making it easier to discuss how much capacity comes from workload expansion versus redundancy, metadata, snapshots, replication, or other operational allowances.

Inputs

TB
%
%
months
Result
Estimated required capacity
Projected base capacity
Added overhead capacity
Increase vs. current capacity

1. Enter current protected capacity
Use the current workload size in terabytes before the extra overhead factor.

2. Set monthly data growth
Enter the expected compound growth rate for the protected workload.

3. Enter the overhead factor
Use a percentage that represents extra capacity required by your design, such as replication, snapshots, metadata, or safety margin.

4. Choose the planning horizon
Enter the number of months to project.

5. Review required capacity
Use the main result as a planning estimate and the breakdown to see how growth and overhead contribute.

Required capacity = Current capacity × (1 + Monthly growth)^Months × (1 + Overhead factor)

Projected base capacity is calculated before overhead. Added overhead capacity equals projected base capacity × overhead factor. Percentages are converted to decimals. The model assumes compound monthly growth and a single overhead factor applied at the end of the horizon.

What the result means

The result combines projected workload growth with the selected additional capacity allowance.

Use multiple scenarios when growth, retention, compression, replication, or recovery design is uncertain.

Given: Current protected capacity = 80 TB; monthly growth = 3%; overhead factor = 20%; horizon = 12 months.

Calculation: Projected base = 80 × 1.03^12 = 114.06 TB. Overhead = 114.06 × 0.20 = 22.81 TB. Required capacity = 136.87 TB.

Result: Plan for about 136.9 TB under these assumptions, roughly 56.9 TB above current protected capacity.

What should the overhead factor include?

Include only capacity that scales with the protected workload and is not already included in the current capacity input. Examples can include replication, snapshot reserve, metadata, or an operational buffer.

Can I enter zero growth?

Yes. With zero growth, the calculator applies only the overhead factor to the current capacity.

Should I use decimal TB or binary TiB?

Use one unit system consistently for both current capacity and the result. The calculator treats the number as TB and does not convert between decimal and binary units.

Does this model retention changes over time?

Not separately. If a retention-policy change increases required storage, incorporate its effect in the overhead assumption or run a separate scenario.

Why might actual capacity needs differ?

Compression, deduplication, change rate, replication design, workload churn, and vendor billing rules can all change real capacity requirements.