# Best practice to backup index daily?

**URL:** <https://discuss.elastic.co/t/best-practice-to-backup-index-daily/18511>\
**Category:** Elasticsearch\
**Created:** [July 7, 2014, 8:12pm UTC](https://discuss.elastic.co/t/best-practice-to-backup-index-daily/18511 "2014-07-07T20:12:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![IronMike](https://avatars.discourse-cdn.com/v4/letter/i/e9a140/32.png) [@IronMike](https://discuss.elastic.co/u/IronMike)\
**Post date:** [July 7, 2014, 8:12pm UTC](https://discuss.elastic.co/t/best-practice-to-backup-index-daily/18511/1 "2014-07-07T20:12:24Z")

</div>

I am able to take a snapshot of the index and back it up to AWS S3. What is  
the best way to automate this approach and have it done daily say every  
days at 12 midnight?  
I am aware that I can probably do it with crontab, but curious if other are  
doing it differently?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8620f7d9-b827-470d-8928-75c308e722cc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8620f7d9-b827-470d-8928-75c308e722cc%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [July 7, 2014, 10:06pm UTC](https://discuss.elastic.co/t/best-practice-to-backup-index-daily/18511/2 "2014-07-07T22:06:00Z")

</div>

The Elasticsearch curator now supports snapshots:

> **[GitHub - elastic/curator: Curator: Tending your Elasticsearch indices](https://github.com/elastic/curator)**
>
> Curator: Tending your Elasticsearch indices. Contribute to elastic/curator development by creating an account on GitHub.

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

You would still need to use cron to schedule tasks, but it would be a  
curator task instead of a direct curl request.

Cheers,

Ivan

On Mon, Jul 7, 2014 at 1:12 PM, sabdalla80 [sabdalla80@gmail.com](mailto:sabdalla80@gmail.com) wrote:

> I am able to take a snapshot of the index and back it up to AWS S3. What  
> is the best way to automate this approach and have it done daily say every  
> days at 12 midnight?  
> I am aware that I can probably do it with crontab, but curious if other  
> are doing it differently?
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/8620f7d9-b827-470d-8928-75c308e722cc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8620f7d9-b827-470d-8928-75c308e722cc%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/8620f7d9-b827-470d-8928-75c308e722cc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/8620f7d9-b827-470d-8928-75c308e722cc%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQB%3D%2BXEGQB3GybgiE3sniiFavc\_NMyTK6LgjNnbus4J-jA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQB%3D%2BXEGQB3GybgiE3sniiFavc_NMyTK6LgjNnbus4J-jA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![IronMike](https://avatars.discourse-cdn.com/v4/letter/i/e9a140/32.png) [@IronMike](https://discuss.elastic.co/u/IronMike)\
**Post date:** [July 8, 2014, 6:14pm UTC](https://discuss.elastic.co/t/best-practice-to-backup-index-daily/18511/3 "2014-07-08T18:14:29Z")

</div>

This looks great. However I am not sure if I am missing anything, When I  
take a snapshot with curl, it works fine by taking the snapshot:

curl -XPUT  
http:local\_host:9200/\_snapshot/es\_repository/snapshot\_1?wait\_for\_completion=true  
However with curator, it completes but no snapshots are actually taken when  
I check, Any ideas what I am missing?  
curator snapshot --most-recent 3 --repository es\_repository

2014-07-08T17:51:20.143 INFO main:644 Job starting  
...

2014-07-08T17:51:20.144 INFO main:654 Default  
timeout of 30 seconds is too low for command SNAPSHOT. Overriding to 21,600  
seconds (6 hours).

2014-07-08T17:51:20.144 INFO \_new\_conn:188 Starting new  
HTTP connection (1): localhost

2014-07-08T17:51:20.153 INFO log\_request\_success:57 GET [http://localhost:9200/](http://localhost:9200/)  
[status:200 request:0.009s]

2014-07-08T17:51:20.154 INFO command\_loop:538 Beginning  
SNAPSHOT operations...

2014-07-08T17:51:20.158 INFO log\_request\_success:57 GET [http://localhost:9200/logstash-\*/\_settings?expand\_wildcards=closed](http://localhost:9200/logstash-*/_settings?expand_wildcards=closed)  
[status:200 request:0.003s]

2014-07-08T17:51:20.158 INFO snap\_latest\_indices:508 Snapshot  
'latest' 3 indices operations completed.

2014-07-08T17:51:20.158 INFO main:671 Done in 0:00:  
00.033295.

On Monday, July 7, 2014 6:06:06 PM UTC-4, Ivan Brusic wrote:

> The Elasticsearch curator now supports snapshots:
> 
> [GitHub - elastic/curator: Curator: Tending your Elasticsearch indices](https://github.com/elasticsearch/curator)
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/blog/elasticsearch-curator-version-1-1-0-released/)
> 
> You would still need to use cron to schedule tasks, but it would be a  
> curator task instead of a direct curl request.
> 
> Cheers,
> 
> Ivan
> 
> On Mon, Jul 7, 2014 at 1:12 PM, sabdalla80 \<[sabda...@gmail.com](mailto:sabda...@gmail.com)  
> \<javascript:\>\> wrote:
> 
> > I am able to take a snapshot of the index and back it up to AWS S3. What  
> > is the best way to automate this approach and have it done daily say every  
> > days at 12 midnight?  
> > I am aware that I can probably do it with crontab, but curious if other  
> > are doing it differently?
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/8620f7d9-b827-470d-8928-75c308e722cc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8620f7d9-b827-470d-8928-75c308e722cc%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/8620f7d9-b827-470d-8928-75c308e722cc%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/8620f7d9-b827-470d-8928-75c308e722cc%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/7bc870f5-470a-432a-9217-e30c4002543f%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/7bc870f5-470a-432a-9217-e30c4002543f%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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 6, 2017, 1:17am UTC](https://discuss.elastic.co/t/best-practice-to-backup-index-daily/18511/4 "2017-07-06T01:17:15Z")

</div>


