Mimir

Database Recovery Runbook

runbook
platform
afbe697f9245

runbooks/database-recovery.md

Database Recovery Runbook

Database recovery begins with impact classification: single tenant, service-specific schema, or shared platform. Restore from point-in-time backup to an isolated instance before promoting any recovery target.

Inventory synchronization issues should first replay warehouse events from the durable event log. Billing data recovery must preserve invoice sequence numbers and payment idempotency keys. Authentication recovery must never restore stale refresh tokens over newer revocations.