BACKUP & RECOVERY PLANNING

Cloud Restore Time and Cost Calculator

Estimate how long a large restore from cloud object storage (AWS S3 and Glacier, Azure Blob, Wasabi, Backblaze B2) or from an on-premises appliance really takes, what it costs in retrieval, request and egress fees, and whether it fits your recovery time objective (RTO).

$ Runs in your browser. Nothing you enter is sent anywhere.

1. What you restore and from where

Restore source:

Selecting a source fills its wait time and prices. Your edits are kept until you change the source or reset.

Data to restore (TB):

TB (1 TB = 1024 GB, as billed by AWS/Azure).

Average object size (MB):

1 MB = 1,048,576 bytes. Used only to count requests (objects = data / object size, rounded up). Check what your backup software writes.

Recovery time objective, RTO (hours):

Wait before download, fast case (hours):

Time before data is available to download (archive restore / rehydration). Pre-filled from the source.

Wait before download, slow case (hours):

Time before data is available to download. Pre-filled from the source.

2. Speed limits

Restore travels over the network link

Ticked by default for cloud sources, unticked for on-premises. When unticked, only the target write and source read speeds limit the restore.

Network link (Gbps):

Decimal: 1 Gbps = 1,000,000,000 bit/s = 125,000,000 bytes/s.

Usable share of the link (%):

Assumption: protocol overhead, TCP, shared link. 1 to 100.

Restore target write speed, MB/s (decimal):

MB/s (decimal). 0 = no limit.

Backup software / source read speed, MB/s (decimal):

MB/s (decimal), incl. dedup rehydration. 0 = no limit.

Restore target is in the same cloud region (no internet egress)

When ticked, egress cost is 0 and the link above still limits speed: set it to the in-cloud throughput you expect.

3. Cost inputs

Total data stored in this bucket/account (TB):

TB (1 TB = 1024 GB). Follows the restore size until you edit it. Wasabi and B2 free egress depend on it.

Days the restored temporary copy is kept:

Glacier restores create a temporary copy billed at the S3 Standard rate while it exists.

Free egress allowance left this month (GB):

AWS: 100 GB/month, pooled across all AWS services. Azure: first 100 GB/month. Enter 0 if already used.

Advanced: prices (US East, checked 28 Sep 2026)

Retrieval ($ per GB):

Requests ($ per 1,000):

Internet egress, first tier ($ per GB):

Egress above the free 3x allowance ($ per GB):

Temporary copy, S3 Standard ($ per GB-month):

First-50-TB S3 Standard rate.

Check the highlighted inputs

Results are not calculated until every visible input is a valid number in range.

Result

– Total restore time fast case – slow case

– Transfer time

– Effective throughput, MB/s (decimal)

– Bottleneck

– Estimated restore cost

Time breakdown

Cost breakdown

What to change

Notes and assumptions

Formulas used

bytes = TB × 2^40; GB = TB × 1024

link bytes/s = Gbps × 10^9 ÷ 8 × usable %

throughput = lowest of link, target write, source read (0 = no limit)

transfer hours = bytes ÷ throughput ÷ 3600

total = wait + transfer (fast and slow case)

objects = ceil(bytes ÷ (object MB × 2^20))

retrieval = GB × $/GB; requests = objects × $/1000 ÷ 1000

egress (AWS/Azure) = tiered $/GB on (GB − free allowance)

temporary copy = GB × S3 Standard rate × days ÷ (365/12)

Estimates are a starting point. Review and test before relying on them for recovery planning; run a real test restore to measure your own speeds. Prices change: confirm on the official pricing pages (AWS S3, Azure Blob, Azure bandwidth, Wasabi, Backblaze B2).

HNOrigin is not affiliated with or endorsed by Amazon Web Services, Microsoft, Wasabi Technologies or Backblaze. Product names are trademarks of their owners.