---
title: Repository Snapshot
description: Describes what AutoOps detects and surfaces with the Repository Snapshot insight: Snapshot and restore operations cannot be performed because no snapshot repository is properly configured on the cluster.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/repository_snapshot
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# Repository Snapshot
Snapshot and restore operations cannot be performed because no snapshot repository is properly configured on the cluster. repo on nodes and a registered repository, scheduled backups will not run and recovery options are limited.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


| Field     | Value            |
|-----------|------------------|
| Component | Elasticsearch    |
| Severity  | Medium           |
| Scope     | Cluster          |
| Domains   | snapshots-backup |


## Example: What you might see in AutoOps

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.

### Snapshot and restore operations cannot be performed on the cluster


#### What was detected

_No description available._

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="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.
  ```json

  {
    "type": "fs",
    "settings": {
      "location": "your_backup_location"
    }
  }
  ```

  <note>
    Requires the `manage cluster` privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
  </note>
</dropdown>


#### Background and impact

Impact: When these operations cannot be performed, there's a risk of data loss.
To backup indices you need to use the cluster snapshot mechanism. If no location is specified for a snapshot repository, no backup will be taken from a running cluster. To create and restore snapshots, you need to register a snapshot repository with every node in the cluster. To do this, you need to configure the static setting path.repo in the yaml config file. After restarting all the nodes, you can register the repository with the following command: