# Migrating from Hot to Hot-Cold Elastic Cluster using Snapshot and Restore

**URL:** <https://discuss.elastic.co/t/migrating-from-hot-to-hot-cold-elastic-cluster-using-snapshot-and-restore/332886>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management, snapshot-and-restore\
**Created:** [May 9, 2023, 7:47am UTC](https://discuss.elastic.co/t/migrating-from-hot-to-hot-cold-elastic-cluster-using-snapshot-and-restore/332886 "2023-05-09T07:47:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![yago82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yago82/32/97755_2.png) [@yago82](https://discuss.elastic.co/u/yago82)\
**Post date:** [May 9, 2023, 7:47am UTC](https://discuss.elastic.co/t/migrating-from-hot-to-hot-cold-elastic-cluster-using-snapshot-and-restore/332886/1 "2023-05-09T07:47:09Z")

</div>

Hi Elastic Community,  
We're considering migrating from a Elastic cluster (with only Hot nodes) to a hot-cold cluster to optimize performance and reduce hardware costs. Our question is, how will the cluster behave when we migrate from a hot to a hot-cold configuration using Snapshot and Restore?

If the migration is executed correctly, Elastic will take a complete snapshot of the data in the Hot cluster, including index data and settings. This snapshot can then be restored in the new Hot-Cold cluster, with hot and cold nodes already configured.

What do you think about it?

Thanks for your support

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 11, 2023, 12:56am UTC](https://discuss.elastic.co/t/migrating-from-hot-to-hot-cold-elastic-cluster-using-snapshot-and-restore/332886/2 "2023-05-11T00:56:54Z")

</div>

Are you using our Elasticsearch Service here?

---

<div class="post-metadata">

**Author:** ![yago82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yago82/32/97755_2.png) [@yago82](https://discuss.elastic.co/u/yago82)\
**Post date:** [May 11, 2023, 2:32pm UTC](https://discuss.elastic.co/t/migrating-from-hot-to-hot-cold-elastic-cluster-using-snapshot-and-restore/332886/3 "2023-05-11T14:32:01Z")

</div>

> [@warkolm](#):
>
> Are you using our Elasticsearch Service here?

I may have misunderstood the question, but if it's referring to the type of deployment, we currently have an Elasticsearch cluster on Kubernetes deployed with Helm Chart. We are in the process of migrating to an Elasticsearch cluster on Kubernetes using ECK as the operator.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 14, 2023, 11:40pm UTC](https://discuss.elastic.co/t/migrating-from-hot-to-hot-cold-elastic-cluster-using-snapshot-and-restore/332886/4 "2023-05-14T23:40:47Z")

</div>

Ok that's fine, I wanted to understand your deployment model!

> [@yago82](#):
>
> If the migration is executed correctly, Elastic will take a complete snapshot of the data in the Hot cluster, including index data and settings. This snapshot can then be restored in the new Hot-Cold cluster, with hot and cold nodes already configured.

As long as your node tagging (for the tiers) is consistent between clusters, yes.

---

<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:** [June 11, 2023, 11:41pm UTC](https://discuss.elastic.co/t/migrating-from-hot-to-hot-cold-elastic-cluster-using-snapshot-and-restore/332886/5 "2023-06-11T23:41:02Z")

</div>

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