Keep the recovery set together
Record the Firetower and CLI versions used for each backup. You need the database dump, its matching root key, deployment configuration, and any worker files you need to recover.
A database dump alone cannot decrypt credentials. The installer CLI has no restore command.
Prepare an isolated environment
- Keep the original backup unchanged. Work from a copy.
- Use an isolated server that cannot contact production workers.
- Preserve the source versions and configuration before planning upgrades.
- Include separately stored files and persistent volumes in the recovery plan.
Get help with the restore
Contact us with your versions, backup method and the error you are recovering from. Do not send root keys, passwords or database dumps through chat.
The exact import and volume-recovery steps depend on your deployment. Rehearse them in the isolated environment before replacing production.
Validate before reconnecting
- Sign in and confirm the expected people and resources.
- Confirm stored credentials can be decrypted.
- Reconnect one worker deliberately and run a small task.
- Check repository access and recovered files before reconnecting the rest of the fleet.
Start with Back up Firetower to prepare your recovery set.