Aws backup and disaster recovery11/29/2023 ![]() In case of disaster entire traffic is routed to AWS and then the AWS infrastructure can be scaled accordingly. An identical solution to your on-site infrastructure runs on AWS. Multisite or active-active: Here the workload is deployed to multiple AWS Regions, and it actively serves traffic from these regions.Pilot Light cannot process requests without additional actions, whereas Warm Standby just requires you to scale up, as everything else is already deployed. Here, the recovery is fast but hosting costs are higher for large backup instances. At the time of recovery, these systems are scaled up and ready to handle the load. All the business-critical systems are always ON and completely duplicated but in a scaled-down mode. It maintains a completely functional version of your workload always running in the Disaster Recovery region, but this is scaled down. Warm Standby: This takes the Pilot-light approach to the next level by reducing recovery time to almost zero.This approach costs the least as most systems are down and are brought up only after a disaster. This version hosts the critical functionalities of the application. Here a minimal version of the environment is always running on the cloud. They are brought to use only during testing or when DR is invoked. On the other hand, application servers are loaded with configurations and application code but are switched off. Data backup and replication resources such as database and object storage are always ON. Data is replicated from one region to another and a copy of the core workload infrastructure is provisioned. Pilot Light: As per the name, this methodology uses a minimal backup environment. ![]() On the other hand, it calls for the longest recovery time as it recovers the environment from scratch. This technique costs the least because it does not host a live backup environment. AWS CodePipeline can be used for the automatic redeployment of configuration and application code. To facilitate hustle-free redeployment, Infrastructure should always be deployed using Infrastructure as Code (IaC) using services like AWS Cloud Development Kit. It is recommended to backup Infrastructure, configuration, and application code also in the Recovery Region.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |