Origin by Corvus - Backup, Recovery & Disaster Resilience
Zero-Data-Loss Architecture, Encrypted Snapshots & Point-In-Time Restoration
Quantum Tiger (Morning Bay Technology Pvt. Ltd.)
Mission-critical disaster recovery runbook, automated snapshot retention, and validation test suites.
Docs Hub - User GUIDE - Install - [SYNC] Updates
Backup Architecture & Topology
Origin by Corvus separates structured relational state from binary file storage to ensure point-in-time recovery:
Backup Component Matrix
| Subsystem | Stored Data | Backup Mechanism | Default Schedule | Retention Policy |
|---|---|---|---|---|
| PostgreSQL Database | Channels, messages, users, teams, permissions, plugin state | pg_dump -Fc (Compressed Custom Format) | Daily at 02:00 AM UTC | 30 Days (Rolling) |
| MinIO S3 Object Store | Uploaded documents, audio/video recordings, image attachments | tar -czf of minio_data volume | Weekly Sunday 03:00 AM UTC | 30 Days (Rolling) |
| Configuration & Secrets | docker-compose.yml, .env, nginx.conf, TLS keys | Compressed archive with SHA-256 hash | On Every Update / Manual | Permanent |
Instant Manual Backup (Single Command)
Create an instantaneous, consistent snapshot of both database and object volumes:
# Linux / macOS
sudo ./install.sh backup
# Or using the Linux PATH convenience command:
origin-backup
# Windows Server (PowerShell)
.\install.ps1 backup
Interactive Operations Menu: You can also run
sudo ./install.sh(or.\install.ps1) without arguments and select Option 7 (Create manual backup).
Expected Command Output (Click to Expand)
[INFO] Initiating manual backup of Origin by Corvus stack...
[[OK]] PostgreSQL database dumped: /opt/origin/backups/manual-db-2026-11-08-1630.dump (42 MB)
[[OK]] Persistent volumes archived: /opt/origin/backups/manual-volumes-2026-11-08-1630.tar.gz (185 MB)
[[OK]] SHA-256 checksums calculated and verified.
[[OK]] Backup verified and stored in /opt/origin/backups/
[SYNC] Automated Backup Automation Setup
Linux: Automated Cron Schedule (/etc/cron.d/origin-backup)
The production installer automatically registers a dedicated cron schedule:
# /etc/cron.d/origin-backup
# Nightly PostgreSQL dump at 02:00 AM
0 2 * * * root /opt/origin/install.sh backup > /var/log/origin-backup.log 2>&1
# Weekly volume snapshot pruning older than 30 days
0 3 * * 0 root find /opt/origin/backups/ -type f -mtime +30 -delete
Windows: Task Scheduler Script
$Action = New-ScheduledTaskAction -Execute "PowerShell.exe" -Argument "-ExecutionPolicy Bypass -File C:\Origin\install.ps1 backup"
$Trigger = New-ScheduledTaskTrigger -Daily -At 2am
Register-ScheduledTask -TaskName "OriginBackup" -Action $Action -Trigger $Trigger -User "SYSTEM"
Step-by-Step Disaster Recovery & Restoration
In the event of hardware failure, catastrophic corruption, or server migration, follow this verified restoration runbook:
Complete Terminal Restoration Sequence:
# 1. Navigate to deployment directory
cd /opt/origin
# 2. Stop Origin application to ensure zero active database writes
docker compose stop origin
# 3. Restore the PostgreSQL database from a specific snapshot dump
docker compose exec -T postgres dropdb -U origin_user origin_db || true
docker compose exec -T postgres createdb -U origin_user origin_db
docker compose exec -T postgres pg_restore -U origin_user -d origin_db < /opt/origin/backups/manual-db-2026-11-08-1630.dump
# 4. Restore MinIO file attachments volume (if migrating or recovering storage)
tar -xzf /opt/origin/backups/manual-volumes-2026-11-08-1630.tar.gz -C /var/lib/docker/volumes/
# 5. Restart Origin application stack
docker compose up -d origin
# 6. Verify cluster health
docker compose exec -T origin curl -fsS http://localhost:8065/api/v4/system/ping
[!TIP] The health check must return
{"status":"OK"}. After restoration, log in to the System Console and verify that user channels, message history, and file attachments are immediately accessible.