1. Home
  2. Docs
  3. Deployment & infrastructure
  4. Storage, backup and recovery
Deployment & infrastructure

Storage, backup and recovery

Protect database and uploaded files, keep backups separate from the host, and prove that restoration works.

Developer v2026.10 Updated 7 Nov 2026

What to back up

At minimum protect PostgreSQL and all persistent operational file storage. If Redis contains only reconstructable cache/queue state, recovery requirements differ from the database; document that explicitly.

Backup pattern

  • Take regular PostgreSQL backups in a restorable format.
  • Replicate backups off the application host.
  • Back up or replicate object/file storage according to retention needs.
  • Encrypt backup locations and restrict access.
  • Test restoration on a schedule.

Before risky changes

Create and validate a fresh backup before schema migrations, host migration, volume changes, or major version upgrades.

Application keys

Preserve encryption and blind-index keys when restoring existing encrypted data. Replacing those keys can make stored values unreadable or make exact-match lookups stop matching existing records.

Was this page helpful?

Still stuck?

Open a ticket and reference this page — we will pick it up from there.

Open a ticket