# I am encountering an issue while attempting to verify a snapshot repository in Elasticsearch. The repository is named old-indices. Below is the relevant log entry from the Elasticsearch cluster: **URL:** \ **Category:** Elasticsearch\ **Tags:** snapshot-and-restore\ **Created:** [December 31, 2024, 12:08pm UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658 "2024-12-31T12:08:16Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![abdelkriem](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@abdelkriem](https://discuss.elastic.co/u/abdelkriem)\ **Post date:** [December 31, 2024, 12:08pm UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658/1 "2024-12-31T12:08:16Z")
[2024-12-31T17:06:04,282] [WARN] [r.suppressed] [Elastic-Master-1] path: /\_snapshot/old-indices/\_verify, params: {repository=old-indices}, status: 500org.elasticsearch.repositories.RepositoryVerificationException: [old-indices] [[4Se7RLnxSSy1\_7Ngi4XisA, 'org.elasticsearch.transport.RemoteTransportexception: [node-1][10.10.24.153:9300] [internal:admin/repository/verify] ']] ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/8/383f4cf6aaa8837c9d12c5df156ea8e26415adf4.png) ---
**Author:** ![abdelkriem](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@abdelkriem](https://discuss.elastic.co/u/abdelkriem)\ **Post date:** [December 31, 2024, 12:20pm UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658/2 "2024-12-31T12:20:08Z")
![image](https://us1.discourse-cdn.com/elastic/optimized/3X/5/7/571eec9dfbcdca7e4cedc00db8ace53f3051beca_2_690x34.png) ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 31, 2024, 12:39pm UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658/3 "2024-12-31T12:39:16Z")
Hi @abdelkriem and welcome! Please don't post images of text, just post the text itself. I can barely read the message you've shared, but it looks like it's this one right? > If so, that's exactly the problem. ---
**Author:** ![abdelkriem](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@abdelkriem](https://discuss.elastic.co/u/abdelkriem)\ **Post date:** [December 31, 2024, 12:52pm UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658/4 "2024-12-31T12:52:58Z")
Thanks for your response, yes this is the problem: [2024-12-31T17:09:26,113] [WARN][o.e.r.V.TransportAction] [node-1] [old-indices] failed to verify repository org.elasticsearch.repositories.RepositoryVerificationException: [old-indices] a file written by master to the store [/home//snapshot/old-indices] cannot be accessed on the node [{node-1}{4Se7RLnxSSy1\_7Ngi4XisA {vSipvIAIQHSUFpA68jW6UQ} {node-1}{! :9300}{cdfhilmrstw}{8.15.0}{7000099-8512000} {ml.machine\_memory=16429281280, ml.allocated\_processors=8, ml.allocated\_processors\_double=8.0, ml.max\_jvm\_size=8216641536 ml.config\_version=12.0.0, xpack.installed=true, transform.config\_version=10.0.0}]. This might indicate that the store [/home//snapshot/old-indices] is not shared between this node and the master node or that permissions on the store don't allow reading files written by the master node ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [December 31, 2024, 1:55pm UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658/5 "2024-12-31T13:55:13Z")
All master and data nodes need to have read and write access to the same shared repository. Mounting separate volumes in the same place per node will not work as Elasticsearch will verify the repository by having one node write a file and another one read the same. ---
**Author:** ![abdelkriem](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@abdelkriem](https://discuss.elastic.co/u/abdelkriem)\ **Post date:** [January 5, 2025, 8:34am UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658/6 "2025-01-05T08:34:24Z")
This implies that the shared repository can only be mounted on a single node at a time. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 5, 2025, 8:40am UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658/7 "2025-01-05T08:40:06Z")
> [@abdelkriem](#): > > This implies that the shared repository can only be mounted on a single node at a time. No, it does not. Why would that be the case? ---
**Author:** ![abdelkriem](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@abdelkriem](https://discuss.elastic.co/u/abdelkriem)\ **Post date:** [January 6, 2025, 8:42am UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658/8 "2025-01-06T08:42:01Z")
I have built a three-node cluster, with all roles assigned to each of these nodes. I am now looking to take a snapshot of the indices. Based on the official documentation, my understanding is that I need to create a folder on **all three nodes** and set the `path.repo` parameter in the `elasticsearch.yml` file to ensure it is consistent across all nodes. However, I recently came across guidance suggesting that the folder only needs to be created on **one of the nodes**. Could you please clarify which approach is correct? Specifically: 1. Should the snapshot repository folder be created on all nodes in the cluster, or is it sufficient to create it on just one node? 2. If it is required on all nodes, does the folder path need to be identical across them? Your clarification on this matter will be greatly appreciated. Thank you in advance for your support! ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 6, 2025, 8:45am UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658/9 "2025-01-06T08:45:23Z")
> [@abdelkriem](#): > > I have built a three-node cluster, with all roles assigned to each of these nodes. I am now looking to take a snapshot of the indices. Based on the official documentation, my understanding is that I need to create a folder on **all three nodes** and set the `path.repo` parameter in the `elasticsearch.yml` file to ensure it is consistent across all nodes. > > However, I recently came across guidance suggesting that the folder only needs to be created on **one of the nodes**. Could you please clarify which approach is correct? Both of these are incorrect. You need to create a shared storage volume, e.g. NFS, and mount this on the same path on all master and data nodes and all nodes need to be able to both read and write to this single shared volume. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [January 6, 2025, 2:12pm UTC](https://discuss.elastic.co/t/i-am-encountering-an-issue-while-attempting-to-verify-a-snapshot-repository-in-elasticsearch-the-repository-is-named-old-indices-below-is-the-relevant-log-entry-from-the-elasticsearch-cluster/372658/10 "2025-01-06T14:12:07Z")
> [@abdelkriem](#): > > Based on the official documentation, my understanding is that I need to create a folder on **all three nodes** and set the `path.repo` parameter in the `elasticsearch.yml` file to ensure it is consistent across all nodes. Which documentation you followed? The [register a snapshot repository](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-register-repository.html#self-managed-repo-types) page describe the types of repositories you can have. It clearly mention _shared file system_ for file based repositories on local clusters, and the [shared file system](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-filesystem-repository.html) page also states that you need to use a shared file system. > Use a shared file system repository to store snapshots on a shared file system.