Storage · AZ-104 / AZ-305
Storage recovery timeline checker
Compare RPO/RTO targets, backup age at incident, and illustrative recovery phases; reinforces that replication is not backup.
Run the local exercise
Key results
| Metric | Value | Unit |
|---|---|---|
| Illustrative copy + restore + validate time | 95 | min |
| RPO check | Pass | |
| RTO phase check | Pass |
Illustrative recovery phases and target
| Metric | Value | Unit |
|---|---|---|
| Copy phase | 30 | min |
| Restore phase | 45 | min |
| Validation phase | 20 | min |
| RTO target | 120 | min |
- RPO is the acceptable data-loss window measured in time. RTO is the target time to restore usable service.
- RPO compares latest backup age at incident to the target; RTO here checks only copy + restore + validate phases.
- Detection and incident start delay are excluded unless supplied; this cannot certify end-to-end disaster recovery.
Experiment steps
- Set objectives, backup age at incident, and illustrative phase durations.
- Check whether RPO passes, and compare copy + restore + validate with RTO.
- Record validation; do not equate file copy completion with business recovery.
Sources, formula, and limitations
Original illustrative recovery timeline; total phase time = copy + restore + validate. RPO compares latest backup age at incident with the target.
This is a 2026-10-10 teaching sample, not an Azure Backup or storage replication benchmark; detection and start delay are excluded.
Teaching timeline only; it cannot certify end-to-end disaster recovery and does not represent measured Azure performance.