# Store indices in separate locations **URL:** \ **Category:** Elasticsearch\ **Created:** [September 3, 2019, 6:15pm UTC](https://discuss.elastic.co/t/store-indices-in-separate-locations/197925 "2019-09-03T18:15:01Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![vini](https://avatars.discourse-cdn.com/v4/letter/v/c77e96/32.png) [@vini](https://discuss.elastic.co/u/vini)\ **Post date:** [September 3, 2019, 6:15pm UTC](https://discuss.elastic.co/t/store-indices-in-separate-locations/197925/1 "2019-09-03T18:15:01Z")
Hi all, I know this wasn’t possible with older version of elastic but in the recent version I haven’t been able to confirm yet. Can I define multiple locations to store indexes and define what index type is placed where? So that I can tell elastic to store my frozen indexes in a different place to my hot data? Thanks in advance, if there is any documentation I missed about this I am happy to be pointed back to it. ---
**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\ **Post date:** [September 3, 2019, 6:23pm UTC](https://discuss.elastic.co/t/store-indices-in-separate-locations/197925/2 "2019-09-03T18:23:45Z")
See the [Hot-Warm](https://www.elastic.co/blog/hot-warm-architecture) examples These use an attribute box\_type, but I think that field value is arbitrary. [This post](https://www.elastic.co/blog/implementing-hot-warm-cold-in-elasticsearch-with-index-lifecycle-management) uses different keywords with similar results. ---
**Author:** ![vini](https://avatars.discourse-cdn.com/v4/letter/v/c77e96/32.png) [@vini](https://discuss.elastic.co/u/vini)\ **Post date:** [September 4, 2019, 7:34pm UTC](https://discuss.elastic.co/t/store-indices-in-separate-locations/197925/3 "2019-09-04T19:34:06Z")
Thanks for the reply, I didn’t explain what I want properly in my original post. I want to have a node store different indexes in different directories. I don’t want to define this policy based on nodes but rather make the same node decide in which directory or drive to store a certain index. All my hosts have slow and fast drives and I am trying to leverage that the best possible way. Yes I could run multiple nodes per host but that would make things much more complex to run and more costly from a license point of view. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 4, 2019, 7:36pm UTC](https://discuss.elastic.co/t/store-indices-in-separate-locations/197925/4 "2019-09-04T19:36:00Z")
You can not make that differentiation within a single node so will need to use multiple nodes per host to allow that level of control. ---
**Author:** ![vini](https://avatars.discourse-cdn.com/v4/letter/v/c77e96/32.png) [@vini](https://discuss.elastic.co/u/vini)\ **Post date:** [September 4, 2019, 7:39pm UTC](https://discuss.elastic.co/t/store-indices-in-separate-locations/197925/5 "2019-09-04T19:39:50Z")
I am happy to work with a hack if that’s what it takes, any even remote option I could explore for that? When you setup multiple nodes per host, how do you do it? Do you use rpms (if you are on Linux) or do you use the binaries and setup two district software structures? I have been looking st this but there so so many ways I could do it, any tips? Thanks in advance! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 2, 2019, 7:39pm UTC](https://discuss.elastic.co/t/store-indices-in-separate-locations/197925/6 "2019-10-02T19:39:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.