The system must recover within 15 minutes and may lose at most five minutes of data.
Avoid the cost of running a full-capacity production environment in two Regions at all times.
Choose TWO appropriate elements.
RTO is recovery time and RPO is acceptable data loss. A warm standby can shorten recovery, while frequent replication or backups support a short RPO.
Detailed explanation
Building from zero is unlikely to meet a 15-minute RTO.
Building from zero is unlikely to meet a 15-minute RTO.
A warm standby is already running at reduced capacity and can target a shorter RTO than a pilot light.
A warm standby is already running at reduced capacity and can target a shorter RTO than a pilot light.
It may meet recovery targets but is likely excessive when avoiding the cost of duplicate full capacity is a requirement.
It may meet recovery targets but is likely excessive when avoiding the cost of duplicate full capacity is a requirement.
RPO is the maximum data-loss interval, so replication or backups must occur within that interval.
RPO is the maximum data-loss interval, so replication or backups must occur within that interval.
Check official documentation
Compare the following points with the official documentation.
AWSの災害復旧戦略とRTO・RPOの公式説明を確認する。
What to confirm
RTO/RPOとコスト条件からウォームスタンバイとデータ複製を選べる。
Key points
- RTO
- RPO
- Warm standby
- Data replication
Notes
- Environment: AWS公式災害復旧ガイダンスの確認
- Confirm current AWS architecture guidance and service behavior in the official documentation.
Foundation review
Recovery objectives
RTO controls how quickly service returns; RPO controls how recent recovered data must be.
Cost and readiness
A warm standby balances readiness and cost between rebuilding from backup and running full active-active capacity.