# Archival strategy of indices

**URL:** <https://discuss.elastic.co/t/archival-strategy-of-indices/137085>\
**Category:** Elasticsearch\
**Created:** [June 22, 2018, 9:14pm UTC](https://discuss.elastic.co/t/archival-strategy-of-indices/137085 "2018-06-22T21:14:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gthang](https://avatars.discourse-cdn.com/v4/letter/g/258eb7/32.png) [@gthang](https://discuss.elastic.co/u/gthang)\
**Post date:** [June 22, 2018, 9:14pm UTC](https://discuss.elastic.co/t/archival-strategy-of-indices/137085/1 "2018-06-22T21:14:47Z")

</div>

Hello,

We have about 40 different indices being produced everyday. We currently have an alias setup for to point to the current business day index, and every night when the day rolls over, we create a new index and recreate the alias.

Ideally we would like to make the previous day's index read-only and move it to SAN. We would still be able to access it to run queries etc. I don't think the snapshot feature will allow us to query the index without restoring it.

Any thoughts/suggestions and best practises for what I am trying to achieve?

Thanks!  
G-Thang

---

<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:** [June 22, 2018, 9:16pm UTC](https://discuss.elastic.co/t/archival-strategy-of-indices/137085/2 "2018-06-22T21:16:36Z")

</div>

[Elasticsearch Curator](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html) is usually what we recommend here.

---

<div class="post-metadata">

**Author:** ![gthang](https://avatars.discourse-cdn.com/v4/letter/g/258eb7/32.png) [@gthang](https://discuss.elastic.co/u/gthang)\
**Post date:** [June 22, 2018, 9:22pm UTC](https://discuss.elastic.co/t/archival-strategy-of-indices/137085/3 "2018-06-22T21:22:59Z")

</div>

Thanks for that, but unfortunately I can't install the package in the production host(security drama). I will just have to use the existing REST calls :(.

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [June 22, 2018, 11:02pm UTC](https://discuss.elastic.co/t/archival-strategy-of-indices/137085/4 "2018-06-22T23:02:53Z")

</div>

Curator doesn't have to be installed in the cluster. It only needs client access, which supports all X-Pack Security/SSL options.

---

<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 20, 2018, 11:12pm UTC](https://discuss.elastic.co/t/archival-strategy-of-indices/137085/5 "2018-07-20T23:12:10Z")

</div>

Closed on July 20, 2018, 11:12pm UTC

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