# Data directory on remort serever

**URL:** <https://discuss.elastic.co/t/data-directory-on-remort-serever/264972>\
**Category:** Elasticsearch\
**Created:** [February 21, 2021, 4:17am UTC](https://discuss.elastic.co/t/data-directory-on-remort-serever/264972 "2021-02-21T04:17:16Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ankur\_Mahajan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankur_mahajan/32/45618_2.png) [@Ankur\_Mahajan](https://discuss.elastic.co/u/Ankur_Mahajan)\
**Post date:** [February 21, 2021, 4:17am UTC](https://discuss.elastic.co/t/data-directory-on-remort-serever/264972/1 "2021-02-21T04:17:16Z")

</div>

Is there any possibility where I can put the **data directory** to a remort cloud instance?

**Cloud instance 1**  
**Public IP:** 1:11:11:111 (Dummy)  
**Elasticsearch data directory path:** /home/elasticsearch/data

**Cloud instance 2**  
Elasticsearch 5.6.16 running with below configurations.  
**data.path:** 1:11:11:111/home/elasticsearch/data (SFTP or FTP path)

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 21, 2021, 8:26am UTC](https://discuss.elastic.co/t/data-directory-on-remort-serever/264972/2 "2021-02-21T08:26:15Z")

</div>

Why do you want to do such a thing instead of running on fast local disks?

---

<div class="post-metadata">

**Author:** ![Ankur\_Mahajan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankur_mahajan/32/45618_2.png) [@Ankur\_Mahajan](https://discuss.elastic.co/u/Ankur_Mahajan)\
**Post date:** [February 21, 2021, 1:30pm UTC](https://discuss.elastic.co/t/data-directory-on-remort-serever/264972/3 "2021-02-21T13:30:04Z")

</div>

I am actually exploring this. Is it possible by any chance?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 21, 2021, 6:43pm UTC](https://discuss.elastic.co/t/data-directory-on-remort-serever/264972/4 "2021-02-21T18:43:31Z")

</div>

Have a look at:

> [@Why NFS is to be avoided for data directories](https://discuss.elastic.co/t/why-nfs-is-to-be-avoided-for-data-directories/215240):
>
> ES: 7.5 I have seen the recommendations in official documentation to 'avoid NFS' when using them as data directories for elasticsearch. I have also seen almost everywhere in the forums to 'avoid NFS' but couldn't find a proper explanation. Is it due to the fact that NFS is exported as a file system, and not a block device? Since there would be higher number of concurrent writes and reads, NFS would have protocol level bottlenecks. Is it due to network latency related issues of any network…

---

<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:** [February 21, 2021, 9:18pm UTC](https://discuss.elastic.co/t/data-directory-on-remort-serever/264972/5 "2021-02-21T21:18:53Z")

</div>

TDLR, no you don't want to do this.

---

<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:** [March 21, 2021, 9:19pm UTC](https://discuss.elastic.co/t/data-directory-on-remort-serever/264972/6 "2021-03-21T21:19:35Z")

</div>

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