# ES Snapshot - RepositoryMissingException missing

**URL:** <https://discuss.elastic.co/t/es-snapshot-repositorymissingexception-missing/166510>\
**Category:** Elasticsearch\
**Created:** [January 31, 2019, 9:30am UTC](https://discuss.elastic.co/t/es-snapshot-repositorymissingexception-missing/166510 "2019-01-31T09:30:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![genseb](https://avatars.discourse-cdn.com/v4/letter/g/c4cdca/32.png) [@genseb](https://discuss.elastic.co/u/genseb)\
**Post date:** [January 31, 2019, 9:30am UTC](https://discuss.elastic.co/t/es-snapshot-repositorymissingexception-missing/166510/1 "2019-01-31T09:30:54Z")

</div>

Hi,

We are encountering strange behaviours with ElasticSearch snapshots.

Snapshots starts then following messages appear for some shards:

RepositoryMissingException[[\*\*\*\*\*] missing]

The repository exists because most shards are backup:

```
 "shards" : {
    "total" : 2816,
    "failed" : 744,
    "successful" : 2072

```

Here my architecture:

**Server1** == curl\_request ==\> **Cluster\_ES** ==\> **AWS\_S3**

Thanks for your help.

---

<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:** [February 28, 2019, 9:31am UTC](https://discuss.elastic.co/t/es-snapshot-repositorymissingexception-missing/166510/2 "2019-02-28T09:31:00Z")

</div>

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