Ravi Sir's Cards › AWS
RPO, RTO and strategies
This revision card explains RPO, RTO and strategies. It starts from the need that “We have backups” is not a recovery time you can sell to the business. It describes RPO is how much data you can lose; RTO is how fast you must be back. Strategies range backup/restore , then pilot light , then warm , then multi-site. The how-to section notes write RPO/RTO per app; pick strategy and region copy; run game days. An example on the card is payments: RPO 5 min + warm standby; blog: RPO 24 h + backup/restore.
Read card text
What this card says
Why do we need it?
“We have backups” is not a recovery time you can sell to the business.
What is it?
RPO is how much data you can lose; RTO is how fast you must be back. Strategies range backup/restore → pilot light → warm → multi-site.
RPO / RTO
How to do it
Write RPO/RTO per app; pick strategy and region copy; run game days.
Example
Payments: RPO 5 min + warm standby; blog: RPO 24 h + backup/restore.