Restore checklist
A recovery rehearsal you can repeat.
A practical checklist for choosing a snapshot, preparing a safe destination, validating the application and recording the result.
Start free trial
Ask AI about CalmBackup
See what it does, who it’s for, and whether it fits your needs.
Opens with product context and a link to this page.
View or copy the prompt
01 / Restore checklist
Before you touch the restore command.
Choose what this rehearsal needs to prove: recovery after losing a server, recovery from an earlier snapshot, or simply that a new backup setup works. Write down the expected outcome so a successful command is not the only pass criterion.
- 01
Identify the snapshot
Record the source, backup identifier and timestamp. Choose data that lets you check meaningful application behavior.
- 02
Recover the key
Confirm you can access the encryption key without relying on the source machine. Use the key associated with this archive.
- 03
Prepare an isolated destination
Install the database tools and application dependencies. Confirm the target database and file paths; separate the environment from production traffic and outbound integrations.
- 04
Review the configuration
Use an explicit recovery configuration. Have another operator check the destination when the rehearsal involves valuable existing data.
02 / Restore checklist
Run the restore. Keep the evidence.
The CLI obtains the archive, authenticates and decrypts it, extracts the contents and invokes the database restore. Record the output and any warnings. Stop to understand unexpected errors rather than treating a partially completed import as success.
calmbackup --config /path/to/recovery.yaml restore <backup-id>03 / Restore checklist
Check what your users would notice.
Assign an owner to any problem found during the rehearsal. Repeat the relevant steps after fixing it, and schedule the next exercise around changes to the application or infrastructure.
- 01
Inspect the important data
Check representative records and their relationships. Include older records as well as recent ones from before the snapshot.
- 02
Open the associated files
Check uploads and generated documents. Verify ownership and permissions as well as the presence of filenames.
- 03
Exercise the application
Run representative reads and writes in the isolated environment. Inspect queues or scheduled operations without triggering production side effects.
- 04
Record the full recovery time
Include obtaining credentials, preparing the environment, downloading, importing and validating. Keep the result and any missing steps in the runbook.

A calmer place to start
Your next backup.
Your first recovery rehearsal.
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