# Repository-s3 plugin not synching snapshots

**URL:** <https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [September 26, 2022, 3:40am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117 "2022-09-26T03:40:15Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vishrant\_Gupta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishrant_gupta/32/103610_2.png) [@Vishrant\_Gupta](https://discuss.elastic.co/u/Vishrant_Gupta)\
**Post date:** [September 26, 2022, 3:40am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/1 "2022-09-26T03:40:15Z")

</div>

Hi there, I have two elasticsearch clusters running on two separate kubernetes clusters. Both the elasticsearch clusters have the `repository-s3` plugin installed.

```auto
    "2": {
        "name": "elasticsearch-client-575db98f7b-gd5gc",
        "component": "repository-s3",
        "version": "7.10.2"
    },
    "6": {
        "name": "elasticsearch-data-0",
        "component": "repository-s3",
        "version": "7.10.2"
    },
    "10": {
        "name": "elasticsearch-master-0",
        "component": "repository-s3",
        "version": "7.10.2"
    },

```

In one of the clusters, I am registering the `repository` in `readonly` mode, as follows:

```auto
PUT /_snapshot/backup_name_2_5k
{
  "type": "s3",
  "settings": {
      "base_path": "/backups/elasticsearch/backup_name_2_5k",
      "bucket": "backup",
      "region": "ap-south-1",
      "readonly": true
  }
}

```

And in another cluster in read-write mode as follows:

```auto
PUT /_snapshot/backup_name_2_5k
{
  "type": "s3",
  "settings": {
      "base_path": "/backups/elasticsearch/backup_name_2_5k",
      "bucket": "backup",
      "region": "ap-south-1"
  }
}

```

Both have the same repository name and the base path.

In the cluster where the repository is registered as read-write I am triggering the snapshot creation as follows:

```auto
PUT /_snapshot/backup_name_2_5k/backup_name_2_5k?wait_for_completion=true
{
    "indices": "vsa-*"
}

```

In the cluster **where I created the snapshot** , I see in the list the snapshot exists, and I confirmed in the s3 path the data has been written, but, in the cluster where I registered the repository as `readonly` the newly created snapshot is not showing up.

What could be the reason for this? I expect the snapshot to be listed in both the elasticsearch cluster as I use the same repository path with `readonly` flag in one of the clusters.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 26, 2022, 3:53am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/2 "2022-09-26T03:53:45Z")

</div>

Welcome to our community! 😃

Elasticsearch 7.10 is [EOL](https://www.elastic.co/support/eol) and no longer supported, you need to upgrade.

> [@Vishrant\_Gupta](#):
>
> in the cluster where I registered the repository as `readonly` the newly created snapshot is not showing up

What is the output from `GET _snapshot`?

---

<div class="post-metadata">

**Author:** ![Vishrant\_Gupta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishrant_gupta/32/103610_2.png) [@Vishrant\_Gupta](https://discuss.elastic.co/u/Vishrant_Gupta)\
**Post date:** [September 26, 2022, 4:02am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/4 "2022-09-26T04:02:25Z")

</div>

@warkolm the output of `GET _snapshot` is:

```auto
{
    "backup_name_2_5k": {
        "type": "s3",
        "settings": {
            "bucket": "backup",
            "base_path": "/backups/elasticsearch/backup_name_2_5k",
            "readonly": "true",
            "region": "ap-south-1"
        }
    }
}

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 26, 2022, 4:03am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/6 "2022-09-26T04:03:32Z")

</div>

What about from the other cluster?

---

<div class="post-metadata">

**Author:** ![Vishrant\_Gupta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishrant_gupta/32/103610_2.png) [@Vishrant\_Gupta](https://discuss.elastic.co/u/Vishrant_Gupta)\
**Post date:** [September 26, 2022, 4:05am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/7 "2022-09-26T04:05:29Z")

</div>

For the other cluster it's

```auto
{
    "backup_name_2_5k": {
        "type": "s3",
        "settings": {
            "bucket": "backup",
            "region": "ap-south-1",
            "base_path": "/backups/elasticsearch/backup_name_2_5k"
        }
    }
}

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 26, 2022, 4:06am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/8 "2022-09-26T04:06:51Z")

</div>

Thanks, what about `GET _cat/snapshots?v` from both?

---

<div class="post-metadata">

**Author:** ![Vishrant\_Gupta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishrant_gupta/32/103610_2.png) [@Vishrant\_Gupta](https://discuss.elastic.co/u/Vishrant_Gupta)\
**Post date:** [September 26, 2022, 4:09am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/9 "2022-09-26T04:09:45Z")

</div>

Both the clusters responded with:

```auto
{
    "error": {
        "root_cause": [
            {
                "type": "action_request_validation_exception",
                "reason": "Validation Failed: 1: repository is missing;"
            }
        ],
        "type": "action_request_validation_exception",
        "reason": "Validation Failed: 1: repository is missing;"
    },
    "status": 400
}

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 26, 2022, 4:27am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/10 "2022-09-26T04:27:14Z")

</div>

Can you run the 2nd command in [Register a snapshot repository | Elasticsearch Guide [8.4] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.4/snapshots-register-repository.html#snapshots-repository-verification)?

---

<div class="post-metadata">

**Author:** ![Vishrant\_Gupta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishrant_gupta/32/103610_2.png) [@Vishrant\_Gupta](https://discuss.elastic.co/u/Vishrant_Gupta)\
**Post date:** [September 26, 2022, 1:35pm UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/11 "2022-09-26T13:35:39Z")

</div>

Below is the output of `POST /_snapshot/backup_name_2_5k/_verify`

```auto
{
	"nodes": {
		"VSHLh5AxQX-8649VKaLi9w": {
			"name": "elasticsearch-data-0"
		},
		"xhBcoEP-RW6X2DSOhDtJXg": {
			"name": "elasticsearch-master-0"
		}
	}
}

```

After sending the above request, `GET _cat/snapshots?v` still returns the following:

```auto
{
    "error": {
        "root_cause": [
            {
                "type": "action_request_validation_exception",
                "reason": "Validation Failed: 1: repository is missing;"
            }
        ],
        "type": "action_request_validation_exception",
        "reason": "Validation Failed: 1: repository is missing;"
    },
    "status": 400
}

```

---

<div class="post-metadata">

**Author:** ![Vishrant\_Gupta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishrant_gupta/32/103610_2.png) [@Vishrant\_Gupta](https://discuss.elastic.co/u/Vishrant_Gupta)\
**Post date:** [October 11, 2022, 3:48am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/12 "2022-10-11T03:48:18Z")

</div>

@warkolm do you know that issue might be happening?

---

<div class="post-metadata">

**Author:** ![Vishrant\_Gupta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishrant_gupta/32/103610_2.png) [@Vishrant\_Gupta](https://discuss.elastic.co/u/Vishrant_Gupta)\
**Post date:** [October 19, 2022, 10:11pm UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/13 "2022-10-19T22:11:40Z")

</div>

can anyone from [@elastic\_team](https://discuss.elastic.co/groups/elastic_team) help here to understand what the issue could be?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 20, 2022, 6:57am UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/14 "2022-10-20T06:57:33Z")

</div>

Could you run:

```
GET /

```

On both clusters please?

---

<div class="post-metadata">

**Author:** ![Vishrant\_Gupta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishrant_gupta/32/103610_2.png) [@Vishrant\_Gupta](https://discuss.elastic.co/u/Vishrant_Gupta)\
**Post date:** [October 20, 2022, 4:54pm UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/15 "2022-10-20T16:54:55Z")

</div>

I figured it out. For others, the issue was how you configure your repository, the base\_path should not start with `/` (root path)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 17, 2022, 4:55pm UTC](https://discuss.elastic.co/t/repository-s3-plugin-not-synching-snapshots/315117/16 "2022-11-17T16:55:37Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.