# Snapshot Recovery on a Separate ECE Setup

**URL:** <https://discuss.elastic.co/t/snapshot-recovery-on-a-separate-ece-setup/199353>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [September 13, 2019, 3:39am UTC](https://discuss.elastic.co/t/snapshot-recovery-on-a-separate-ece-setup/199353 "2019-09-13T03:39:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ong](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ong/32/40766_2.png) [@Ong](https://discuss.elastic.co/u/Ong)\
**Post date:** [September 13, 2019, 3:39am UTC](https://discuss.elastic.co/t/snapshot-recovery-on-a-separate-ece-setup/199353/1 "2019-09-13T03:39:14Z")

</div>

I have an ECE 2.3 setup which has gone down due to a damaged zookeeper. Because of this, I set up a new ECE and created a couple of new ES cluster deployments on the new ECE, also on version 2.3.

How do I restore data from the previous deployments to the new ES clusters on the new ECE?

On the Snapshot recovery UI, I am only able to select from deployments created on the new ECE and not from the previous one. The snapshots are stored on Minio.

---

<div class="post-metadata">

**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\
**Post date:** [September 13, 2019, 1:23pm UTC](https://discuss.elastic.co/t/snapshot-recovery-on-a-separate-ece-setup/199353/2 "2019-09-13T13:23:00Z")

</div>

Our support isn't ideal here - in order to clone the cluster from the snapshots you would have to use the [API](https://www.elastic.co/guide/en/cloud-enterprise/current/Clusters_-_Elasticsearch_-_CRUD.html#create-es-cluster), and bring up the cluster with 2 key fields under [transient](https://www.elastic.co/guide/en/cloud-enterprise/current/definitions.html#TransientElasticsearchPlanConfiguration) - `plan_configuration.extended_maintenance` to `true` (to avoid eg Kibana adding indices during the restore process) and [`restore_snapshot`](https://www.elastic.co/guide/en/cloud-enterprise/current/definitions.html#RestoreSnapshotConfiguration) - the reference docs describe the format, but basically `repository_config.raw_settings` and `restore_payload.raw_settings` give you direct access to the ES API for repo creation and restore respectively.

Alternatively you can bring up the cluster from the UI, disable routing on all nodes, close all indices and then use the console API to perform the same steps manually

---

<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:** [September 27, 2019, 1:23pm UTC](https://discuss.elastic.co/t/snapshot-recovery-on-a-separate-ece-setup/199353/3 "2019-09-27T13:23:01Z")

</div>

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