# ILM and curator

**URL:** <https://discuss.elastic.co/t/ilm-and-curator/352706>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [February 7, 2024, 7:55am UTC](https://discuss.elastic.co/t/ilm-and-curator/352706 "2024-02-07T07:55:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Youssef\_Shehadeh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/youssef_shehadeh/32/130815_2.png) [@Youssef\_Shehadeh](https://discuss.elastic.co/u/Youssef_Shehadeh)\
**Post date:** [February 7, 2024, 7:55am UTC](https://discuss.elastic.co/t/ilm-and-curator/352706/1 "2024-02-07T07:55:03Z")

</div>

Hello All,

I have a few questions about snapshots and restoring snapshots. Please consider this scenario: if I have an elastic cluster deployed in a production environment and to reduce storage, I take snapshots for indices every week and store them in a backup server.

```
How does the restoring process occur?
Do I need to mount every backup directory and restore them manually?
Can a duplicate name issue appear during this process?
Can I use Curator to restore snapshots by aliases or by age filters?

```

Another part of the questions:

I created an ILM policy to move the data to the cold tier after a specific amount of time. Then I used Curator to move the indices from the cold tier to the frozen tier, but noticed that Curator only moved the indices that are not managed by the ILM policy. Is this correct?

My idea is that I want to move indices from the cold tier to the frozen tier, then take a snapshot of the indices in the frozen tier to a mounted directory, and then delete it using a Curator cron job. Is this possible?

---

<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 6, 2024, 7:55am UTC](https://discuss.elastic.co/t/ilm-and-curator/352706/2 "2024-03-06T07:55:10Z")

</div>

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