# Retiring data to another Datacenter

**URL:** <https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652>\
**Category:** Elasticsearch\
**Created:** [August 23, 2016, 7:05am UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652 "2016-08-23T07:05:31Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![shaharmor](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@shaharmor](https://discuss.elastic.co/u/shaharmor)\
**Post date:** [August 23, 2016, 7:05am UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652/1 "2016-08-23T07:05:31Z")

</div>

Hi,

We are looking for a way to move old indices to a different datacenter, still using the same cluster.

All new data will go to specific "hot" nodes (using shard allocation awareness), and each day an old index will be moved to other "cold" nodes (Again, using shard allocation awareness).

No new data will be indexed in the cold data nodes.

I understand its possible to have split brain situations in this scenario, but i don't mind the cold nodes to be "detached" for some time from the cluster, as long as its not affecting indexing/searching in the "hot" nodes.

When the connection comes back between the cluster they should be able to fully restore the cluster health right?

Will that work?

Thanks

---

<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, 2016, 9:07am UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652/2 "2016-08-23T09:07:42Z")

</div>

> [@shaharmor](#):
>
> When the connection comes back between the cluster they should be able to fully restore the cluster health right?

You would probably need to restart one "half" of the cluster for this to happen.

> [@shaharmor](#):
>
> Will that work?

Sghort answer, no. Longer answer, don't even try.

---

<div class="post-metadata">

**Author:** ![shaharmor](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@shaharmor](https://discuss.elastic.co/u/shaharmor)\
**Post date:** [August 23, 2016, 10:58am UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652/3 "2016-08-23T10:58:23Z")

</div>

Thanks for the answer @warkolm.

What if we wanted to completely move our ES cluster to a different datacenter? What would be the best approach to do that?

---

<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, 2016, 10:59am UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652/4 "2016-08-23T10:59:42Z")

</div>

Snapshot and restore.  
You can reindex from one into the other too.

---

<div class="post-metadata">

**Author:** ![shaharmor](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@shaharmor](https://discuss.elastic.co/u/shaharmor)\
**Post date:** [August 23, 2016, 11:57am UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652/5 "2016-08-23T11:57:23Z")

</div>

And what about the live index? the one that constantly have new data being indexed into?

---

<div class="post-metadata">

**Author:** ![shaharmor](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@shaharmor](https://discuss.elastic.co/u/shaharmor)\
**Post date:** [August 23, 2016, 12:11pm UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652/6 "2016-08-23T12:11:29Z")

</div>

Also, what exactly is the reason that it won't work? Can't i use the multiple datacenter solution just during the transfer to the new DC?

I can set the new DC to use a new shard allocation tag, and then move indices one by one. Why would that won't work?

---

<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, 2016, 8:27pm UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652/7 "2016-08-23T20:27:41Z")

</div>

Check out [Scaling Elasticsearch Across Data Centers With Kafka | Elastic Blog](https://www.elastic.co/blog/scaling_elasticsearch_across_data_centers_with_kafka)

> [@shaharmor](#):
>
> Also, what exactly is the reason that it won't work?

Are you willing to restart half your cluster to get it to join back? Or to separate it?

---

<div class="post-metadata">

**Author:** ![shaharmor](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@shaharmor](https://discuss.elastic.co/u/shaharmor)\
**Post date:** [August 24, 2016, 8:32am UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652/8 "2016-08-24T08:32:23Z")

</div>

If its only for the duration of the migration of the data to another datacenter than yeah, i'm willing to restart it. (I believe its not going to fail every few seconds...)

---

<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 24, 2016, 8:57pm UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652/9 "2016-08-24T20:57:26Z")

</div>

> [@shaharmor](#):
>
> I believe its not going to fail every few seconds...

You hope, you mean 🙂

---

<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:** [July 5, 2017, 10:25pm UTC](https://discuss.elastic.co/t/retiring-data-to-another-datacenter/58652/10 "2017-07-05T22:25:24Z")

</div>


