# Sanpshot by Type:URL

**URL:** <https://discuss.elastic.co/t/sanpshot-by-type-url/32334>\
**Category:** Elasticsearch\
**Created:** [October 16, 2015, 7:19am UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334 "2015-10-16T07:19:47Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![krish0608](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krish0608/32/6797_2.png) [@krish0608](https://discuss.elastic.co/u/krish0608)\
**Post date:** [October 16, 2015, 7:19am UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/1 "2015-10-16T07:19:47Z")

</div>

{"error":"UnsupportedOperationException[URL repository doesn't support this operation]","status":500}

While Taking Backup type:URL it is showing this error on selecting these option....  
ignore\_unavailable  
True False  
include\_global\_state  
True False  
So,thats why it is not creating backup..please help me out.

PUT /\_snapshot/my\_backup  
{  
"type": "url",  
"settings": {  
"compress" : true,  
"location": "[http://localhost/my\_backup/\*](http://localhost/my_backup/*)"  
}  
}

---

<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 16, 2015, 7:31am UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/2 "2015-10-16T07:31:33Z")

</div>

You can not write to a read only repo. Use a Shared FS.

---

<div class="post-metadata">

**Author:** ![krish0608](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krish0608/32/6797_2.png) [@krish0608](https://discuss.elastic.co/u/krish0608)\
**Post date:** [October 16, 2015, 7:32am UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/3 "2015-10-16T07:32:48Z")

</div>

how to create Shared FS.??can u help me?

---

<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 16, 2015, 7:34am UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/4 "2015-10-16T07:34:44Z")

</div>

Well. Read that [https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html)

---

<div class="post-metadata">

**Author:** ![terrasacer](https://avatars.discourse-cdn.com/v4/letter/t/ecd19e/32.png) [@terrasacer](https://discuss.elastic.co/u/terrasacer)\
**Post date:** [October 24, 2015, 2:07pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/5 "2015-10-24T14:07:37Z")

</div>

Hi,

I have a different problem in this regard.

I'm registering a repository in fs type.

```
PUT _snapshot/repofs
{
  "type": "fs",
  "settings": {
  "location": "/root/data"
  }
}

```

Then I create a snapshot.

```
PUT _snapshot/repofs/first
{
  "indices": "*",
  "ignore_unavailable": true
}

```

Then I create a repository in url type.

```
PUT _snapshot/repourl
{
  "type": "url",
  "settings": {
    "url": "http://mysitename.com/root/data/*"
  }
}

```

And finally, I get an FileNotFoundException when I run the following command:

```
GET /_snapshot/repourl/_all

```

> {  
> "error": "RepositoryException[[repourl] failed to list snapshots in repository]; nested: FileNotFoundException[[http://mysitename.com/root/data/index](http://mysitename.com/root/data/index)]; ",  
> "status": 500  
> }

Whats wrong?

---

<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 24, 2015, 3:05pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/6 "2015-10-24T15:05:44Z")

</div>

What happen if you run from your elasticsearch machine:

curl [http://mysitename.com/root/data/index](http://mysitename.com/root/data/index)

You need to run it as the same user who is running elasticsearch.

---

<div class="post-metadata">

**Author:** ![terrasacer](https://avatars.discourse-cdn.com/v4/letter/t/ecd19e/32.png) [@terrasacer](https://discuss.elastic.co/u/terrasacer)\
**Post date:** [October 24, 2015, 5:13pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/7 "2015-10-24T17:13:02Z")

</div>

> [@dadoonet](#):
>
> curl [http://mysitename.com/root/data/index](http://mysitename.com/root/data/index)

server returns a page that was created for the 404.

---

<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 24, 2015, 5:47pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/8 "2015-10-24T17:47:33Z")

</div>

And curl [http://mysitename.com/root/data/](http://mysitename.com/root/data/) ?

Are you sure this site has the data in this URL? Might be another one depending on how your web server has been set up?

---

<div class="post-metadata">

**Author:** ![terrasacer](https://avatars.discourse-cdn.com/v4/letter/t/ecd19e/32.png) [@terrasacer](https://discuss.elastic.co/u/terrasacer)\
**Post date:** [October 24, 2015, 5:51pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/9 "2015-10-24T17:51:37Z")

</div>

> [@dadoonet](#):
>
> Are you sure this site has the data in this URL? Might be another one depending on how your web server has been set up?

Yes, I am sure.

I do not understand the problem. We use nginx. Maybe this is the source of the problem.

---

<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 24, 2015, 6:35pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/10 "2015-10-24T18:35:02Z")

</div>

Do you have access to [http://mysitename.com/root/data/](http://mysitename.com/root/data/) ?

---

<div class="post-metadata">

**Author:** ![terrasacer](https://avatars.discourse-cdn.com/v4/letter/t/ecd19e/32.png) [@terrasacer](https://discuss.elastic.co/u/terrasacer)\
**Post date:** [October 24, 2015, 7:51pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/11 "2015-10-24T19:51:46Z")

</div>

> [@dadoonet](#):
>
> Do you have access to [http://mysitename.com/root/data/](http://mysitename.com/root/data/) ?

Of course,

I checked, the snapshot files are stored in this directory.

---

<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 24, 2015, 8:12pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/12 "2015-10-24T20:12:50Z")

</div>

I did not mean if you have access to the dir but to the url.

Can you ls your data dir?

```
ls -l /root/data
```

---

<div class="post-metadata">

**Author:** ![terrasacer](https://avatars.discourse-cdn.com/v4/letter/t/ecd19e/32.png) [@terrasacer](https://discuss.elastic.co/u/terrasacer)\
**Post date:** [October 24, 2015, 8:18pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/13 "2015-10-24T20:18:58Z")

</div>

> [@dadoonet](#):
>
> Can you ls your data dir?

Yes.

```
# ls -l /root/data
total 32
-rw-r--r-- 1 root root 32 Oct 24 13:56 index
drwxr-xr-x 4 root root 4096 Oct 24 13:51 indices
-rw-r--r-- 1 root root 4467 Oct 24 13:51 metadata-first
-rw-r--r-- 1 root root 4467 Oct 24 13:56 metadata-second
-rw-r--r-- 1 root root 217 Oct 24 13:51 snapshot-first
-rw-r--r-- 1 root root 218 Oct 24 13:56 snapshot-second

```

---

<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 24, 2015, 9:51pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/14 "2015-10-24T21:51:53Z")

</div>

So index file is here but your web server is giving you a 404, right?

And you still believe your configuration is correct?

I can't help on NGinx but I think you have something wrong there. BTW running all that as root is just a nonsense, security wise.

So, first fix your web server issues. When done, try to make it work with elasticsearch.

HTH

---

<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, 11:42pm UTC](https://discuss.elastic.co/t/sanpshot-by-type-url/32334/15 "2017-07-05T23:42:46Z")

</div>


