# Unable to take snapshot

**URL:** https://discuss.elastic.co/t/unable-to-take-snapshot/218088
**Category:** Elasticsearch
**Created:** [February 6, 2020, 5:31am UTC](https://discuss.elastic.co/t/unable-to-take-snapshot/218088 "2020-02-06T05:31:48Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Gayathri.Srivathsan](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@Gayathri.Srivathsan](https://discuss.elastic.co/u/Gayathri.Srivathsan)
#### Post date: [February 6, 2020, 5:31am UTC](https://discuss.elastic.co/t/unable-to-take-snapshot/218088/1 "2020-02-06T05:31:48Z")

</div>

Hi All,

I created a read only repository pointing my bitbucket repo.I tried to create snapshot but it gives the following error.

{  
"error": {  
"root\_cause": [  
{  
"type": "not\_x\_content\_exception",  
"reason": "Compressor detection can only be called on some xcontent bytes or compressed xcontent bytes"  
}  
],  
"type": "not\_x\_content\_exception",  
"reason": "Compressor detection can only be called on some xcontent bytes or compressed xcontent bytes"  
},  
"status": 500  
}

I dont know which mapping has gone wrong here.

---

<div class="post-metadata">

### Author: ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)
#### Post date: [February 6, 2020, 5:52am UTC](https://discuss.elastic.co/t/unable-to-take-snapshot/218088/2 "2020-02-06T05:52:26Z")

</div>

Hi @Gayathri.Srivathsan

what's your exact repository settings, i.e. how did you create the repository?

> [@Gayathri.Srivathsan](#):
>
> I created a read only repository pointing my bitbucket repo

What plugin did you use here? Bitbucket is a version control system, to my knowledge there is no repository plugin for it (and frankly I don't see how one would make sense).  
Also, a read-only repository will not allow you to take snapshots it only allows reading/restoring from it as the name suggests 🙂

---

<div class="post-metadata">

### Author: ![Gayathri.Srivathsan](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@Gayathri.Srivathsan](https://discuss.elastic.co/u/Gayathri.Srivathsan)
#### Post date: [February 6, 2020, 6:12am UTC](https://discuss.elastic.co/t/unable-to-take-snapshot/218088/3 "2020-02-06T06:12:51Z")

</div>

HI,  
I wanted to push my backup data directly to bitbucket. Is it possible in shared repository. Can I give the URL in path.repo

---

<div class="post-metadata">

### Author: ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)
#### Post date: [February 6, 2020, 6:16am UTC](https://discuss.elastic.co/t/unable-to-take-snapshot/218088/4 "2020-02-06T06:16:33Z")

</div>

@Gayathri.Srivathsan not that won't be possible. You need to provide a shared file system path that is seen by all your nodes for `path.repo` when using the `fs` repository, you can't run against arbitrary GIT/HTTP endpoints.  
A version control system is not suitable for storing the potentially large files generated by the Elasticsearch snapshot functionality to begin with. You can either snapshot to a shared file system, HDFS or one of our supported cloud storage backends as an alternative.

---

<div class="post-metadata">

### Author: ![Gayathri.Srivathsan](https://avatars.discourse-cdn.com/v4/letter/g/a5b964/32.png) [@Gayathri.Srivathsan](https://discuss.elastic.co/u/Gayathri.Srivathsan)
#### Post date: [February 6, 2020, 6:37am UTC](https://discuss.elastic.co/t/unable-to-take-snapshot/218088/5 "2020-02-06T06:37:58Z")

</div>

@Armin_Braun

Okay . Thanks for the info.

---

<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: [March 5, 2020, 6:38am UTC](https://discuss.elastic.co/t/unable-to-take-snapshot/218088/6 "2020-03-05T06:38:03Z")

</div>

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