Database60-90 min

Database Backup and Restore

Automate backups, encrypt and store them safely, regularly test restores, and document recovery steps.

PostgreSQLpg_dumpS3Cron

Prerequisites

A PostgreSQL database.
Storage for backups such as S3, R2, or a managed provider backup system.
A staging database for restore testing.

Plan the implementation

Start by choosing the exact page, route, API, or deployment surface you want to improve. A narrow target makes the implementation measurable and easier to verify.

Write down the current behavior and the user-facing problem it creates.
Pick one measurable success signal such as bundle size, latency, error rate, security coverage, or UI responsiveness.
Identify the files, routes, providers, and environment variables involved.
Create a rollback note before changing production-sensitive configuration.

Set up the required tools

Install or configure only the tools needed for this implementation. Keep config close to the feature so future developers can find the moving parts quickly.

Implementation snippet

pg_dump --version
psql --version

Checklist

Dependencies are added to the correct workspace package.
Environment variables are documented in `.env.example` when needed.
Local development still starts without production-only secrets.
The change is small enough to review in one pull request.

Implement the core pattern

Choose backup frequency based on acceptable data loss.
Use `pg_dump` or managed backups for logical backups.
Upload backups to durable storage outside the database server.
Encrypt backups or rely on encrypted storage with strict access control.
Practice restoring into staging and record the recovery time.