# Help with data recovery!

**URL:** <https://discuss.elastic.co/t/help-with-data-recovery/19306>\
**Category:** Elasticsearch\
**Created:** [August 15, 2014, 4:24pm UTC](https://discuss.elastic.co/t/help-with-data-recovery/19306 "2014-08-15T16:24:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard\_Wolford](https://avatars.discourse-cdn.com/v4/letter/r/ba8739/32.png) [@Richard\_Wolford](https://discuss.elastic.co/u/Richard_Wolford)\
**Post date:** [August 15, 2014, 4:24pm UTC](https://discuss.elastic.co/t/help-with-data-recovery/19306/1 "2014-08-15T16:24:31Z")

</div>

We had an Elasticsearch server that was reading IIS log files and storing  
the data on a remote file share. Everything was working just fine. The  
Elasticsearch server then encountered a problem, so we spun up a new one  
and pointed it to the same remote file share. However, the new  
Elasticsearch server, even though the configuration is 100% identical to  
the server that had a problem (and was shut down), it cannot see any of the  
data that was previously collected. Kibana is showing "all shards  
failed." How do we get this new Elasticsearch server to use the data that  
was generated by the old Elasticsearch server (this server cannot be  
brought back online btw).

Thanks!

--  
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/0efd41ee-0390-4b1b-bfd7-da93bccc646a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0efd41ee-0390-4b1b-bfd7-da93bccc646a%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![James\_4](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@James\_4](https://discuss.elastic.co/u/James_4)\
**Post date:** [August 15, 2014, 9:41pm UTC](https://discuss.elastic.co/t/help-with-data-recovery/19306/2 "2014-08-15T21:41:55Z")

</div>

How are you running ES? Installed package? I would copy the data from  
/var/lib/elasticsearch to the new server.

On Friday, August 15, 2014 10:24:31 AM UTC-6, Richard Wolford wrote:

> We had an Elasticsearch server that was reading IIS log files and storing  
> the data on a remote file share. Everything was working just fine. The  
> Elasticsearch server then encountered a problem, so we spun up a new one  
> and pointed it to the same remote file share. However, the new  
> Elasticsearch server, even though the configuration is 100% identical to  
> the server that had a problem (and was shut down), it cannot see any of the  
> data that was previously collected. Kibana is showing "all shards  
> failed." How do we get this new Elasticsearch server to use the data that  
> was generated by the old Elasticsearch server (this server cannot be  
> brought back online btw).
> 
> Thanks!

--  
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/b2e8e94a-3748-4359-a893-ebafe02cf958%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b2e8e94a-3748-4359-a893-ebafe02cf958%40googlegroups.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:08am UTC](https://discuss.elastic.co/t/help-with-data-recovery/19306/3 "2017-07-06T01:08:12Z")

</div>


