Back up and restore your instance
Back up your database and deployment configuration together. The MySQL procedure provides the export and restore commands.
What to keep
- The database dump and its checksum.
.env, Compose files,start.sh, and supplied configuration directories.- The application, MySQL, and Redis image versions used by the deployment.
- Your offline license file, if configured.
When you use a SQL dump, exclude the live MySQL data directory from the configuration copy. Protect backups: they contain credentials, account data, and saved workspaces. Keep a copy on a separate host and verify that you can restore it.
Restore your instance
- Restore the deployment files and select the recorded image versions.
- Follow the database restore procedure.
- Verify sign-in and a saved workspace before restoring user access.
If you replace an air-gapped host, obtain license material for its fingerprint.
Choose a backup frequency that matches how much recent work your organization can lose. Create a backup before updates.