# Export/Transfer from multiple nodes to one single node **URL:** \ **Category:** Elasticsearch\ **Created:** [October 5, 2018, 7:49am UTC](https://discuss.elastic.co/t/export-transfer-from-multiple-nodes-to-one-single-node/151171 "2018-10-05T07:49:23Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![boeledi01](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@boeledi01](https://discuss.elastic.co/u/boeledi01)\ **Post date:** [October 5, 2018, 7:49am UTC](https://discuss.elastic.co/t/export-transfer-from-multiple-nodes-to-one-single-node/151171/1 "2018-10-05T07:49:23Z")
Hi, We are currently running ES 2.1 in production and experiencing issues once we need to sort documents. Our cluster is made of 3 nodes (heap: 15 GB). We have 3 indexes (5 shards). One of our indexes counts more than 310 000 000 documents, I would like to make a test to run ES 6.3 on another server (and ONLY ONE server). The problem is that I have only 1 server available (4 vCPU, 65 GB...) to run these tests. These tests are not intended to demonstrate any performance but this is more a feasibility test. The question: How could I do to get the content of ONE index and have it on ONE node? Many thanks for your help ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [October 5, 2018, 8:12am UTC](https://discuss.elastic.co/t/export-transfer-from-multiple-nodes-to-one-single-node/151171/2 "2018-10-05T08:12:28Z")
I think [reindex from remote](https://www.elastic.co/guide/en/elasticsearch/reference/6.3/docs-reindex.html#reindex-from-remote) is going to work for you here. Start up a 6.3 node and tell it to reindex the data that you want from your existing cluster. ---
**Author:** ![boeledi01](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@boeledi01](https://discuss.elastic.co/u/boeledi01)\ **Post date:** [October 5, 2018, 8:18am UTC](https://discuss.elastic.co/t/export-transfer-from-multiple-nodes-to-one-single-node/151171/3 "2018-10-05T08:18:35Z")
Thanks David. The only problem I have is that ES 2.1 is working in PROD (isolated domain), and my other server in DEV (secured). Both domain may no talk to each other. The only way is transfer data via file.... ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [October 5, 2018, 9:17am UTC](https://discuss.elastic.co/t/export-transfer-from-multiple-nodes-to-one-single-node/151171/4 "2018-10-05T09:17:38Z")
In which case you will need to use [snapshot and restore](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html) to snapshot your production data into somewhere that your development cluster can read it first. This is a bit tricky because you cannot restore a 2.1 snapshot directly into a 6.3 cluster since the versions are too different. I would start a 2.x node in your development environment, restore the snapshot into that, and then use reindex-from-remote to upgrade it from 2.x to 6.x. Although you only have one development machine available, it should be no problem to run a 2.x node and a 6.x node side-by-side. The main difficulty is to keep track of which one is which - I recommend setting `http.port` explicitly on each so you know which is listening on which port, and setting `path.data` on each so their data directories don't get entangled. You might also want to set `discovery.zen.ping.unicast.hosts: []` to stop them discovering each other and complaining about being incompatible. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 2, 2018, 9:22am UTC](https://discuss.elastic.co/t/export-transfer-from-multiple-nodes-to-one-single-node/151171/5 "2018-11-02T09:22:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.