Basic Information
| Field | Details |
|---|---|
| English name | AWS Elastic Disaster Recovery (AWS DRS) |
| Full name | AWS Elastic Disaster Recovery |
| Chinese description | AWS 弹性灾难恢复 |
| Japanese description | AWS Elastic Disaster Recovery（災害復旧サービス） |
| Exam frequency | ⭐⭐⭐⭐ |
| Often confused with | AWS Backup / EBS Snapshot / Storage Gateway |
In one sentence
AWS DRS protects physical, virtual, and other-cloud servers with continuous block replication to reduce RPO and RTO.
Core purpose
- An agent copies changed blocks from source servers into a low-cost AWS staging area.
- Tests or incidents launch recovery EC2 instances, followed by validation, failover, and later failback planning.
- Continuous replication narrows data loss, but networking, DNS, launch settings, and application dependencies still require testing.
Exam focus
- Disaster recovery, continuous replication, and rapid full-server recovery point to AWS DRS.
- EBS snapshots protect volumes, AWS Backup governs multiple services, and Storage Gateway provides hybrid storage interfaces.
- Architecture questions balance RPO, RTO, recovery drills, and standby-environment cost.
Common misconceptions
- DRS is not an ordinary long-term backup service.
- Continuous replication does not remove the need to test consistency, DNS, and application dependencies.
Key takeaway
Backup protects data; DRS brings complete servers and services back online faster.
Related services
EC2, AWS Backup, EBS Snapshot, Route 53, Storage Gateway.