AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Aws backup and disaster recovery12/11/2023 ![]() ![]() Service validation tests provide metrics on the function and correctness of your API operations.Service API metrics such as error rates and response latencies are a good way to understand your workload health.Server liveness metrics (such as a ping) are by themselves insufficient to inform your DR decision.It relies in part on Amazon CloudWatch alarms that enable you to determine your workload health based on metrics such as: In a previous blog post, I showed how quick detection is essential for low RTO, and I shared a serverless architecture to achieve this. When a disaster occurs, successful recovery depends on detection of the disaster event, restoration of the workload in the recovery Region, and failover to send traffic to the recovery Region. Recovery with pilot light or warm standby This is because pilot light requires you to first deploy infrastructure and then scale out resources before the workload can handle requests. Then it requires you to scale out this existing deployment, which gives it a lower RTO time than pilot light. Warm standby can handle traffic at reduced levels immediately. Figure 2 shows an EC2 Auto Scaling group that is configured, but it has no deployed EC2 instances. Similarly, the DR Region in a pilot light strategy (unlike warm standby) cannot serve requests until additional steps are taken. It provides a quick way to light the furnace burners that then provide heat. If the passive stack is deployed to the recovery Region at full capacity however, then this strategy is known as “hot standby.” Because warm standby deploys a functional stack to the recovery Region, this makes it easier to test Region readiness using synthetic transactions.Ī pilot light in a home furnace does not provide heat to the home. ![]() It may be more, but is always less than the full production deployment for cost savings. This is shown as one Amazon Elastic Compute Cloud (Amazon EC2) instance per tier in Figure 3. The DR endpoint can handle requests, but cannot handle production levels of traffic. The warm standby strategy deploys a functional stack, but at reduced capacity. The primary difference between the two strategies is infrastructure deployment and readiness. Differences between these two DR strategies RPO for these strategies is similar, since they share a common data strategy. However, the extent of workload infrastructure readiness differs between the two strategies, as detailed in the next section.Īs required for all active/passive strategies, both require a means to route traffic to the primary Region, and then fail over to the recovery Region when recovering from a disaster. For both strategies, the deployed infrastructure will require additional actions to become production ready. This includes support infrastructure such as Amazon Virtual Private Cloud (Amazon VPC) with subnets and routing configured, Elastic Load Balancing, and Amazon EC2 Auto Scaling groups. Resources used for the workload infrastructure are deployed in the recovery Region for both strategies. Backups are necessary to enable you to get back to the last known good state. ![]() This is because when human action type disasters occur, data can be deleted or corrupted, and replication will replicate the bad data. In addition to replication, both strategies require you to create a continuous backup in the recovery Region. These data resources are ready to serve requests. Warm standby DR strategy Similarities between these two DR strategiesīoth strategies replicate data from the primary Region to data resources in the recovery Region, such as Amazon Relational Database Service (Amazon RDS) DB instances or Amazon DynamoDB tables. ![]()
0 Comments
Read More
Leave a Reply. |