Cloud concept · Updated

Disaster recovery - Disaster recovery is the planned restoration of applications, infrastructure, and data after a disruptive event within defined downtime and data-loss limits.

In short

Disaster recovery combines recoverable data, replacement infrastructure, documented procedures, and testing to restore technology services after failures, attacks, or operational mistakes. In the cloud, it uses capabilities such as backups, replication, automated provisioning, and geographically separate deployments to balance recovery requirements against cost and complexity.

Cloud Concepts Hub →

6 key aspects of Disaster recovery

Effective disaster recovery combines measurable objectives, isolated and protected recovery resources, appropriate architecture, and repeatedly tested restoration procedures.

01
Business-driven recovery objectives

Define RTO and RPO for each workload based on the impact of downtime and lost data. Use these targets to select backup frequency, replication methods, infrastructure readiness, and testing schedules.

02
Independent recovery locations

Use separate failure domains appropriate to the threat, such as another Region for regional disruption or another account for administrative isolation. Confirm that recovery locations satisfy data residency requirements and have the necessary services, quotas, and capacity.

03
Recoverable history alongside replication

Use replication to improve data availability and retained backups to recover earlier states. Do not assume a current replica protects against logical corruption, malicious changes, or ransomware.

04
Protected backup data and encryption keys

Restrict backup deletion, apply immutable retention where appropriate, and separate backup administration from production administration. Ensure destination permissions and encryption-key policies support recovery without allowing unnecessary access.

05
Cost-aware recovery strategies

Choose between backup and restore, pilot light, warm standby, and active-active architectures according to workload requirements. Faster recovery generally requires more continuously provisioned resources and greater operational complexity.

06
Tested restoration and failback

Exercise recovery procedures with realistic dependencies and measure achieved RTO and RPO. Include application validation, traffic switching, rollback decisions, and controlled return to the primary environment.

Cloud services for Disaster recovery

AWS Backup coordinates protection and retention across supported resources, while Amazon Data Lifecycle Manager handles EBS snapshot and AMI lifecycle needs. AWS Elastic Disaster Recovery maintains server replication for recovery workflows. AWS DataSync can move file and object datasets into a recovery location, and Amazon S3 can retain versioned or retention-protected copies. AWS KMS supplies encryption-key controls that must remain usable during restoration. Together, these services support a recovery architecture, but engineers must still configure geographic and account isolation, protect historical copies, rebuild dependencies, and test complete application recovery against RTO and RPO.

AWS BackupAWS Backup

AWS Backup centrally manages backup policies, schedules, retention, and restores for supported resources, with cross-account and cross-Region copying where supported. AWS Backup Vault Lock can enforce retention controls; compliance mode prevents changes or removal after its configured grace period, helping protect recovery points against malicious deletion.

AWS Elastic Disaster RecoveryAWS Elastic Disaster Recovery

AWS Elastic Disaster Recovery replicates supported source servers into a staging area in AWS and launches recovery instances for drills or recovery. It supports lower-RPO server recovery designs, but application dependencies, validation, traffic redirection, and failback still require planning.

AWS DataSyncAWS DataSync

AWS DataSync transfers file and object data between supported storage systems, including on-premises storage and AWS storage services. It can populate or refresh recovery datasets, but independent versions, retention policies, and destination protection are needed because a transfer task alone is not an immutable backup.

Amazon S3Amazon S3

Amazon S3 provides storage for recovery data, with Versioning, replication, and Object Lock supporting different protection requirements. Object Lock protects specified object versions against deletion or overwrite according to its retention settings, while replication requires explicit configuration and monitoring.

Disaster recovery exam questions

Real practice exam questions on Disaster recovery, with the correct answer and its explanation. Answer them with every option in the exam simulator.

CLF-C02

A consulting company backs up its project-management database every night and uses infrastructure templates to recreate its application servers. During a recovery exercise, the company discovers that all database backups are stored in the same AWS Region as the production application. The company must be able to restore service if that entire Region becomes unavailable, and losing changes made since the previous night's backup is acceptable. Which improvement should the company make?

Show answerCORRECT ANSWER

Maintain copies of the database backups in another Region and test restoring the application and its data there.

Backups in another Region provide a recovery source outside the affected Region. Testing restoration verifies that the backups and infrastructure templates can be used together to restore service. Nightly backups fit the company's stated tolerance for data loss.

SOA-C03

A company uses Amazon Route 53 failover A records to route a public application to endpoints in two AWS Regions. Both records have a TTL of 3,600 seconds. The secondary endpoint is ready to serve production traffic.

A scheduled disaster recovery exercise will make the primary endpoint unhealthy and verify traffic redirection. Once Route 53 begins returning the secondary address, DNS resolvers must stop returning the cached primary address within 60 seconds. Assume that resolvers honor record TTLs, do not serve expired responses, and clients perform new DNS lookups rather than reuse existing connections. Health check detection time is measured separately.

Which preparation should a CloudOps engineer perform to meet this requirement?

Show answerCORRECT ANSWER

Reduce both failover records' TTLs to 60 seconds at least 3,600 seconds before initiating the exercise.

Waiting out the previous TTL allows answers cached with the original 3,600-second TTL to expire before the exercise. Subsequently cached answers have a TTL of 60 seconds, limiting how long compliant resolvers can continue returning the primary address after Route 53 changes its answer.

SCS-C03

A company is configuring a scheduled AWS DataSync task to copy files from an on-premises NFS server to an Amazon S3 bucket for recovery from accidental deletion or corruption. Production users cannot administer the destination bucket. The task will use TransferMode=CHANGED and map each source file to the same S3 key on every run.

The recovery design must meet these requirements:
• New and modified source files are copied during each scheduled run.
• Earlier copies of modified files remain recoverable after subsequent runs.
• If a file is deleted from the source, its most recently copied contents remain accessible through a standard S3 GET request without a version ID.

The bucket has no Lifecycle expiration rules, and no other process modifies destination objects. Which configuration meets these requirements?

Show answerCORRECT ANSWER

Enable S3 Versioning before the first transfer. Set OverwriteMode=ALWAYS and PreserveDeletedFiles=PRESERVE.

ALWAYS allows DataSync to copy changed source files over their existing destination keys. S3 Versioning retains the previous object versions for recovery. PRESERVE keeps destination objects when their corresponding source files are deleted, leaving their latest copied contents accessible without specifying a version ID.

Practice Disaster recovery in a full exam

Questions on Disaster recovery in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Disaster recovery

3 min read

Disaster recovery addresses how an organization restores technology services when their normal operating environment becomes unavailable or untrustworthy. Events include regional outages, accidental deletion, failed deployments, compromised credentials, and ransomware. It is part of business continuity, which also covers people, facilities, communications, and business processes. A disaster recovery plan must identify dependencies and recovery order: restoring an application server is insufficient if its database, identity provider, encryption keys, or network connectivity remain unavailable.

Begin with recovery time objective, or RTO, and recovery point objective, or RPO. RTO is the target maximum time to restore a service after disruption. RPO is the maximum acceptable data loss measured in time. For example, an order-processing application might require recovery within one hour and tolerate losing no more than five minutes of transactions. A daily backup alone cannot reliably meet that RPO; frequent backups, transaction-log capture, or replication would be needed. Actual recovery performance must be measured rather than inferred from a product feature.

Cloud recovery strategies range from backup and restore to pilot light, warm standby, and multi-site active-active deployments. Backup and restore generally has lower ongoing infrastructure costs but requires more rebuilding and data restoration. Pilot light keeps essential components available while other resources are deployed or scaled during recovery. Warm standby maintains a smaller functioning environment that can be expanded. Active-active deployments can reduce interruption but introduce costs and challenges around consistency, conflict resolution, routing, and operational coordination. None automatically guarantees zero downtime or zero data loss.

Availability Zones provide isolation within an AWS Region and help applications tolerate localized infrastructure failures. Multiple Zones do not provide protection against every Region-wide disruption. A secondary Region can provide geographic separation for recovery, but the application must have usable data, configuration, permissions, capacity, and recovery procedures there. Multiple Regions also support other goals, including lower latency for geographically distributed users and meeting jurisdictional requirements. These goals are distinct: copying data into another country for recovery can violate data-sovereignty restrictions unless the destination and processing arrangements are permitted.

Replication and backup solve different problems. Replication can make recent data available elsewhere, but it can also propagate corruption, unwanted changes, or encrypted files. Retained backups provide historical recovery points. For ransomware resilience, combine appropriately configured immutable retention with restricted deletion permissions, separate administrative boundaries, monitoring, and restore testing. Cross-account and cross-Region copies reduce different risks and are not interchangeable. Encrypt backups and replicated data, protect encryption keys from unauthorized use or deletion, and verify that recovery identities can decrypt the destination copies.

For example, an engineering team could centrally schedule database and volume backups, retain protected copies in a separate account, and copy supported backups to an approved recovery Region. It could also replicate critical servers to reduce recovery time. Infrastructure-as-code templates would recreate networks and application resources, while a runbook would specify database recovery, application validation, traffic redirection, and eventual failback. Recovery exercises should verify data integrity, application behavior, recovery duration, replication lag, quotas, and key access. A successful backup job is evidence that data was captured, not proof that the business service can be recovered.

Learn Disaster recovery in lessons

10 short lessons on Disaster recovery in 5 certification courses.

and 4 more lessons

Open the lessons