# Choose where to store data

**URL:** <https://discuss.elastic.co/t/choose-where-to-store-data/53302>\
**Category:** Elasticsearch\
**Created:** [June 20, 2016, 10:33am UTC](https://discuss.elastic.co/t/choose-where-to-store-data/53302 "2016-06-20T10:33:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carlos\_Vega\_Moreno](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_vega_moreno/32/3773_2.png) [@Carlos\_Vega\_Moreno](https://discuss.elastic.co/u/Carlos_Vega_Moreno)\
**Post date:** [June 20, 2016, 10:33am UTC](https://discuss.elastic.co/t/choose-where-to-store-data/53302/1 "2016-06-20T10:33:25Z")

</div>

I would like to know if there is any way to move old indices to a different drive, like, for example a SAN drive. This way, the old data could be backed up in a different drive, maybe slower.

Greetings,

Carlos Vega

---

<div class="post-metadata">

**Author:** ![mainec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mainec/32/5557_2.png) [@mainec](https://discuss.elastic.co/u/mainec)\
**Post date:** [June 20, 2016, 11:06am UTC](https://discuss.elastic.co/t/choose-where-to-store-data/53302/2 "2016-06-20T11:06:32Z")

</div>

Unless you want to do that on a running cluster it should be as simple as moving the files over and telling ES about the new directory. See also:

[http://elasticsearch-users.115913.n3.nabble.com/moving-data-directory-td4030005.html](http://elasticsearch-users.115913.n3.nabble.com/moving-data-directory-td4030005.html)

For more documentation on how to configure data directories see also here:

[https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-dir-layout.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-dir-layout.html)

Hope this helps,  
Isabel

---

<div class="post-metadata">

**Author:** ![Carlos\_Vega\_Moreno](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_vega_moreno/32/3773_2.png) [@Carlos\_Vega\_Moreno](https://discuss.elastic.co/u/Carlos_Vega_Moreno)\
**Post date:** [June 20, 2016, 12:09pm UTC](https://discuss.elastic.co/t/choose-where-to-store-data/53302/3 "2016-06-20T12:09:20Z")

</div>

I want to do it on a running cluster, like, moving all indices older than 2 months, to a different path.

Greetings,

Carlos Vega

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [July 9, 2016, 2:41pm UTC](https://discuss.elastic.co/t/choose-where-to-store-data/53302/4 "2016-07-09T14:41:30Z")

</div>

I don't think you can move old documents/indexes to another path on the same node, but for separate nodes it's certainly possible. See [https://www.elastic.co/blog/hot-warm-architecture](https://www.elastic.co/blog/hot-warm-architecture).

---

<div class="post-metadata">

**Author:** ![Carlos\_Vega\_Moreno](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_vega_moreno/32/3773_2.png) [@Carlos\_Vega\_Moreno](https://discuss.elastic.co/u/Carlos_Vega_Moreno)\
**Post date:** [July 11, 2016, 7:02am UTC](https://discuss.elastic.co/t/choose-where-to-store-data/53302/5 "2016-07-11T07:02:22Z")

</div>

The resons behind this hipoteticall feature would be to move old data to a bigger, slower, storage system. I like that it is possible to use JBOD and RAID systems, but would be awesome to move old data to slower paths.

---

<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:36pm UTC](https://discuss.elastic.co/t/choose-where-to-store-data/53302/6 "2017-07-05T22:36:42Z")

</div>


