# Snapshot in s3 bucket not seen by other cluster

**URL:** <https://discuss.elastic.co/t/snapshot-in-s3-bucket-not-seen-by-other-cluster/286006>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [October 6, 2021, 10:14am UTC](https://discuss.elastic.co/t/snapshot-in-s3-bucket-not-seen-by-other-cluster/286006 "2021-10-06T10:14:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![raphaelSeguin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raphaelseguin/32/93811_2.png) [@raphaelSeguin](https://discuss.elastic.co/u/raphaelSeguin)\
**Post date:** [October 6, 2021, 10:14am UTC](https://discuss.elastic.co/t/snapshot-in-s3-bucket-not-seen-by-other-cluster/286006/1 "2021-10-06T10:14:21Z")

</div>

Hi,  
I'm using an s3 repository to snapshot a cluster. I was hoping to restore the snapshot on a remote cluster by registering a repository pointing to the same bucket. But the snapshot I took from he first cluster remains invisible to the second one.  
Here are the comands I used:  
To take a snapshot from cluster 1:

```auto
curl -XPUT "localhost:9200/_snapshot/my_repo/full_2021.07.28_ok?wait_for_completion=true" 
-H 'Content-Type: application/json' 
-d '
{"indices": "my_index-*",
    "ignore_unavailable": true,
    "include_global_state": false
}'

```

Then i could verify its presence with:

```auto
curl localhost:9200/_snapshot/my_repo/my_snapshot

```

Then if I check the repo on cluster 2 (same request), I get:

```auto
{
  "snapshots": []
}

```

What am I missing here ?

---

<div class="post-metadata">

**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:** [October 6, 2021, 10:32am UTC](https://discuss.elastic.co/t/snapshot-in-s3-bucket-not-seen-by-other-cluster/286006/2 "2021-10-06T10:32:02Z")

</div>

A guess: you forgot to register the repository as read-only on cluster 2. Never register a repository as writeable from multiple clusters, it will lead to data loss. From [the docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-register-repository.html):

> If you register the same snapshot repository with multiple clusters, only one cluster should have write access to the repository. All other clusters connected to that repository should set the repository to `readonly` mode.

---

<div class="post-metadata">

**Author:** ![raphaelSeguin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raphaelseguin/32/93811_2.png) [@raphaelSeguin](https://discuss.elastic.co/u/raphaelSeguin)\
**Post date:** [October 6, 2021, 10:34am UTC](https://discuss.elastic.co/t/snapshot-in-s3-bucket-not-seen-by-other-cluster/286006/3 "2021-10-06T10:34:02Z")

</div>

I guess you're right. I'll check it out and keep you posted !

---

<div class="post-metadata">

**Author:** ![raphaelSeguin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raphaelseguin/32/93811_2.png) [@raphaelSeguin](https://discuss.elastic.co/u/raphaelSeguin)\
**Post date:** [October 8, 2021, 11:22am UTC](https://discuss.elastic.co/t/snapshot-in-s3-bucket-not-seen-by-other-cluster/286006/4 "2021-10-08T11:22:02Z")

</div>

That was the right answer.Thank you, it works fine, now.

---

<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 5, 2021, 11:22am UTC](https://discuss.elastic.co/t/snapshot-in-s3-bucket-not-seen-by-other-cluster/286006/5 "2021-11-05T11:22:04Z")

</div>

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