An ERP application is deployed across multiple AZs in a single region. In the event of failure, the RecoveryTime Objective (RTO) must be less than 3 hours, and the Recovery Point Objective (RPO) must be 15 minutes
the customer realizes that data corruption occurred roughly 1.5 hours ago.
What DR strategy could be used to achieve this RTO and RPO in the event of this kind of failure?
A.
Take hourly DB backups to S3, with transaction logs stored in S3 every 5 minutes.
B.
Use synchronous database master-slave replication between two availability zones.
C.
Take hourly DB backups to EC2 Instance store volumes with transaction logs stored In S3 every 5 minutes.
D.
Take 15 minute DB backups stored In Glacier with transaction logs stored in S3 every 5 minutes.
A, dump everything in S3
http://www.aiotestking.com/amazon/what-dr-strategy-could-be-used-to-achieve-this-rto-and-rpo-in-the-event-of-this-kind-of-failure/
Answer A : http://jayendrapatil.com/category/disaster-recovery/
An ERP application is deployed across multiple AZs in a single region. In the event of failure, the Recovery Time Objective (RTO) must be less than 3 hours, and the Recovery Point Objective (RPO) must be 15 minutes. The customer realizes that data corruption occurred roughly 1.5 hours ago. What DR strategy could be used to achieve this RTO and RPO in the event of this kind of failure?
Take hourly DB backups to S3, with transaction logs stored in S3 every 5 minutes
Use synchronous database master-slave replication between two availability zones. (Replication won’t help to backtrack and would be sync always)
Take hourly DB backups to EC2 Instance store volumes with transaction logs stored In S3 every 5 minutes. (Instance store not a preferred storage)
Take 15 minute DB backups stored in Glacier with transaction logs stored in S3 every 5 minutes. (Glacier does not meet the RTO)