Snapshot repository missing
No snapshot repository is properly configured, so the cluster cannot create or restore snapshots. Without backups, recovery after data loss or corruption is limited.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Cluster |
| Domains | snapshots-backup |
The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.
No usable snapshot repository is configured on the cluster. Snapshot and restore operations cannot run.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Add snapshot repository
Condition: Always shown for this insight.
Register a snapshot repository so you can back up indices. Use the action below and replace the placeholder repository name and path.
PUT _snapshot/your_backup
{
"type": "fs",
"settings": {
"location": "your_backup_location"
}
}
Requires the manage cluster privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
Elasticsearch backs up indices through the snapshot and restore APIs. Those APIs need a registered repository that every node can reach.
On self-managed clusters that use a shared filesystem repository, nodes typically need path.repo in elasticsearch.yml before you can register the repository. Other repository types (for example cloud object stores) have their own setup path.
Without a working repository, scheduled backups do not run and you cannot restore from snapshots after failure, accidental deletes, or corruption.