Backups
Nomad Enterprise's state consists of the following components:
- Jobs
- Deployments
- Evaluations
- Allocations
- Nodes
- Variables
- Key Material to encrypt secrets such as Variables and to sign JWTs
Nomad Enterprise backs this information up when it generates a snapshot.
Note
The only exception is the keystore(opens in new tab), if using the local key store, back it up separately.
You can trigger snapshot creation manually or automatically with the snapshot agent(opens in new tab).
To support your company's RPO policy we recommend configuring Nomad snapshot agent to take periodic backups of the Nomad cluster state. Configure the snapshot agent to take backups at a specified interval and store them in S3 or other compatible remote storage, preferably with configured lifecycle policy. Configure the number of backups the snapshot agent retains(opens in new tab).
If using the snapshot agent for backups, Nomad Enterprise restores the cluster back to the time when the agent took the snapshot. To pull individual items from a backup, restore the snapshot to an isolated cluster and use the API to retrieve individual items. You can only restore snapshots to the same Nomad Enterprise version which took the backup.
Use the nomad operator snapshot restore command to restore a snapshot.