AWS Backup & Disaster Recovery
7 questions found
What is AWS Backup and how does it simplify managing backups across multiple AWS services?
Beginner
AWS Backup is a fully managed service that lets you centralize and automate data protection across many AWS services, such as EC2, EBS, RDS, DynamoDB, and EFS, from a single console, letting you define a backup policy once and apply it consistently across all your resources instead of configuring backups separately for each individual service.
aws backup create-backup-plan --backup-plan file://backup-plan.json
Real-world example
A company with resources spread across EC2, RDS, and DynamoDB uses a single AWS Backup plan to enforce a consistent daily backup schedule and retention policy across all three services, rather than managing three separate backup processes.
Common follow-ups: What AWS services does AWS Backup support?;How does AWS Backup pricing work compared to native snapshot pricing?
RDS & Databases;Amazon EFS (Elastic File System)
What is the difference between Recovery Point Objective and Recovery Time Objective in disaster recovery planning?
Beginner
Recovery Point Objective, or RPO, defines the maximum acceptable amount of data loss measured in time, such as losing at most fifteen minutes of data, while Recovery Time Objective, or RTO, defines the maximum acceptable amount of time an application can remain down before it must be restored, and together these two metrics guide exactly how frequently you need to back up data and how quickly your recovery process must complete.
// Example targets
// RPO: 15 minutes (backups every 15 minutes)
// RTO: 1 hour (system must be restored within 1 hour)
Real-world example
A financial trading platform sets an extremely tight RPO of just a few seconds using continuous replication, since even a small amount of lost transaction data would be unacceptable, while a less critical internal tool accepts an RPO of twenty four hours.
Common follow-ups: How do RPO and RTO requirements influence the choice of disaster recovery strategy?;What is the cost tradeoff between a tighter RPO and RTO versus a more relaxed one?
RDS & Databases;AWS Global Infrastructure (Regions
AZs & Edge Locations)
What are the four common disaster recovery strategies on AWS, including backup and restore and pilot light?
Intermediate
The backup and restore strategy is the simplest and cheapest, relying purely on restoring data from backups after a disaster, accepting a longer recovery time, pilot light keeps a minimal version of critical systems always running in a secondary region ready to be scaled up quickly, warm standby runs a fully functional but smaller scale version of the environment in a secondary region that can be scaled up rapidly, and multi site active active runs full production capacity in multiple regions simultaneously for the fastest possible recovery at the highest cost.
// Pilot light example: minimal database replica always running
// scaled up to full capacity only when disaster recovery is triggered
Real-world example
An e commerce company uses a pilot light strategy, keeping a small replicated database always running in a secondary region, and only scales up the full application infrastructure in that region if its primary region experiences a major outage.
Common follow-ups: How do you decide which disaster recovery strategy fits a specific application's needs?;What is the cost comparison across all four disaster recovery strategies?
AWS Global Infrastructure (Regions
AZs & Edge Locations);Auto Scaling Groups
How do backup vaults and vault lock in AWS Backup help protect against accidental or malicious data deletion?
Intermediate
A backup vault is a logical container that organizes and stores your backups, and Vault Lock lets you apply a write once read many policy to that vault, preventing anyone, including the account root user, from deleting backups or reducing their retention period before a specified time has passed, providing strong protection against accidental deletion or a malicious actor attempting to destroy your backup history.
aws backup put-backup-vault-lock-configuration --backup-vault-name my-vault --min-retention-days 30 --max-retention-days 365
Real-world example
A company subject to strict regulatory requirements enables Vault Lock on its backup vault, guaranteeing that even a compromised administrator account cannot delete critical compliance backups before their mandated retention period expires.
Common follow-ups: Can a Vault Lock configuration ever be reversed once applied?;How does Vault Lock compare to S3 Object Lock for similar protection?
IAM;S3 & Storage
How does cross region backup copying in AWS Backup support disaster recovery objectives?
Intermediate
AWS Backup lets you configure a backup plan to automatically copy backups from the region where the resource lives into a different AWS region, ensuring that even if an entire region becomes unavailable due to a major disaster, a recent copy of your critical data remains safely available in a separate geographic location ready to support recovery efforts.
aws backup create-backup-plan --backup-plan '{"BackupPlanName":"CrossRegionPlan","Rules":[{"RuleName":"DailyBackup","TargetBackupVaultName":"my-vault","CopyActions":[{"DestinationBackupVaultArn":"arn:aws:backup:us-west-2:123456789012:backup-vault:secondary-vault"}]}]}'
Real-world example
A healthcare company configures AWS Backup to automatically copy its daily database backups from its primary region on the east coast to a secondary vault on the west coast, ensuring patient data survives even a full regional outage.
Common follow-ups: What is the additional cost of cross region backup copying?;How quickly can a cross region backup be restored compared to a local backup?
AWS Global Infrastructure (Regions
AZs & Edge Locations);AWS Cost Management & Billing
How does AWS Elastic Disaster Recovery differ from traditional backup based recovery approaches?
Advanced
AWS Elastic Disaster Recovery uses continuous, block level replication of your on premises or cloud based servers into a low cost staging area within AWS, allowing for recovery time objectives measured in minutes rather than the hours or days typical of restoring from traditional backups, since the replicated servers can be launched almost immediately as fully functioning EC2 instances during an actual disaster event.
aws drs create-replication-configuration-template --staging-area-subnet-id subnet-12345 --default-large-staging-disk-type gp3
Real-world example
A company running critical servers on premises uses Elastic Disaster Recovery to continuously replicate those servers into AWS, allowing them to fail over to fully running EC2 instances within minutes during an actual data center outage, rather than spending hours restoring from backup.
Common follow-ups: How does Elastic Disaster Recovery pricing compare to running a full standby environment continuously?;What is involved in testing a disaster recovery failover without disrupting production?
EC2 & Compute;AWS Cost Management & Billing
How should an organization test and validate its disaster recovery plan to ensure it actually works during a real event?
Advanced
Effective disaster recovery testing involves regularly performing actual failover drills, not just reviewing documentation, using tools like AWS Fault Injection Simulator to intentionally introduce failures and validate that automated recovery mechanisms behave as expected, and documenting clear runbooks with defined roles and responsibilities so that during a real event, the response is well rehearsed and confusion is minimized.
aws fis start-experiment --experiment-template-id template-12345
Real-world example
A company conducts a quarterly disaster recovery drill where it deliberately fails over its production database to a secondary region during a scheduled maintenance window, verifying that both the technical process and the team's response runbook work correctly before an actual emergency occurs.
Common follow-ups: How often should disaster recovery drills be performed for critical systems?;What is AWS Fault Injection Simulator and how does it support resilience testing?
Monitoring (CloudWatch);AWS Global Infrastructure (Regions
AZs & Edge Locations)