Skip to main content
A backup is a point-in-time snapshot of a connected database, encrypted and compressed, stored in your chosen storage. DBDock Cloud runs the same engines as the CLI — see Concepts for the backup pipeline and formats.

​
Create a backup

1

Open Backups → New backup

Choose the connection to back up.
2

Pick a destination

Select managed storage or one of your own buckets. Defaults to your primary storage.
3

Start it

Watch live progress. When it finishes, the backup appears in the list with its size, duration, and status.
To run backups automatically, create a schedule instead of starting them by hand.

​
Restore a backup

Open any completed backup and choose Restore. You can restore into the original database or a different connection — useful for refreshing staging from production.
Restoring overwrites data in the target database. Double-check the target connection before you confirm.

​
Manage backups

Failed backups can be retried from the list. The logs explain what went wrong — a common cause is an unreachable database or a storage credential issue.
Download the encrypted backup file to keep an off-platform copy. You’ll need your encryption secret to restore it later — see Key management.
Every backup keeps detailed logs, including timing and any errors, so you can diagnose issues without guesswork.
Remove a backup you no longer need. See Deletion safety for how DBDock protects against accidental data loss.

​
Retention

Instead of deleting backups by hand, set a retention policy so DBDock keeps the right number and cleans up the rest automatically. Retention has three controls — a maximum count, a maximum age, and a floor that’s never crossed. See Retention strategies.

​
Encryption

Backups are encrypted with AES-256-GCM. On paid plans, encryption is on by default. The encryption secret is what makes a backup restorable — store it safely and separately from the backups themselves. See Encryption.

Schedules

Automate backups with cron.

Storage

Where backups are stored.