0Tyler
/
nd063-c2-design-for-availability-resilience-reliability-replacement-project-starter-template
Public
forked from udacity/nd063-c2-design-for-availability-resilience-reliability-replacement-project-starter-template
-
Notifications
You must be signed in to change notification settings - Fork 0
/
estimates.txt
14 lines (14 loc) · 1009 Bytes
/
estimates.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
1. Minimum RTO for a single AZ outage : Just take few minutes if the Multi-AZ deployment has been configured.
2. Minimum RTO for a single region outage :
00:00 - Problem happens (0 minutes)
00:05 - An amount of time passes before an alert triggers (5 minutes)
00:06 - Alert triggers on-all staff (1 minute)
00:16 - On-call staff may need to get out of bed, get to computer, log in, log onto VPN (10 minutes)
00:26 - On-call staff starts diagnosing issue (10 minutes)
00:41 - Root cause is discovered (15 minutes)
00:46 - Remediation started (5 minutes)
00:56 - Remediation completed (10 minutes)
Total time: 56 minutes
3. Minimum RPO for a single AZ outage : A few minutes of data be lost because Amazon RDS automatically maintains a synchronous standby replica in a different AZ.
4. Minimum RPO for a single region outage : it's about 5 minutes to uploads transaction logs, so the RPO is about 10 minutes to the replica database.
(Ref:https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PIT.html)