Start with units
Network links are normally stated in bits per second. Eight bits equal one byte, so a 1GbE link is 1,000 Mbps or a theoretical 125 MB/s before overhead. Storage advertisements use decimal TB; operating systems may display binary TiB. Keep the chosen unit visible throughout the estimate.
Transfer-time equation
seconds = data bits รท effective bits per second. For a decimal TB input, one TB is 8,000,000 megabits. Effective throughput is the minimum of the source, destination, link after protocol overhead, and any service throttle.
Practical throughput range
Ethernet link rate is not file throughput. TCP/IP and SMB overhead, encryption, small-file metadata, Wi-Fi contention, disk performance, CPU, other users, and cloud service policies reduce payload. State an efficiency assumption and treat the result as a planning range, not a promise.
Asymmetric internet changes recovery
Initial cloud upload usually uses the much slower upload path. A full restore uses download, but still depends on the local destination and service behavior. Restricting jobs to overnight hours extends calendar duration even when raw transfer hours stay the same.
Worked example
At 40 Mbps upload and 75% practical efficiency, the usable estimate is 30 Mbps. Uploading 4 TB is therefore measured in many days of transfer time; a 12-hour daily backup window roughly doubles the calendar duration. Use a local copy or seed workflow when that does not meet recovery needs.
Bottleneck method
- List source read, destination write, link, and service limits in the same unit.
- Apply a documented practical-efficiency factor to the link.
- Use the smallest rate, then compare predicted duration with the available window.
- Change the actual limiting stage before buying a faster component elsewhere.
Use these formulas
Apply them in Cloud Backup Upload & Restore Time Calculator, Local Network Transfer Time Calculator, and Recovery Time Estimator.