# Elasticsearch Disaster Recovery from Snapshots

**URL:** <https://discuss.elastic.co/t/elasticsearch-disaster-recovery-from-snapshots/168469>\
**Category:** Elasticsearch\
**Created:** [February 14, 2019, 6:39pm UTC](https://discuss.elastic.co/t/elasticsearch-disaster-recovery-from-snapshots/168469 "2019-02-14T18:39:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Darnell\_Martin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darnell_martin/32/59411_2.png) [@Darnell\_Martin](https://discuss.elastic.co/u/Darnell_Martin)\
**Post date:** [February 14, 2019, 6:39pm UTC](https://discuss.elastic.co/t/elasticsearch-disaster-recovery-from-snapshots/168469/1 "2019-02-14T18:39:54Z")

</div>

Hey All,

I am working on a Disaster Recovery Process for our 3 Node Elasticsearch cluster. The Warm Node in the cluster is using Curator to Snapshot all Indexes on the cluster to an S3 Snapshot Repository every hour. During a Disaster Recovery process we are deleting the 3 nodes and creating 3 new ones and then restoring all of the indexes including the .system ones, however I am coming across errors with the ".triggered\_watches", ".watcher-history-_", ".security\_audit\_log-_", ".monitoring-\*" and many other indexes failing to have their shards assigned. I have tried using the cluster reroute API to assign them manually but they won't assign. We are on Elasticsearch Version 6.2.3 any suggestions?

---

<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 14, 2019, 6:39pm UTC](https://discuss.elastic.co/t/elasticsearch-disaster-recovery-from-snapshots/168469/2 "2019-03-14T18:39:59Z")

</div>

Closed on March 14, 2019, 6:39pm UTC

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