What does this calculator do?
A backup window is the time available to finish a backup before the systems are needed again. Two questions follow from it, and this calculator answers both. In throughput mode you give the data size and the window, and it returns the sustained rate the path must deliver. In time mode you give the data size and the rate you can actually achieve, and it returns how long the job will take. An optional compression or deduplication saving reduces the data actually moved before either calculation runs. Units follow the standards exactly: kB, MB, GB and TB are powers of ten (1 GB = 10⁹ bytes) while KiB, MiB, GiB and TiB are powers of two (1 GiB = 2³⁰ bytes). The two ladders are never mixed, so "1 GB = 1024 MB" is not treated as a universal rule.
Formula
Compression is applied first; then the effective data is either divided by the window or by the rate.
effectiveData = dataSize × (1 − compression ÷ 100) requiredThroughput = effectiveData ÷ backupWindow time = effectiveData ÷ throughput
How to use it
Choose the mode; the form shows the fields it needs. Enter the data size with its unit — full backup size for a full job, or the changed data for an incremental. Set the compression percentage only if your backup software actually achieves it on this data: already-compressed media and encrypted volumes gain nothing. In throughput mode enter the window in hours; in time mode enter the rate you have measured, not the rated link speed.
Worked example
20 TB in an 8-hour window with no compression: 20 × 10¹² bytes is 160 Tbit, and 8 hours is 28,800 seconds, so the path must sustain about 694.4444 MB/s — roughly 5,555.5556 Mbps, or 5.5556 Gbps. In time mode, the same 20 TB at a measured 500 MB/s takes about 11.111 hours, or 666.67 minutes, which will not fit an 8-hour window.
Frequently asked questions
Why does my backup take longer than this says?
Backups are rarely bandwidth-bound alone. Snapshot creation, catalogue and metadata operations, per-file overhead on millions of small files, source disk read speed, target ingest rate, verification passes and other jobs competing for the same window all add time this model does not include.
Should I enter a compression percentage?
Only one you have observed on similar data. Text, logs and databases compress well; video, images, encrypted volumes and already-compressed archives barely compress at all. An optimistic figure here produces an optimistic window and a missed schedule.
Does this apply to incremental backups?
Yes, if you enter the changed data rather than the full data set. Synthetic fulls, merges and consolidation passes on the target are extra work that this calculation does not represent.
Sources
- SNIA Dictionary — vendor-neutral definitions of RAID levels, stripe, mirror, parity, IOPS and raw versus usable capacity.
- NIST — Prefixes for binary multiples (IEC 80000-13): a drive sold as 2 TB (2 × 10¹² bytes) is about 1.82 TiB as reported by most operating systems, which is why raw and usable figures are shown in the unit you choose.
- Nominal equal-drive capacity model used here: RAID 0 = N × S, RAID 1 = S, RAID 5 = (N−1) × S, RAID 6 = (N−2) × S, RAID 10 = (N/2) × S. Filesystem overhead, metadata, hot spares, vendor reservations, compression and deduplication are not modelled unless you enter them.
- Reviewed: 2026-08-10
Related calculators
Last updated: 2026-08-10 · v1.0.0 · Report an error