Database Runbook
Schema changes should follow:
On this page ▾
Migration lifecycle
text
model/schema change
│
▼
migration generation
│
▼
migration review
│
▼
test database
│
▼
deploymentProduction rule
Never run destructive schema commands against production without a reviewed migration/backup strategy.
Backups
Production backups should be:
- automated
- encrypted
- monitored
- periodically restore-tested
A backup that has never been restored is not a verified recovery mechanism.
Something wrong or missing on this page?Report a docs issue