By LabBench · Calculation review: October 19, 2026. The examples below are calculated scenarios, not measured equipment benchmarks.
Use the data you actually transfer
A full backup of 1 TB and an incremental backup of 200 GB have very different transfer windows. Enter changed data after any effective deduplication or compression, if you know it. A tool reporting the size of protected files may not be reporting bytes sent. Initial seeding, later incrementals and a complete restore should each get their own estimate.
Turn link speed into throughput
1 Gbps is 1,000 megabits per second. Divide by eight to get the ideal 125 decimal megabytes per second. At 80% utilization, the effective throughput is 100 MB/s. That utilization is a scenario you choose, not a speed guarantee. Protocol overhead, small files, source and destination disks, encryption, shared links and server limits can all reduce it.
The transfer formula is: seconds = bytes × 8 ÷ (Mbps × 1,000,000 × utilization fraction). One decimal TB is 1,000,000,000,000 bytes; one TiB is larger. Select the unit matching the backup report.
Compare a local link and a home upload
| Data | Link | Effective MB/s | Transfer time |
|---|---|---|---|
| 1 TB | 1,000 Mbps | 100 | 2 h 46 m 40 s |
| 1 TB | 50 Mbps | 5 | 2 d 7 h 33 m 20 s |
| 200 GB | 50 Mbps | 5 | 11 h 6 m 40 s |
Open the 1 TB / 50 Mbps setup → · Open the incremental example →
An eight-hour window at 5 MB/s carries only 144 GB: 5,000,000 bytes/s × 28,800 seconds. The 200 GB example will not fit even if throughput stays steady. Pausing overnight and resuming later extends elapsed completion time further; check that your backup tool resumes safely.
Measure a representative transfer
- Use the same source, destination, protocol, encryption settings and network route as the real job.
- Record transferred bytes and elapsed transfer time for a representative sample. Include a realistic mix of small files if that is your workload.
- Convert observed MB/s into Mbps by multiplying by eight. Divide by the nominal link speed to estimate utilization.
- Allow additional time for scans, snapshots, verification and retries. The calculator estimates the data transfer stage, not every stage of a backup job.
For example, a measured 75 MB/s over a 1,000 Mbps link corresponds to 600 Mbps, or 60% utilization. That is more useful for this path than assuming every gigabit network reaches the same speed.
If the window is too long
First identify the bottleneck. A faster network cannot fix a destination disk that is already saturated. Consider a smaller incremental transfer, a longer initial seed window, or a secure offline seed if your storage provider supports it. Verify provider instructions, encryption and the integrity of the seed before relying on it.
A restore may use a different network direction, different storage, and different processing. Estimate it separately and actually test a restore. A short successful upload is not proof of recovery.
Sources: bandwidth and transfer-unit reference; a real initial-backup uplink problem. The community example motivates the planning task; its proposed setup is not presented as a tested recommendation.
Calculate your backup window → · Plan the storage capacity → · Estimate the server's running cost →