Planning tool
Backup and recovery planner
How much storage a backup needs is only half of it. This also tells you how long a full restore takes, and whether it meets what the business can tolerate.
Result
Backup storage, one copy
43TB
Storage including off-site copy
86TB
Local plus off-site/cloud
Weekly full
3.33TB
After 1.5:1 compression/dedupe
Daily incremental
0.1TB
Worst-case data loss (RPO)
24h
Full restore time
15.9h
- Good:A backup every 24 h meets the 24 h recovery point.
- Problem:Restoring everything takes about 15.9 h against a 8 h target. Use a faster restore path (local copy, faster disks or network), or restore the critical systems first.
- Check:The weekly full needs about 1,389 Mbps to finish in 8 h; the link gives about 700 Mbps. Lengthen the window, or use synthetic fulls.
Method
How the numbers are worked out
Storage
A weekly full backup plus daily incrementals (only the day's changes), kept for the retention you choose, plus any monthly fulls. An off-site copy doubles it.
RPO and RTO
The recovery point is how often a backup runs: up to that much work can be lost. The recovery time here is how long a complete restore of all data takes at 70% of the link speed.
Window
The speed needed to finish a full backup inside the window is data ÷ window; if the link is slower, the backup runs into working hours.
Assumptions and limits
- Restoring one server or a few files is much quicker than a full restore. Critical systems are restored first in practice.
- A backup that has never been test-restored is a hope, not a plan. Schedule restore tests.
- Ransomware often reaches backup storage on the network; keep one copy offline or immutable.
Related
Nothing you type here leaves your device unless you choose to send it to us. These are planning estimates; a survey or the equipment data sheet confirms the final figures.
Want an engineer to check it?
Send us what you worked out and we will come back with a design based on the real site.