AWS Elastic Disaster Recovery (AWS DRS) minimizes downtime and data loss. Backup and Disaster Recovery with fast, reliable recovery of on-premises and cloud-based applications using affordable storage, minimal compute, and point-in-time recovery.
Set up AWS Elastic Disaster Recovery on your source servers to initiate secure data replication. Your data is replicated to a staging area subnet in your AWS account in the AWS Region you select. The staging area design reduces costs by using affordable storage and minimal compute resources to maintain ongoing replication. You can perform non-disruptive tests to confirm that implementation is complete. During normal operation, maintain readiness by monitoring replication and periodically performing recovery and failback drills. If you need to recover applications, you can launch recovery instances on AWS within minutes, using the most up-to-date server state or a previous point in time. After your applications are running on AWS, you can choose to keep them there, or you can initiate data replication back to your primary site when the issue is resolved. You can fail back to your primary site whenever you’re ready.
AWS offers four main disaster recovery (DR) strategies you can adopt to create backups that are available during disaster events. Each strategy has a progressively higher cost and complexity but lower recovery times:
Each DR strategy on AWS offers different recovery time objectives (RTO) and recovery point objectives (RPO). Strategies are designed at several ranges of costs and complexities.
Generally, the more complex and highly available DR strategies come with higher costs. Less complex strategies that provide lower availability are more cost-effective.
To ensure your DR strategy suits the needs of your district, test it initially and continuously.
Consider your recovery time objective (RTO) and recovery point objective (RPO), as illustrated in the image below.
The following chart shows how the four disaster recovery strategies.