AWS Elastic Disaster Recovery Service (DRS)  sandbox 

Questions

  1. How does it compare with other AWS tools like VM import/export, Server Migration Service, AWS Migration Service (MGN)

Unique property others don’t have - failover orchestration.

Elastic Disaster Recovery (DRS)

The full name is Elastic Disaster Recovery. However, the short form is DRS (Disaster Recovery Service).

What does it do?

Failover from on-prem to AWS Failover from any cloud to AWS Failover from 1 AWS region to another AWS region No need to maintain a duplicate recovery site Agent based - need to install an agent on source server to replicate data to AWS. DRS launches replication servers on AWS side for replicating data from source, these servers are lightweight. During replication, EBS is created corresponding to the source server disk. Snapshots are taken at regular intervals and customers can define a retention period. Any recovery drill carried out on AWS side, has no impact on source apps or replication. Converts the source server boot disk to boot successfully on EC2, customers can provide custom scripts to complement this automatic conversion too. Replicate source network (only if source server is on AWS). Basically captures all configuration related to the source network (possibly from config) and creates a {{ relref “cloudformation” }} template to be deployed into a new region as part of recovery.

What can it NOT do?

Recover to Outposts that CloudEndure Disaster Recovery (discontinued for all regions except China, GovCloud) can do. Is it Regional or Global? Regional, does not support China or Gov Cloud.

Key Concepts

RPO RTO Staging Account Target Account Source Replication

Limits?

Default limit of 3000 servers into a single target account. Customers can use multiple target accounts, or request a limit increase. Limit of 300 servers into a single staging account. To recover say 1000 servers into a single target account, customers can use multiple staging accounts.