The 4 most common Disaster Recovery architectures on AWS
A disaster recovery plan, or Disaster Recovery plan, is a recovery process that covers data, hardware, and software that a company may have lost in a disaster. Having this plan is essential to ensure the continuity of your business. Let's look at the main disaster recovery architectures that AWS offers.
To develop such a plan, it is essential to invest time and resources in order to minimize the time to restore damaged systems. Using the resources and tools of Amazon Web Services (AWS) provides you with a wealth of DR benefits. Plus, it gives you access to a fast, reliable, secure infrastructure that runs on your own global platform and provides the flexibility to quickly change and optimize resources during a DR event.
If you found this post interesting, don't forget to download our free ebook: Using Amazon Web Services for Disaster Recovery.
Disaster Recovery Scenarios on AWS
Next, we will see what are the Four Most Common DR Scenarios in AWS, what they consist of and what their benefits are. This will help your company to establish a Disaster Recovery Plan on the Amazon platform capable of recovering data and files in the event of a system failure.
Backup and Restore
Scenario consisting of Back up your current software to replicate your data to AWS. Companies use Amazon S3 for short-term storage, while they typically use Amazon Glacier for longer-term storage.
In the event of a disaster, you can implement system restoration more quickly and keep data available in your infrastructure long-term.
Pilot Light
Scenario in which A minimal version of the system runs in the cloud to ensure the production environment is provisioned quickly. Unlike the previous data-centric scenario, the pilot light Also includes applications.
In the event of a disaster, you have a core around which all the other pieces of the AWS infrastructure can be efficiently provisioned to restore the system. When you initiate a data or application recovery, you will typically have preconfigured servers grouped together as Amazon Machine Images (AMIs).
Warm Standby
Solution that extends the elements of pilot light and preparation. It works from a stripped-down version that always runs in a fully functional environment within the cloud.
Having some services running constantly reduces disaster recovery time. By identifying business-critical systems, you can fully duplicate systems on AWS and have them always up.
multisite
Use weighted DNS loads, such as Amazon Route 53, to route production traffic to the different sites that deliver the same application. Some traffic will go to infrastructure in AWS, and the rest to on-premise infrastructure. IT will determine how much application traffic should be processed locally and how much in AWS.
In the face of a disaster, You can adjust DNS weighting and send all traffic to AWS serversAWS service capacity can be quickly scaled up to handle full production load.
What do you think? Now you know the most common Disaster Recovery architectures in AWS.
If you want to learn more about these scenarios or would like to learn more about how AWS can help you with your disaster recovery plan, we recommend: download our new free guide.
