# Elasticsearch Curator 4.2.6 clarifications?

**URL:** <https://discuss.elastic.co/t/elasticsearch-curator-4-2-6-clarifications/80628>\
**Category:** Elasticsearch\
**Created:** [March 30, 2017, 8:32am UTC](https://discuss.elastic.co/t/elasticsearch-curator-4-2-6-clarifications/80628 "2017-03-30T08:32:41Z")\
**Posts on this page:** 3\
**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:** [March 30, 2017, 8:32am UTC](https://discuss.elastic.co/t/elasticsearch-curator-4-2-6-clarifications/80628/1 "2017-03-30T08:32:41Z")

</div>

Hi,

1)In curator i can able to get date pattern as Name-2017-03-30 for a snapshot but i want like this `Name-2017-Mar-30` ? Is it possible?

1. I have a ES cluster consisting of 5 nodes . Each node has an VM (i.e for 5 nodes i have 5 VM's) . Do i need to install curator in all the VM's or Can i install in any one VM ? What happens if that curator installed VM goes down?

2. Do i need to run cron job for backup and restore using curator in any one VM(I.e node) or i have to run in all the VM'S(i.e nodes)? What happens if cron job running VM goes down?

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:** [March 30, 2017, 2:43pm UTC](https://discuss.elastic.co/t/elasticsearch-curator-4-2-6-clarifications/80628/2 "2017-03-30T14:43:02Z")

</div>

> [@Yaswanth](#):
>
> 1)In curator i can able to get date pattern as Name-2017-03-30 for a snapshot but i want like this Name-2017-Mar-30 ? Is it possible?

No, unless you want to do it manually. Curator provides no deterministic way to do that.

> [@Yaswanth](#):
>
> 1. I have a ES cluster consisting of 5 nodes . Each node has an VM (i.e for 5 nodes i have 5 VM's) . Do i need to install curator in all the VM's or Can i install in any one VM ? What happens if that curator installed VM goes down?

In cases like this, you can deploy Curator to each node and set [`master_only`] ([Configuration File | Curator Reference [8.0] | Elastic](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/configfile.html#master_only)) to `True` in your client configuration file. This flag tells Curator to only run the actions on the _elected_ master node, of which there will be only one (unless you've put yourself into a split-brain scenario). The elected master is the actual master node out of all of the _eligible_ master nodes. Curator will start on each of the nodes, but after having discovered that it is not on the elected master, will terminate without doing any actions.

> [@Yaswanth](#):
>
> 1. Do i need to run cron job for backup and restore using curator in any one VM(I.e node) or i have to run in all the VM'S(i.e nodes)? What happens if cron job running VM goes down?

Snapshot is performed by Elasticsearch at the cluster level. You do not need to run it on every node. As far as the "what if cron" goes down question is concerned, the answer is the same as the previous.

---

<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:** [April 27, 2017, 2:43pm UTC](https://discuss.elastic.co/t/elasticsearch-curator-4-2-6-clarifications/80628/3 "2017-04-27T14:43:22Z")

</div>

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