Dump check
The driver checks the generated database dump. PostgreSQL lists the archive, MySQL checks for a completion marker, and SQLite runs an integrity check.
Backup recovery
Select a snapshot, recover it with your key, and check the application. A practical recovery routine starts before an incident.
Start free trial
See what it does, who it’s for, and whether it fits your needs.
Opens with product context and a link to this page.
Evidence at every stage
A backup moving successfully through one stage is useful evidence, but it does not answer every recovery question. Keep upload status, archive integrity and application recovery separate.
The driver checks the generated database dump. PostgreSQL lists the archive, MySQL checks for a completion marker, and SQLite runs an integrity check.
AES-GCM verifies the authentication tag when the client opens an encrypted archive. An invalid key or modified ciphertext causes decryption to fail.
You restore into a separate environment and check that your application can use the recovered database and files. Include this in your operating routine.
02 / Backup recovery
A restore writes to the database and directory paths in the configuration you use. Work on a separate recovery machine or isolated environment for a practice run. Review the target host, database name, SQLite path and directory paths before running the command.
Use the encryption key that matches the selected archive. Confirm that the destination has the database tools and versions needed to import the dump, enough disk space for the downloaded and extracted files, and the application configuration needed for a useful test.
03 / Backup recovery
List the available snapshots and choose an explicit backup ID. Using an ID makes it clear which point in your backup history is being recovered. Use an explicit configuration path for a dedicated recovery environment.
The client retrieves the backup metadata and download URL. If a local encrypted copy matches the recorded checksum, it can be reused; otherwise the archive is downloaded.
The client opens the archive with your configured key, checks the GCM authentication tag and extracts the compressed contents locally.
The database driver imports or copies its dump, then the configured directories are restored to their destination paths.
Confirm representative records, uploaded files, permissions and application startup. Perform a few real reads and writes in the test environment.
calmbackup --config /path/to/recovery.yaml list
calmbackup --config /path/to/recovery.yaml restore <backup-id>04 / Backup recovery
Record where to find the recovery key, how to obtain a backup ID, which configuration to use, and how to validate the result. Keep that runbook accessible if the original server is offline.
Measure the time from starting the download to a working application. Your backup frequency affects how much data you might lose; your restore procedure and environment affect how long you may be unavailable. Neither is guaranteed by a successful upload.

Repeat a restore exercise after a database upgrade, configuration change or new storage path.
Keep the original backup history and encryption keys until you have confirmed recovery in the new environment.
A closer look
Yes, the client downloads the selected encrypted archive when a suitable cached copy is not available. You still need access to the backup source and the correct encryption key.
The workflow described here restores a selected backup snapshot. It does not describe transaction-log replay to an arbitrary moment between snapshots.
Choose the snapshot that matches the incident. A recent backup can already include an accidental deletion or bad application change. Review timestamps and keep enough history for your recovery needs.

A calmer place to start
Connect a source, keep your encryption key safe, and try a restore. Make the whole routine familiar before you need it.
Start your 14-day trial