When to use this calculator
Size a backup link from the data volume and backup window rather than from concurrent media streams. A 1,000 GB job over eight hours at 80% payload efficiency needs about 347.22 Mbps of average link capacity. Verify sustained network, source-disk and destination performance before relying on the window.
Explore the networks & service capacity calculators for other questions in this topic. For a related calculation, use the Upload Time Calculator: Estimate the time required to upload a decimal-megabyte file.
Use the data transferred in this backup job
For incremental backups, enter the transferred change volume, not the entire retained backup repository. Compression and deduplication may reduce the amount, but their effect depends on your software and data. A 1,000 GB transfer in eight hours at 80% payload efficiency requires about 347.22 Mbps of average link capacity.
PUTTING IT INTO PRACTICE
Backup Bandwidth: a worked example
The values below are an illustrative example, not a recommendation. Replace them with measurements or assumptions that match your question.
| Input | Example value |
|---|---|
| Data to transfer (decimal GB) | 1,000 |
| Backup window (hours) | 8 |
| Estimated payload efficiency (%) | 80 |
| Result | 347.222222 Mbps |
- Check the input labels and enter the example values above.
- Apply the relationship: Required Mbps = data GB × 8,000/(window hours × 3,600 × efficiency/100)..
- The result is 347.222222 Mbps, rounded for display.
How to interpret your result
Enter the bytes actually transferred for this job, after any compression or deduplication. Uses decimal GB and Mbps. Efficiency models the usable payload fraction of link capacity; choose an assumption appropriate to your connection. Excludes disk bottlenecks, retries, cloud throttles and peak contention. This is not a measured throughput guarantee or an SMPTE 2110 media-network calculator.
The result is an average link-capacity requirement in Mbps. Compare it with sustained usable throughput, not just an advertised line speed; the payload-only rate is shown separately.
Frequently asked questions
Does enough internet bandwidth guarantee the backup finishes?
No. Disk reads and writes, CPU work, retries, shared traffic and cloud-service throttles can limit sustained throughput. This estimate is an average planning quantity; validate the complete transfer path.
When is the backup bandwidth calculator useful?
Size a backup link from the data volume and backup window rather than from concurrent media streams. A 1,000 GB job over eight hours at 80% payload efficiency needs about 347.22 Mbps of average link capacity. Verify sustained network, source-disk and destination performance before relying on the window.
How do I use the backup bandwidth calculator?
Enter data to transfer (decimal gb), backup window (hours), estimated payload efficiency (%). The result updates automatically. Use the units shown beside each input; the example values illustrate the method.
Which formula does this calculator use?
Required Mbps = data GB × 8,000/(window hours × 3,600 × efficiency/100)..
What should I check before using the result?
Enter the bytes actually transferred for this job, after any compression or deduplication. Uses decimal GB and Mbps. Efficiency models the usable payload fraction of link capacity; choose an assumption appropriate to your connection. Excludes disk bottlenecks, retries, cloud throttles and peak contention. This is not a measured throughput guarantee or an SMPTE 2110 media-network calculator.
How are results rounded?
Scalar numbers display up to six decimal places, with scientific notation for very large or small values. Text, fraction, date and schedule outputs use the format described on the tool. Intermediate calculations use JavaScript floating-point arithmetic. Keep sensible precision for your measurements.
Further reading
For background on this topic, see AWS Backup: backup-window and bandwidth considerations ↗. This is a topic reference, not an external review or endorsement of this tool.
Calculators Map editorial process · Updated · Methods and limitations