Nightly Backups Run. Are You Actually Covered?
Automated backups have run for months. A teammate says you are fully covered for disasters. Defend whether you agree.
Answer key reviewed by Branko Petric
Read first: AWS Databases: RDS and DynamoDB
Your decision
Your team set up automated nightly database backups months ago. A teammate says we are fully covered if anything goes wrong. Do you agree, and what would you check?
The situation
Your team configured automated nightly database backups several months ago. They have been running ever since, and the backup job reports success in the logs every night.
Context
The backups are written to a folder on the same server that runs the database. No one has ever performed a restore from them. A teammate says there is nothing to worry about because backups are running, so the team is fully covered.
Related challenges
- Add a NOT NULL Column to a 50M-Row Prod Table
A migration adds a NOT NULL column to a huge live table. A teammate wants to run the ALTER directly. Defend the safe path.
- Your Primary Region Is Down. Fail Over Now?
The primary region is degraded. A teammate wants to flip DNS to the standby immediately. Defend whether and how you fail over.
- Every Deploy Hammers the Database for 10 Minutes. Bigger DB?
Each deploy flushes the cache and the database melts for 10 minutes while it refills. A teammate wants to double the database size. Defend fixing the stampede instead of paying for peak.
- Failover Lost 5 Minutes of Writes. Promise Zero Data Loss?
An async-replica failover dropped five minutes of committed writes. Leadership demands zero data loss with zero performance impact. Defend the honest trade-off.
More: Database scenario interview questions for DevOps and SRE