# Is path.repo needed to register a snapshot repository for "type" = "s3"? (elasticsearch 1.7.4)

**URL:** https://discuss.elastic.co/t/is-path-repo-needed-to-register-a-snapshot-repository-for-type-s3-elasticsearch-1-7-4/41932
**Category:** Elasticsearch
**Created:** [February 16, 2016, 7:59pm UTC](https://discuss.elastic.co/t/is-path-repo-needed-to-register-a-snapshot-repository-for-type-s3-elasticsearch-1-7-4/41932 "2016-02-16T19:59:47Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Vishal\_Singh1](https://avatars.discourse-cdn.com/v4/letter/v/439d5e/32.png) [@Vishal\_Singh1](https://discuss.elastic.co/u/Vishal_Singh1)
#### Post date: [February 16, 2016, 7:59pm UTC](https://discuss.elastic.co/t/is-path-repo-needed-to-register-a-snapshot-repository-for-type-s3-elasticsearch-1-7-4/41932/1 "2016-02-16T19:59:47Z")

</div>

I am getting this error

1. Error injecting constructor, org.elasticsearch.repositories.RepositoryException: [repository] location [backup] doesn't match any of the locations specified by path.repo because this setting is empty  
at org.elasticsearch.repositories.fs.FsRepository.(Unknown Source)  
while locating org.elasticsearch.repositories.fs.FsRepository  
while locating org.elasticsearch.repositories.Repository

1 error  
at org.elasticsearch.common.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:344)

I am really new at this. So, I apologize for newbie questions.

I am using "type": "s3" then why do I need to set path.repo entry?

Thank you for the help

---

<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: [February 18, 2016, 4:07pm UTC](https://discuss.elastic.co/t/is-path-repo-needed-to-register-a-snapshot-repository-for-type-s3-elasticsearch-1-7-4/41932/2 "2016-02-18T16:07:49Z")

</div>

Indeed. If you are using `"type": "s3"`, we should probably not check if `path.repo` has been defined.  
Might be a bug. Might have been fixed in 2.x though.

@Igor_Motov thoughts?

---

<div class="post-metadata">

### Author: ![Vishal\_Singh1](https://avatars.discourse-cdn.com/v4/letter/v/439d5e/32.png) [@Vishal\_Singh1](https://discuss.elastic.co/u/Vishal_Singh1)
#### Post date: [February 18, 2016, 4:28pm UTC](https://discuss.elastic.co/t/is-path-repo-needed-to-register-a-snapshot-repository-for-type-s3-elasticsearch-1-7-4/41932/3 "2016-02-18T16:28:35Z")

</div>

adding path.repo=["s3"] works for me. But it seems to be a work around to avoid ES throwing the error.

---

<div class="post-metadata">

### Author: ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)
#### Post date: [February 18, 2016, 6:38pm UTC](https://discuss.elastic.co/t/is-path-repo-needed-to-register-a-snapshot-repository-for-type-s3-elasticsearch-1-7-4/41932/4 "2016-02-18T18:38:48Z")

</div>

@Vishal_Singh1 is it possible that you had another FS repository registered?

---

<div class="post-metadata">

### Author: ![Vishal\_Singh1](https://avatars.discourse-cdn.com/v4/letter/v/439d5e/32.png) [@Vishal\_Singh1](https://discuss.elastic.co/u/Vishal_Singh1)
#### Post date: [February 18, 2016, 9:28pm UTC](https://discuss.elastic.co/t/is-path-repo-needed-to-register-a-snapshot-repository-for-type-s3-elasticsearch-1-7-4/41932/5 "2016-02-18T21:28:03Z")

</div>

Yes, I checked. I have 3 repository and one of them is FS repository. That will explain the problem 🙂  
I wish that the error is not thrown when I was trying to register S3. Thanks again for explaining it to me 🙂

---

<div class="post-metadata">

### Author: ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)
#### Post date: [February 18, 2016, 10:02pm UTC](https://discuss.elastic.co/t/is-path-repo-needed-to-register-a-snapshot-repository-for-type-s3-elasticsearch-1-7-4/41932/6 "2016-02-18T22:02:04Z")

</div>

@Vishal_Singh1 That looks like a bug. I thought we [fixed](https://github.com/elastic/elasticsearch/issues/10351) it in 1.5.1 though. If you can reproduce it, could you open an issue for it?

---

<div class="post-metadata">

### Author: ![geekpete](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geekpete/32/20409_2.png) [@geekpete](https://discuss.elastic.co/u/geekpete)
#### Post date: [May 18, 2016, 12:10am UTC](https://discuss.elastic.co/t/is-path-repo-needed-to-register-a-snapshot-repository-for-type-s3-elasticsearch-1-7-4/41932/7 "2016-05-18T00:10:20Z")

</div>

Hi Team,

I've just tried using both s3 and fs snapshot repos with and without the path.repo line in the elasticsearch config on v2.3.1 and got expected results.

The path.repo isn't required for creating an s3 snapshot repository in the version I tested.

I can test other versions out if people are still seeing issues with older versions so that we can confirm?

Thanks.

---

<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: [July 5, 2017, 10:50pm UTC](https://discuss.elastic.co/t/is-path-repo-needed-to-register-a-snapshot-repository-for-type-s3-elasticsearch-1-7-4/41932/8 "2017-07-05T22:50:51Z")

</div>


