AWS Elastic Disaster Recovery のアイコン

AWS Elastic Disaster Recovery Specialized2021年〜

A service that continuously replicates on-premises or other cloud servers to AWS for disaster recovery

What It Does

AWS Elastic Disaster Recovery (DRS) continuously replicates servers from on-premises or other clouds to AWS, enabling failover in minutes during a disaster. Block-level replication synchronizes OS and application changes to AWS in real time.

Use Cases

It is used for building disaster recovery sites on AWS for on-premises servers, securing DR environments from other clouds, and meeting compliance requirements for disaster recovery plans. Regular failover drills can also be conducted.

Everyday Analogy

Think of it like real-time backup of important documents. Every time a document is updated at the office (on-premises), a copy is automatically stored in a remote vault (AWS). Even if the office is hit by a disaster, you can retrieve the documents from the vault and resume operations immediately.

What Is Elastic Disaster Recovery?

AWS Elastic Disaster Recovery is a service that enables server disaster recovery (DR) in the cloud. Install an agent on the source server, and block-level disk changes are continuously replicated to AWS. During a disaster, EC2 instances are launched from the replicated data, enabling recovery in minutes.

How Replication Works

The AWS Replication Agent installed on the source server detects block-level disk changes and transfers them to an AWS staging area over encrypted communication. Data is stored on low-cost EBS volumes in the staging area. Production-spec EC2 instances are launched only during failover, keeping standby costs to a minimum. For the latest trends and practical techniques on replication, related books (Amazon) are also available.

Getting Started

Configure replication settings in the DRS console and install the Replication Agent on the source server. Once the initial sync completes, continuous replication begins. Use 'Launch drill' to run failover tests and validate your recovery procedures. Test instances do not affect the production environment.

Things to Watch Out For

  • During replication, charges apply for staging area EBS volumes and data transfer. EC2 instance charges are added only during failover
  • RPO (Recovery Point Objective) is typically seconds and RTO (Recovery Time Objective) is minutes, but varies based on server configuration and data volume
共有するXB!