Backup and Disaster Recovery · #57
Online Restore Time Calculator
Calculates how long a restore takes and whether it fits the RTO.
- Data is processed in your browser and not sent to a server
Tool
What does this tool do?
Backup speed and restore speed differ: reading from deduplicated repositories, rehydration and target writes are usually slower. Hardware/VM preparation comes before the data transfer and application validation after it. The tool adds these steps up.
How to use it
- Enter the data volume and measured restore speed.
- Add preparation (hardware, network, VM creation) and verification (application test) in minutes.
- Enter the RTO in hours; press Calculate.
Fields
- Data volume
- Used space to restore.
- Restore speed
- MB/s measured in a test restore.
- Preparation (min)
- Recovery environment, network, identity.
- Verification (min)
- Service start, data check.
- RTO target (hours)
- Optional.
Worked example
| Input | Value |
|---|---|
| Data volume | 2000 |
| Restore speed | 200 |
| Preparation (min) | 30 |
| Verification (min) | 0 |
| RTO target (hours) | 4 |
Expected result: 2,000 GB at 200 MB/s → 2 h 46 min 40 s transfer + 30 min preparation = 3 h 16 min 40 s; meets the 4-hour RTO with 43 min to spare.
A warning appears when the margin is below 20 % of the RTO; this is borderline. Instant recovery in backup software can bring RTO down to minutes while the transfer completes in the background.
Second scenario
| Input | Value |
|---|---|
| Data volume | 6000 |
| Restore speed | 150 |
| Preparation (min) | 60 |
| Verification (min) | 45 |
| RTO target (hours) | 8 |
Expected result: 6,000 GB at 150 MB/s, 60 min preparation, 45 min verification: 12 h 51 min 40 s; the 8-hour RTO is exceeded by 4 h 51 min 40 s.
Method and assumptions
Transfer = GB × 1000 / (MB/s) seconds. Total = transfer + preparation + verification. The difference to RTO is shown; a margin below 20 % gives a warning.
Using the result and troubleshooting
Always take the speed from a real test restore, not from backup speed. If the RTO is not met, consider instant recovery, replication or faster storage.
Limits and common mistakes
- Parallel restores, network bottlenecks and application dependency order are not modelled; use the DR startup sequence tool for dependencies.
Frequently asked questions
Why is restore slower than backup?
Deduplicated data is reassembled (rehydration), target writes are sequential and compression is undone. The gap is large on spinning-disk deduplication appliances.
Related tools and service
- RPO and RTO Gap MatrixCompares target and actual RPO/RTO per system and lists the gaps.
- Backup Window Bandwidth CalculatorCalculates the speed needed to move a data volume within a time window and the duration on an existing link.
- DR Startup Sequence PlannerCalculates from a dependency list in which order and parallel waves systems start.
Related service: Backup and Disaster Recovery