# \[7.5.0\] Snapshot linked to ILM

**URL:** <https://discuss.elastic.co/t/7-5-0-snapshot-linked-to-ilm/211773>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [December 13, 2019, 9:45am UTC](https://discuss.elastic.co/t/7-5-0-snapshot-linked-to-ilm/211773 "2019-12-13T09:45:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fabio-sama](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@Fabio-sama](https://discuss.elastic.co/u/Fabio-sama)\
**Post date:** [December 13, 2019, 9:45am UTC](https://discuss.elastic.co/t/7-5-0-snapshot-linked-to-ilm/211773/1 "2019-12-13T09:45:02Z")

</div>

Hi there!

I've already set some index lifecycle policies and they work like a charm.

Now, having the possibility to handle the snapshots through the SLM, I'd like to take them one step further.

Unfortunately, it appears to me they (ILM and SLM) are not really linked.

What I would like to do is to set an ILP and, at the time of rollover, take a snapshot of the soon-to-be-old index and immediately delete it.

I mean, given an index alias `my_index`, at the moment I'm ingesting data into the indices `my_index-000000x` and the `x` is changed every 50Gb.  
What I'd like to do is, as soon as the index `my_index-0000001` has reached 50Gb, start ingesting data into `my_index-0000002`, take a snapshot of index `my_index-0000001` and delete index `my_index-0000001` right after it.

It's kinda strange they developed such powerful tools and then left them not linked.

Any ideas?

Thank you!

---

<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:** [January 10, 2020, 9:45am UTC](https://discuss.elastic.co/t/7-5-0-snapshot-linked-to-ilm/211773/2 "2020-01-10T09:45:03Z")

</div>

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