# Restore snapshot to another DC server using elasticsearch-curator **URL:** \ **Category:** Elasticsearch\ **Created:** [February 27, 2017, 6:55am UTC](https://discuss.elastic.co/t/restore-snapshot-to-another-dc-server-using-elasticsearch-curator/76581 "2017-02-27T06:55:28Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Nitish\_Kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nitish_kumar/32/15870_2.png) [@Nitish\_Kumar](https://discuss.elastic.co/u/Nitish_Kumar)\ **Post date:** [February 27, 2017, 6:55am UTC](https://discuss.elastic.co/t/restore-snapshot-to-another-dc-server-using-elasticsearch-curator/76581/1 "2017-02-27T06:55:28Z")
I need to keep elasticsearch-data in sync within 3 server using elasticsearch-curator. All I want to update data on one server and others update themselves using snapshot and restore method. I was able to create snapshot using curator on first server but couldn't restore it on another. Snapshot While taking snapshot Host entry in curator.yml is like hosts: ["localhost"] on Server 1. I can easily restore it on Server 1 itself. But, the problem arise when I try to restore it on Server 2 Host entry in curator.yml is like hosts: ["localhost","Server 1 IP"] It generates error message: **2017-02-27 10:39:58,927 INFO Preparing Action ID: 1, "restore"** 2017-02-27 10:39:59,145 INFO Trying Action ID: 1, "restore": Restore all indices in the most recent curator-\* snapshot with state SUCCESS. Wait for the restore to complete before continuing. Do not skip the repository filesystem access check. Use the other options to define the index/shard settings for the restore. \*\* 17-02-27 10:39:59,399 INFO Restoring indices "['test\_sec']" from snapshot: curator-20170226143036 \*\* 17-02-27 10:39:59,409 ERROR Failed to complete action: restore. \: Exception encountered. Rerun with loglevel DEBUG and/or check Elasticsearch logs for more information. Exception: TransportError(500, u'snapshot\_restore\_exception', u'[all\_index:curator-20170226143036]snapshot does not exist') ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [February 27, 2017, 9:41pm UTC](https://discuss.elastic.co/t/restore-snapshot-to-another-dc-server-using-elasticsearch-curator/76581/2 "2017-02-27T21:41:17Z")
The same repository must exist on both clusters, with the same shared filesystem available to _all_ machines in both clusters. You must add the repository to both clusters, preferably with the exact same API call. Only then will snapshots taken on cluster A be visible and available for restore on cluster B ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 27, 2017, 9:41pm UTC](https://discuss.elastic.co/t/restore-snapshot-to-another-dc-server-using-elasticsearch-curator/76581/3 "2017-03-27T21:41:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.