Rejourney | Open Source Session Replay & Observability
REJOURNEY

Self-Hosting

Backup & Recovery

Self-Hosted Backup & Recovery

For the official single-node Docker Compose deployment, the critical data is:

  • Postgres
  • .env.selfhosted
  • MinIO data if you use built-in MinIO

Quick Backup

Use the bundled helper:

./scripts/selfhosted/backup.sh
./scripts/selfhosted/backup.sh --full

What it does:

  • Postgres dump every time
  • Redis snapshot when available
  • .env.selfhosted copy every time
  • MinIO object data when --full is used and built-in MinIO is enabled

What to Save

Always save

  • backups/postgres-*.sql.gz
  • backups/env-*

Save when using built-in MinIO

  • backups/minio-*.tar.gz

If you use external S3, your recordings live in that bucket instead of the local MinIO volume, so the database plus .env.selfhosted are the minimum local backups.

Restore Order

1. Recreate the stack config

Put the saved .env.selfhosted back in the repo root.

2. Start infrastructure and bootstrap

./scripts/selfhosted/deploy.sh update

This brings the services back and recreates the storage_endpoints row from your saved config.

3. Restore Postgres

gunzip -c backups/postgres-YYYYMMDD-HHMMSS.sql.gz | \
  docker compose -f docker-compose.selfhosted.yml --env-file .env.selfhosted exec -T postgres \
  psql -U rejourney rejourney

4. Restore MinIO, if applicable

If you use built-in MinIO and you took a --full backup:

gunzip -c backups/minio-YYYYMMDD-HHMMSS.tar.gz | \
  docker run --rm -i -v rejourney_miniodata:/data alpine tar xf - -C /data

5. Restart app services

./scripts/selfhosted/deploy.sh update

That reruns bootstrap and restarts the app services after the restore.

Recommended Schedule

Daily database backup:

0 3 * * * cd /opt/rejourney && ./scripts/selfhosted/backup.sh >> /var/log/rejourney-backup.log 2>&1

Weekly full backup with MinIO data:

0 4 * * 0 cd /opt/rejourney && ./scripts/selfhosted/backup.sh --full >> /var/log/rejourney-backup.log 2>&1

Disaster Recovery Notes

You need all of the following to fully restore a built-in-MinIO deployment:

  • .env.selfhosted
  • Postgres backup
  • MinIO backup

Without .env.selfhosted, you may lose access to encrypted storage credentials in Postgres because STORAGE_ENCRYPTION_KEY lives there.

Verification Checklist

After a restore:

  1. run ./scripts/selfhosted/deploy.sh status
  2. log into the dashboard
  3. open an existing project
  4. open an existing replay
  5. record one new short session and verify it appears

If replay ingestion fails after restore, check:

./scripts/selfhosted/deploy.sh logs ingest-upload
./scripts/selfhosted/deploy.sh logs ingest-worker