What to back up
- The database, which holds everything: events, alerts, cases, users, audit, settings.
- The environment file, which holds the deployment's secrets.
- The ingest CA private key and the agent update signing configuration.
- Collected files, if stored outside the database volume.
Backups
The deployment files include a backup script that takes a full backup of the database to the backups volume and keeps the newest seven. Schedule it with cron or a timer; nightly is the usual choice. Keep that volume on a different disk, or copy it off the host, so a failed disk does not take the backups with it.
Restore
The matching restore script rebuilds a deployment's data from a backup on a fresh host. Rehearse it. The runbook asks for a monthly restore drill onto a scratch host, and the hardening checklist expects it to have happened at least once before production traffic. A backup that has never been restored is a hope, not a backup.
Hosted tenants
FluenceSecurity performs and tests backups for hosted tenants. Customers can request an export at any time in the documented formats.