# Merge multiple Elasticsearch installations

**URL:** <https://discuss.elastic.co/t/merge-multiple-elasticsearch-installations/152206>\
**Category:** Elasticsearch\
**Created:** [October 12, 2018, 9:31am UTC](https://discuss.elastic.co/t/merge-multiple-elasticsearch-installations/152206 "2018-10-12T09:31:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gollrich](https://avatars.discourse-cdn.com/v4/letter/g/c2a13f/32.png) [@gollrich](https://discuss.elastic.co/u/gollrich)\
**Post date:** [October 12, 2018, 9:31am UTC](https://discuss.elastic.co/t/merge-multiple-elasticsearch-installations/152206/1 "2018-10-12T09:31:24Z")

</div>

Greetings!

we have the current problem that for security reasons we have to run elk on premise without connection to the internet.  
We now want to migrate the data of multiple installations to one "global" one .  
Also the idea would be to do this on regular bases but only with the delta of the data since the last migration.  
Is there a tool or concept for this kind of a problem ?

greetings  
Mike

---

<div class="post-metadata">

**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\
**Post date:** [October 14, 2018, 3:24am UTC](https://discuss.elastic.co/t/merge-multiple-elasticsearch-installations/152206/2 "2018-10-14T03:24:38Z")

</div>

Hi Mike,

If you are able to mount an NFS directory to these nodes (maybe you have an internal one that isn't internet accessible?) then you could snapshot the data to this, and then add it as a repository and restore it to the new cluster.

If the global cluster is within your firewalls, you could also have the nodes join the global cluster, and then use allocation filtering to exclude the nodes you want to decommission, which will cause ES to move the data off of them onto your new cluster.

---

<div class="post-metadata">

**Author:** ![gollrich](https://avatars.discourse-cdn.com/v4/letter/g/c2a13f/32.png) [@gollrich](https://discuss.elastic.co/u/gollrich)\
**Post date:** [October 15, 2018, 9:46am UTC](https://discuss.elastic.co/t/merge-multiple-elasticsearch-installations/152206/3 "2018-10-15T09:46:14Z")

</div>

Hi Lee,

thanks for the reply.  
Unfortunally there is no automated connection what so ever possible yet, we wanted to export the data and transfer it manual .  
So for that szeanario you don´t see a possibilty ?

greetings

---

<div class="post-metadata">

**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\
**Post date:** [October 24, 2018, 2:28am UTC](https://discuss.elastic.co/t/merge-multiple-elasticsearch-installations/152206/4 "2018-10-24T02:28:14Z")

</div>

You could also use an external harddrive? (Depending on the size of the data for each node)

Sorry, sounds difficult with no connection.

---

<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:** [November 21, 2018, 2:37am UTC](https://discuss.elastic.co/t/merge-multiple-elasticsearch-installations/152206/5 "2018-11-21T02:37:47Z")

</div>

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