Databases / Operate
Database operations, backed by evidence.
Know what you can lose, how quickly you must recover, and who acts when the system fails. Use the checklist to record the work still ahead.
Before checking a box
Keep the evidence beside the answer.
For each check, record an owner, a date, a link to the evidence, and the next review. A successful backup job is evidence that a job ran. A restore drill that verifies application data is stronger evidence that the backup can serve its purpose.
Set the recovery point objective (RPO) as the amount of data loss the business can accept, and the recovery time objective (RTO) as the time available to restore service. Measure detection, preparation, restoration, validation, and the return to service when rehearsing recovery.
This checklist tracks progress across ten areas. Its count is a self-assessment, and every area still needs a workload-specific standard for completion.
Operate
Be ready for the day something fails.
Check an item only when you have evidence behind it. Record the gaps, name an owner, and test recovery before relying on it.
Your operations checklist
0 / 10
Next: agree recovery targets.
This is your self-assessment, not a certification. Progress stays in this browser.
Download checklist ↓Follow the restore drill →Keep the review current
Repeat it when the system changes.
A checklist completed for one deployment may not describe the next. Revisit it after a major schema change, a move between regions, a material workload increase, a new integration, or a change in the operating team.
Use the downloadable checklist in the review to identify incomplete work and assign responsibility. Progress is saved in this browser on this device; download a copy when you need a record to keep or share.