# SLM: Only one snapshot can be taken at a time. To avoid snapshot failures, edit or delete the policies

**URL:** <https://discuss.elastic.co/t/slm-only-one-snapshot-can-be-taken-at-a-time-to-avoid-snapshot-failures-edit-or-delete-the-policies/273500>\
**Category:** Elasticsearch\
**Created:** [May 20, 2021, 9:39am UTC](https://discuss.elastic.co/t/slm-only-one-snapshot-can-be-taken-at-a-time-to-avoid-snapshot-failures-edit-or-delete-the-policies/273500 "2021-05-20T09:39:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ewolfman](https://avatars.discourse-cdn.com/v4/letter/e/5f8ce5/32.png) [@ewolfman](https://discuss.elastic.co/u/ewolfman)\
**Post date:** [May 20, 2021, 9:39am UTC](https://discuss.elastic.co/t/slm-only-one-snapshot-can-be-taken-at-a-time-to-avoid-snapshot-failures-edit-or-delete-the-policies/273500/1 "2021-05-20T09:39:57Z")

</div>

Hi,

Does it mean that if you do schedule multiple snapshots on the same time they:

1. Will be queued, meaning that they might start later than scheduled but eventually they will execute and take a snapshot.

2. Or does it mean that some of the snapshots will not take place at all due to the conflicts? If this is the case, what happens if they are scheduled to a different time frame, but one of them takes time and is overlapping the other policy scheduling? will the later SLM policy be eventually executed or not?

Thanks.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [May 20, 2021, 9:47am UTC](https://discuss.elastic.co/t/slm-only-one-snapshot-can-be-taken-at-a-time-to-avoid-snapshot-failures-edit-or-delete-the-policies/273500/2 "2021-05-20T09:47:06Z")

</div>

Recent versions can take multiple snapshots at once so you'd be best off upgrading if this is causing you problems. IIRC in older versions there's no queue, the snapshots just fail.

---

<div class="post-metadata">

**Author:** ![ewolfman](https://avatars.discourse-cdn.com/v4/letter/e/5f8ce5/32.png) [@ewolfman](https://discuss.elastic.co/u/ewolfman)\
**Post date:** [May 20, 2021, 10:49am UTC](https://discuss.elastic.co/t/slm-only-one-snapshot-can-be-taken-at-a-time-to-avoid-snapshot-failures-edit-or-delete-the-policies/273500/3 "2021-05-20T10:49:48Z")

</div>

I am using 7.10.2 and still get this message in Kibana UI. Is it supposed to support multiple snapshots in that version?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [May 20, 2021, 1:59pm UTC](https://discuss.elastic.co/t/slm-only-one-snapshot-can-be-taken-at-a-time-to-avoid-snapshot-failures-edit-or-delete-the-policies/273500/4 "2021-05-20T13:59:06Z")

</div>

I can't speak about the Kibana UI you're using, but from Elasticsearch's perspective it should work fine to have overlapping SLM schedules in this version.

---

<div class="post-metadata">

**Author:** ![ewolfman](https://avatars.discourse-cdn.com/v4/letter/e/5f8ce5/32.png) [@ewolfman](https://discuss.elastic.co/u/ewolfman)\
**Post date:** [May 20, 2021, 4:02pm UTC](https://discuss.elastic.co/t/slm-only-one-snapshot-can-be-taken-at-a-time-to-avoid-snapshot-failures-edit-or-delete-the-policies/273500/5 "2021-05-20T16:02:29Z")

</div>

Kibana is also 7.10.2.  
I can say that I did note some lags in SLM when a heavy backup was taking place.

---

<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:** [June 17, 2021, 4:02pm UTC](https://discuss.elastic.co/t/slm-only-one-snapshot-can-be-taken-at-a-time-to-avoid-snapshot-failures-edit-or-delete-the-policies/273500/6 "2021-06-17T16:02:38Z")

</div>

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