This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Runbook — Database Backup and Restore

Capture

1. Identify engine/version, database names, schema migration state, character set/collation, extensions, and baseline ID.
2. Quiesce writes or use the engine’s transaction-consistent backup mode.
3. Export roles/schema/data separately where supported; exclude secrets from public records.
4. Encrypt restricted dumps, compute SHA-256, and record logical size/object counts.
5. Store the key separately from the dump.

Restore test

1. Provision a clean isolated database of the pinned engine version.
2. Restore roles and schemas with new disposable secrets.
3. Restore data and run engine integrity checks.
4. Compare expected table/object counts and migration state.
5. Point a generated server working copy at the restored database and execute the baseline milestone.

Destructive actions

Database reset, liquidation, migration, or custom SQL requires a verified pre-action backup, explicit target/database confirmation, and a rollback record. Never test against the only copy of user state.