# BackUp and restore

**URL:** <https://discuss.elastic.co/t/backup-and-restore/17365>\
**Category:** Elasticsearch\
**Created:** [May 6, 2014, 11:50am UTC](https://discuss.elastic.co/t/backup-and-restore/17365 "2014-05-06T11:50:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ankur\_Goel](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Ankur\_Goel](https://discuss.elastic.co/u/Ankur_Goel)\
**Post date:** [May 6, 2014, 11:50am UTC](https://discuss.elastic.co/t/backup-and-restore/17365/1 "2014-05-06T11:50:27Z")

</div>

Hi All,

We have been using an elastic search cluster with 3 nodes , running on aws  
machines , we have been using EBS for work and data directory of  
elasticsearch . I was experimenting with backup using EBS snapshots , here  
is what I did

1.) created a snapshot of one ebs volume (say, alpha)  
2.) deleted the index  
3.) shutdown the cluster  
4.) unmounted the ebs volume on alpha (say /mnt/data )  
5.) created a new volume from snapshot and mounted on alpha in the same  
location (/mnt/data)  
6.) restarted elastic search on one node only  
cluster went to red state , all shards in unassigned  
state  
7.) restarted another node with blank data (/mnt/data ) directory  
cluster went to yellow state , all shards STILL in  
UNASSIGNED STATE  
8.) manually allocated shards to node  
recovered no documents , few kbs of data got restored  
☹

can anyone please help me debug this , what am I doing wrong , is there a  
better way to do this ??

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/6381f2e3-706d-4bc8-86f5-283396e37560%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6381f2e3-706d-4bc8-86f5-283396e37560%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![andrew](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@andrew](https://discuss.elastic.co/u/andrew)\
**Post date:** [May 6, 2014, 4:48pm UTC](https://discuss.elastic.co/t/backup-and-restore/17365/2 "2014-05-06T16:48:26Z")

</div>

Hi,

The recommend way to do this is to use ES's built-in snapshot/restore feature [1]. You would probably want to store your backups in S3 rather than EBS.

Also note that EBS does not always provide an acceptable level of performance for low-latency queries. If you use EBS you most likely will want to use provisioned IOPS.

Andrew

1. [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-snapshots.html#_snapshot)

On May 6, 2014, at 4:50 AM, Ankur Goel [ankrugold@gmail.com](mailto:ankrugold@gmail.com) wrote:

> Hi All,
> 
> We have been using an Elasticsearch cluster with 3 nodes , running on aws machines , we have been using EBS for work and data directory of elasticsearch . I was experimenting with backup using EBS snapshots , here is what I did
> 
> 1.) created a snapshot of one ebs volume (say, alpha)  
> 2.) deleted the index  
> 3.) shutdown the cluster  
> 4.) unmounted the ebs volume on alpha (say /mnt/data )  
> 5.) created a new volume from snapshot and mounted on alpha in the same location (/mnt/data)  
> 6.) restarted Elasticsearch on one node only  
> cluster went to red state , all shards in unassigned state  
> 7.) restarted another node with blank data (/mnt/data ) directory  
> cluster went to yellow state , all shards STILL in UNASSIGNED STATE  
> 8.) manually allocated shards to node  
> recovered no documents , few kbs of data got restored ☹
> 
> can anyone please help me debug this , what am I doing wrong , is there a better way to do this ??
> 
> --  
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/6381f2e3-706d-4bc8-86f5-283396e37560%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6381f2e3-706d-4bc8-86f5-283396e37560%40googlegroups.com).  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1E2194BC-5D83-4117-8A26-14676D4E2A38%40elasticsearch.com](https://groups.google.com/d/msgid/elasticsearch/1E2194BC-5D83-4117-8A26-14676D4E2A38%40elasticsearch.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 1:31am UTC](https://discuss.elastic.co/t/backup-and-restore/17365/3 "2017-07-06T01:31:18Z")

</div>


