# Portability of Index on disk

**URL:** <https://discuss.elastic.co/t/portability-of-index-on-disk/139457>\
**Category:** Elasticsearch\
**Created:** [July 11, 2018, 3:30am UTC](https://discuss.elastic.co/t/portability-of-index-on-disk/139457 "2018-07-11T03:30:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nos\_0](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@nos\_0](https://discuss.elastic.co/u/nos_0)\
**Post date:** [July 11, 2018, 3:30am UTC](https://discuss.elastic.co/t/portability-of-index-on-disk/139457/1 "2018-07-11T03:30:23Z")

</div>

Hello, I am a new Elasticsearch user. I have been using wikipedia index dumps to run some queries more or less based on this tutorial - [https://www.elastic.co/blog/loading-wikipedia](https://www.elastic.co/blog/loading-wikipedia)

Things are working great! I am using a very simple single shard no replication instance. Which works perfectly fine for my purposes. Now I have managed to shrink the wiki indexes provided, from multiple GB to a few hundred MB that my queries require by playing around with the mappings settings. I want to share this index with others at work.

Goal being they can follow the exact same steps in the tutorial WITHOUT the zcat / bulk import step which takes about 3 hours to run. I figure if I have already created the appropriate index on disk just copying over the few hundred MB will make their setup time much much faster.

Is there some way to achieve this? Thanks in advance for any pointers!

---

<div class="post-metadata">

**Author:** ![gabriel\_tessier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gabriel_tessier/32/27911_2.png) [@gabriel\_tessier](https://discuss.elastic.co/u/gabriel_tessier)\
**Post date:** [July 11, 2018, 4:49am UTC](https://discuss.elastic.co/t/portability-of-index-on-disk/139457/2 "2018-07-11T04:49:19Z")

</div>

One suggestion that we use to share data on same local network is remote reindex.  
And with filtering by query, other co-worker can take only the data they need.

More about here:  
[https://www.elastic.co/guide/en/elasticsearch/reference/master/reindex-upgrade-remote.html](https://www.elastic.co/guide/en/elasticsearch/reference/master/reindex-upgrade-remote.html)

Hope it help.

---

<div class="post-metadata">

**Author:** ![mnozawa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mnozawa/32/15091_2.png) [@mnozawa](https://discuss.elastic.co/u/mnozawa)\
**Post date:** [July 11, 2018, 5:32am UTC](https://discuss.elastic.co/t/portability-of-index-on-disk/139457/3 "2018-07-11T05:32:29Z")

</div>

I think, snapshot is portable data and restorable by another cluster.

[https://www.elastic.co/guide/en/elasticsearch/reference/6.x/modules-snapshots.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.x/modules-snapshots.html)

---

<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:** [August 8, 2018, 5:32am UTC](https://discuss.elastic.co/t/portability-of-index-on-disk/139457/4 "2018-08-08T05:32:33Z")

</div>

Closed on August 8, 2018, 5:32am UTC

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