Offsite Backup Capacity Planner
Size the remote component of an established plan and plan the initial seed separately from normal version growth.
Decision guide
Use Offsite Backup Capacity Planner with confidence
This guide explains the offsite allocation decision behind Offsite Backup Capacity Planner, the evidence worth collecting for retention and destination count, and the boundaries of its remote-capacity requirement. Work through Offsite Backup Capacity Planner after a first run, then revise remote changed-data growth until the output reflects realistic conditions rather than convenience.
What this tool helps you decide
Size offsite backup capacity, changed-data reserve, and independent remote copies for an established backup plan. The Offsite Backup Capacity Planner turns that offsite allocation question into a vendor-neutral remote-capacity requirement, not a product endorsement. Use Offsite Backup Capacity Planner before requesting quotes, because remote changed-data growth can change the sensible retention and destination count choice. Keep that scope visible whenever the remote-capacity requirement is compared with alternatives.
Before you start
Enter protected TB, changed percentage, retention periods, and the number of offsite destinations that each need complete recoverability. Do not count replicas inside one provider account as automatically independent. For Offsite Backup Capacity Planner, write the offsite allocation assumption beside every saved result. That remote-capacity requirement record lets another person reproduce the retention and destination count scenario, challenge remote changed-data growth, and rerun Offsite Backup Capacity Planner after conditions change. Test one conservative offsite allocation case and one demanding case, then compare their remote-capacity requirement range.
How the calculation or recommendation works
One remote target equals protected data plus the 0.55-adjusted changed-data reserve. The offsite planner multiplies that reserve-bearing target by the declared destination count to expose total remote allocation. The Offsite Backup Capacity Planner keeps offsite allocation arithmetic transparent, allowing the remote-capacity requirement to be checked without a vendor account. In Offsite Backup Capacity Planner, follow every retention and destination count unit shown by Offsite Backup Capacity Planner. Decimal TB and TiB answer capacity questions. Keep every Offsite Backup Capacity Planner input in its displayed unit; preserve those Offsite Backup Capacity Planner labels when sharing or checking the result. Round the remote-capacity requirement upward only after reviewing the unrounded Offsite Backup Capacity Planner result.
How to interpret the results
Per-copy capacity should be compared with provider quotas or physical-media size; total target reflects every remote copy. Separate this storage question from upload time, egress cost, credential recovery, and restore logistics. Read the Offsite Backup Capacity Planner summary with its offsite allocation metrics. Use the Offsite Backup Capacity Planner table and caution note to examine the complete retention and destination count tradeoff. Save remote changed-data growth inputs with the result, compare scenarios under the same offsite allocation definition, and investigate conflicting remote-capacity requirement output before acting.
Worked example
Four TB changing 5% monthly across twelve periods needs about 5.32 TB for one offsite target. Two independently recoverable remote targets would raise modeled aggregate allocation to about 10.64 TB. This Offsite Backup Capacity Planner example demonstrates the offsite allocation path, not a universal default. Change remote changed-data growth one input at a time, observe which retention and destination count output moves, and note whether the remote-capacity requirement remains stable. Sensitivity around offsite allocation is more useful than copying another person’s final number.
Assumptions and limitations
The estimate excludes provider metadata, object versioning rules, minimum billable size, compression, deduplication, deleted-item policy, taxes, egress, throttling, and media shipping. Independence depends on credentials and failure domains. The Offsite Backup Capacity Planner is a planning aid for retention and destination count in Offsite Backup Capacity Planner. Treat the offsite allocation assumptions as boundaries: the remote-capacity requirement supports offsite allocation planning only. It does not certify an implementation of Offsite Backup Capacity Planner, guarantee recovery, or provide financial advice. Recheck remote changed-data growth, documentation relevant to Offsite Backup Capacity Planner, and operating requirements before purchasing for Offsite Backup Capacity Planner, migrating data, or approving a policy.
Next steps
Round each destination upward, calculate initial-seed and full-restore time, verify encryption-key custody, and test recovery without relying on the primary system or its normal administrator account. Continue from Offsite Backup Capacity Planner to the Cloud Backup Upload & Restore Time Calculator, then carry the Offsite Backup Capacity Planner finding into another backup planning tool for the next Offsite Backup Capacity Planner retention and destination count decision. Keep the Offsite Backup Capacity Planner remote-capacity requirement with its assumptions. Record the decision date for Offsite Backup Capacity Planner; assign a reviewer and a dated measurement checkpoint.