FOCUSCurrently working on ScheduleSomething and LayerdEvents algorithmsLearn More
FOCUSCurrently working on ScheduleSomething and LayerdEvents algorithmsLearn More
FOCUSCurrently working on ScheduleSomething and LayerdEvents algorithmsLearn More
FOCUSCurrently working on ScheduleSomething and LayerdEvents algorithmsLearn More
CONTRIBUTING.MdOperations & Runbooks
Backup & Disaster Recovery
DocsCONTRIBUTING.mdOperations & RunbooksBackup & Disaster Recovery
GitHub Live Sync

Backup & Disaster Recovery

Live technical documentation fetched from GitHub repository omghante/metapilot/docs/operations/backup-recovery.md

Backup & Recovery Policies

Procedures for database backups, Fernet key management, and disaster recovery.

1. Database Backup Policy

PostgreSQL Production Backup

Execute automated daily database dumps using
pg_dump
:
bash
pg_dump -h localhost -U metapilot -F c -b -v -f "/backups/metapilot_$(date +%Y%m%d_%H%M%S).dump" metapilot

Retention Schedule

  • Daily Dumps: Retained for 30 days.
  • Weekly Dumps: Retained for 12 months.

2. Fernet Key Backup

[!CAUTION] If
FERNET_KEY
is lost, encrypted tenant access tokens in
tenants_tenantconfig
cannot be recovered.
  • Backup Standard:
    FERNET_KEY
    must be stored securely in an encrypted secret store (HashiCorp Vault, AWS Secrets Manager, 1Password Teams).
  • Never commit
    .env
    files to git repositories.