Skip to main content

​
On-demand backup

You can trigger a backup at any time from the Capsule TUI: 
capsule
Navigate to your connection → Backup now. Capsule runs the backup immediately and uploads the result to your dashboard. You can also trigger on-demand backups from the web dashboard without touching the CLI.

​
Scheduled backups

Backups run automatically according to the schedules you configure. See capsule schedule for setup. The Capsule daemon must be running for scheduled backups to fire. Check with: 
systemctl is-active capsule

​
Restore

​
From the CLI

capsule
Navigate to your connection → Backups → select a snapshot → Restore. Capsule will:
  1. Download the encrypted backup from the cloud
  2. Verify the SHA-256 checksum
  3. Decrypt it locally
  4. Pipe it into your database using the native restore tool (psql, mysql, mongorestore)
Restoring overwrites the current contents of the target database. Capsule will ask you to confirm before proceeding.

​
From the dashboard

Open your dashboard, find the backup you want to restore, and click Restore. The dashboard sends a signal to the agent running on your server — the restore runs locally, never through Capsule’s servers.

​
How backups are stored

PropertyDetail
EncryptionAES-256-GCM, encrypted on your server before upload
IntegritySHA-256 checksum verified on every backup and restore
FormatCompressed dump (pg_dump, mysqldump --single-transaction, mongodump --archive)
StorageCapsule-managed Cloudflare R2
RetentionDetermined by your plan and per-schedule retention setting

​
Restore to a different host

To restore a backup to a different server (e.g. production → staging), add the target connection to Capsule, then select the source backup and choose the destination connection when prompted.
Full cross-host restore from the dashboard is coming in a future release.