Backup, upgrade, rollback, and recovery

What to back up

Data	Recommended method	Why it matters
Omakase SQLite and data	SQLite online backup or stopped-volume snapshot	Requests, monitoring, receipts, and setup state
Secret configuration	Encrypted secret-manager backup	Master key, login, OAuth, Plex, and provider access
Plex configuration	Stopped or application-consistent snapshot	Metadata, sections, and watch state
Managed library	Filesystem backup or reproducible source plan	User-selected recovery posture
Plan and upgrade receipts	Normal durable backup	Exact apply inputs and rollback references
Transcode data	None	Disposable

Proxmox bind-mount contents are not included in vzdump; back them up separately.

Upgrade sequence

1. Run Doctor and capture the current revision and health.
2. Verify the exact new private commit or release archive hash.
3. Render every selected Compose profile.
4. Back up and integrity-check SQLite.
5. Back up Plex configuration and the current library generation.
6. Build or pull without replacing the running stack.
7. Deploy the exact revision and wait for health.
8. Prove the image revision, database migrations, login, title readiness, subtitle choices, scoped Plex scan, and representative playback.
9. Preserve the rollback receipt.

Do not update by editing tags and recreating containers by hand.

Recovery order

When a release fails:

1. disable the Omakase sync timer and optional acquisition client;
2. capture the failing logs, configuration names, and revision without credentials;
3. restore Omakase data and the exact code or image together;
4. restore Plex configuration before rebuilding libraries;
5. verify mounts and media reads before Plex scans;
6. start import-only first;
7. re-enable qBittorrent and VPN only after tunnel proof;
8. run Doctor and post-install validation;
9. replay only idempotent pending actions.

Library rollback

Omakase publishes a versioned library generation and atomically changes the stable pointer. Rollback selects a retained prior generation.

Provider media is not deleted by library rollback. Restore Plex database or section configuration only when the recorded recovery plan requires it, and stop Plex before a raw database restore.

Test the backup

A backup is not proven by successful creation. Restore to a disposable path, run SQLite integrity checks, inspect the archive manifest, and confirm the secrets backup is encrypted and recoverable by the owner.

Record the test date and the exact artifacts verified.