# Curator Multiple Snapshots at paticular time?

**URL:** <https://discuss.elastic.co/t/curator-multiple-snapshots-at-paticular-time/89377>\
**Category:** Elasticsearch\
**Created:** [June 14, 2017, 12:52pm UTC](https://discuss.elastic.co/t/curator-multiple-snapshots-at-paticular-time/89377 "2017-06-14T12:52:50Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yaswanth](https://avatars.discourse-cdn.com/v4/letter/y/94ad74/32.png) [@Yaswanth](https://discuss.elastic.co/u/Yaswanth)\
**Post date:** [June 14, 2017, 12:52pm UTC](https://discuss.elastic.co/t/curator-multiple-snapshots-at-paticular-time/89377/1 "2017-06-14T12:52:50Z")

</div>

Hi Team,

My Usecase:

I have `6 VM's` in my azure account and i want to use Curator 4.2.6 to snapshot the indices and running `3 snapshot curator jobs` in each `VM` at particular time (10.00 PM) . I will run these curator jobs using a cron job. But in one documentation i had seen `Curator can't do 2 backups at the same time` .

Questions:

1. If i keep `wait_for_completion: True` Whether one snapshot will wait until the next is complete?  
2)How long a snapshot will wait for if `wait_for_completion: True` is there? What will be happen if it reach the timeout time ? Where all the snapshots which are in queue will be failed if the starting snapshot will reach its timeout time?

Thanks

---

<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 14, 2017, 1:15pm UTC](https://discuss.elastic.co/t/curator-multiple-snapshots-at-paticular-time/89377/2 "2017-06-14T13:15:05Z")

</div>

It's not Curator that can't do 2 backups at the same time, but Elasticsearch. If a snapshot is in progress, any other attempts to begin snapshots will fail.

`wait_for_completion` only counts for running snapshots. It will keep trying until either the snapshot completes. or the client times out, which is defined as `timeout` in the client configuration file, or `timeout_override` in the action file. It will not wait for a previous snapshot to finish and then begin its snapshot.

Rather than starting each job simultaneously, you would do better to have the snapshots run serially, so that one begins immediately after the others.

---

<div class="post-metadata">

**Author:** ![Yaswanth](https://avatars.discourse-cdn.com/v4/letter/y/94ad74/32.png) [@Yaswanth](https://discuss.elastic.co/u/Yaswanth)\
**Post date:** [June 14, 2017, 2:13pm UTC](https://discuss.elastic.co/t/curator-multiple-snapshots-at-paticular-time/89377/3 "2017-06-14T14:13:09Z")

</div>

Thanks @theuntergeek[quote="theuntergeek, post:2, topic:89377"]  
Rather than starting each job simultaneously, you would do better to have the snapshots run serially, so that one begins immediately after the others  
[/quote]

You want me to configure in cron job to run serially by giving 2 min interval between all the curator snapshots jobs OR Is there any flag in curator which will make all my curator jobs to run serially ?

THANKS

---

<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 14, 2017, 10:06pm UTC](https://discuss.elastic.co/t/curator-multiple-snapshots-at-paticular-time/89377/4 "2017-06-14T22:06:20Z")

</div>

Not a flag in Curator, but separate actions. The actions run serially:

```auto
---
actions:
  1:
    action: snapshot
    description: First snapshot
    options:
      ...
  2:
    action: snapshot
    description: Second snapshot
    options:
      ...
  3:
    action: snapshot
    description: Third snapshot
    options:
      ...

```

---

<div class="post-metadata">

**Author:** ![Yaswanth](https://avatars.discourse-cdn.com/v4/letter/y/94ad74/32.png) [@Yaswanth](https://discuss.elastic.co/u/Yaswanth)\
**Post date:** [June 15, 2017, 2:00am UTC](https://discuss.elastic.co/t/curator-multiple-snapshots-at-paticular-time/89377/5 "2017-06-15T02:00:43Z")

</div>

Thanks @theuntergeek

Is it a best practice to keep the `wait_for_completion: False` in all snapshot curator jobs which are running serially OR should i enable it? Because by default the flag will be `True` .

Thanks

---

<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 15, 2017, 2:15am UTC](https://discuss.elastic.co/t/curator-multiple-snapshots-at-paticular-time/89377/6 "2017-06-15T02:15:56Z")

</div>

You absolutely _must_ use `wait_for_completion: True` for _serial_ snapshot jobs, as Elasticsearch will not allow you to run more than one at a time. The others would detect the previous one running and immediately fail, otherwise.

---

<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 13, 2017, 2:15am UTC](https://discuss.elastic.co/t/curator-multiple-snapshots-at-paticular-time/89377/7 "2017-07-13T02:15:58Z")

</div>

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