# Cluster uuid different after cluster migration

**URL:** <https://discuss.elastic.co/t/cluster-uuid-different-after-cluster-migration/312640>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [August 22, 2022, 3:47pm UTC](https://discuss.elastic.co/t/cluster-uuid-different-after-cluster-migration/312640 "2022-08-22T15:47:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas\_Boutelier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomas_boutelier/32/109938_2.png) [@Thomas\_Boutelier](https://discuss.elastic.co/u/Thomas_Boutelier)\
**Post date:** [August 22, 2022, 3:47pm UTC](https://discuss.elastic.co/t/cluster-uuid-different-after-cluster-migration/312640/1 "2022-08-22T15:47:24Z")

</div>

Hello everybody,

I performed a cluster migration; I've recreated a kubernetes cluster and reattached the existing elasticsearch ebs volumes (with all datas).

When I recreated the Elastic manifest, it generated a cluster uuid different than the old one. Everyting seems to be working great, no problems so far. But this is a staging cluster and I have to do the same operation on a production one.

Can a different cluster uuid can cause problems for futur operations ?

Thanks in advance

---

<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:** [August 23, 2022, 1:12am UTC](https://discuss.elastic.co/t/cluster-uuid-different-after-cluster-migration/312640/2 "2022-08-23T01:12:28Z")

</div>

Welcome to our community! 😃

What version of Elasticsearch are you running?

---

<div class="post-metadata">

**Author:** ![Thomas\_Boutelier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomas_boutelier/32/109938_2.png) [@Thomas\_Boutelier](https://discuss.elastic.co/u/Thomas_Boutelier)\
**Post date:** [August 23, 2022, 12:46pm UTC](https://discuss.elastic.co/t/cluster-uuid-different-after-cluster-migration/312640/3 "2022-08-23T12:46:07Z")

</div>

We use a version 7.10.1

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [August 24, 2022, 12:56pm UTC](https://discuss.elastic.co/t/cluster-uuid-different-after-cluster-migration/312640/4 "2022-08-24T12:56:44Z")

</div>

I would say if the cluster UUID has changed you in fact have created a new cluster and not transplanted your existing cluster (which as I understand it is your goal)

Did you first create the new cluster with the new manifest and then modified it to use the existing volumes? I think for a successful migration the volumes have to be there from the beginning to avoid the formation of a new cluster.

For this to work you have to make sure that PersistentVolumeClaims pointing to your existing volumes but with the right names for the new cluster exist before you create the Elasticsearch resources.

We have a tool here [cloud-on-k8s/README.md at 8870369140d2c14a92cb49f1e375b49d161eb761 · elastic/cloud-on-k8s · GitHub](https://github.com/elastic/cloud-on-k8s/blob/8870369140d2c14a92cb49f1e375b49d161eb761/support/reattach-pv/README.md) that is only meant for disaster recovery purposes (!) that might be helpful in illustrating the idea if you are familiar with Go.

---

<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 21, 2022, 12:57pm UTC](https://discuss.elastic.co/t/cluster-uuid-different-after-cluster-migration/312640/5 "2022-09-21T12:57:11Z")

</div>

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