# Hot backup strategy for Elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [October 14, 2014, 10:12pm UTC](https://discuss.elastic.co/t/hot-backup-strategy-for-elasticsearch/20251 "2014-10-14T22:12:45Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![skm](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@skm](https://discuss.elastic.co/u/skm)\ **Post date:** [October 14, 2014, 10:12pm UTC](https://discuss.elastic.co/t/hot-backup-strategy-for-elasticsearch/20251/1 "2014-10-14T22:12:45Z")
Hello List, Going through the current documentation I found that snapshot/restore mechanism is one type of backup strategy that we can use for ES clusters. Any other recommendations? Using the following 1.elasticsearch- "version" : { "number" : "1.3.4", 1. AWS-cloud-plugin 2. curator curator snapshot --repository mys3\_repository --all-indices (weekend) curator snapshot --repository mys3\_repository --most-recent 1 (every week day) The above would be run as cron jobs from one of the nodes in the cluster. Let me know of recommendations for hot backup for elastic search cluster. Thanks, skm -- 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/fdb9ebae-0352-491c-bca6-dc905cd623ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [October 15, 2014, 7:54am UTC](https://discuss.elastic.co/t/hot-backup-strategy-for-elasticsearch/20251/2 "2014-10-15T07:54:06Z")
No - you should definitely use the snapshot and restore as its the most stable and efficient way for backups there is. -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Wed, Oct 15, 2014 at 1:12 AM, skm [replysonika@gmail.com](mailto:replysonika@gmail.com) wrote: > Hello List, > > Going through the current documentation I found that snapshot/restore > mechanism is one type of backup strategy that we can use for ES clusters. > Any other recommendations? > > Using the following > > 1.elasticsearch- > "version" : { > "number" : "1.3.4", > > 1. AWS-cloud-plugin > 2. curator > > curator snapshot --repository mys3\_repository --all-indices (weekend) > curator snapshot --repository mys3\_repository --most-recent 1 (every week > day) > > The above would be run as cron jobs from one of the nodes in the cluster. > > Let me know of recommendations for hot backup for Elasticsearch cluster. > > Thanks, > skm > > -- > 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/fdb9ebae-0352-491c-bca6-dc905cd623ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae%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/CAHTr4ZtpT5Q2C2sswPDJRN0KK3xNWGbxdUFoctqGd%3D%2B1q7cs1Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtpT5Q2C2sswPDJRN0KK3xNWGbxdUFoctqGd%3D%2B1q7cs1Q%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![skm](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@skm](https://discuss.elastic.co/u/skm)\ **Post date:** [October 15, 2014, 2:15pm UTC](https://discuss.elastic.co/t/hot-backup-strategy-for-elasticsearch/20251/3 "2014-10-15T14:15:39Z")
Thank you for the response! Usually for large amounts of data (TBs) how the snapshot backup strategy work? Full snapshots every week and then most-recent snapshots work well? The most recent would be redundant if there is no new data in the last 24 hrs.? Thanks, skm On Wednesday, October 15, 2014 12:54:13 AM UTC-7, Itamar Syn-Hershko wrote: > No - you should definitely use the snapshot and restore as its the most > stable and efficient way for backups there is. > > -- > > Itamar Syn-Hershko > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > Freelance Developer & Consultant > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > On Wed, Oct 15, 2014 at 1:12 AM, skm \<[reply...@gmail.com](mailto:reply...@gmail.com) \\> > wrote: > > > Hello List, > > > > Going through the current documentation I found that snapshot/restore > > mechanism is one type of backup strategy that we can use for ES clusters. > > Any other recommendations? > > > > Using the following > > > > 1.elasticsearch- > > "version" : { > > "number" : "1.3.4", > > > > 1. AWS-cloud-plugin > > 2. curator > > > > curator snapshot --repository mys3\_repository --all-indices (weekend) > > curator snapshot --repository mys3\_repository --most-recent 1 (every week > > day) > > > > The above would be run as cron jobs from one of the nodes in the cluster. > > > > Let me know of recommendations for hot backup for Elasticsearch cluster. > > > > Thanks, > > skm > > > > -- > > 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) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae%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/e42872cd-7f44-4ada-b1d5-e988edac60e0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e42872cd-7f44-4ada-b1d5-e988edac60e0%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [October 15, 2014, 2:41pm UTC](https://discuss.elastic.co/t/hot-backup-strategy-for-elasticsearch/20251/4 "2014-10-15T14:41:24Z")
Incremental. See > **[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. -- Itamar Syn-Hershko [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) Freelance Developer & Consultant Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) On Wed, Oct 15, 2014 at 5:15 PM, skm [replysonika@gmail.com](mailto:replysonika@gmail.com) wrote: > Thank you for the response! > > Usually for large amounts of data (TBs) how the snapshot backup strategy > work? Full snapshots every week and then most-recent snapshots work well? > The most recent would be redundant if there is no new data in the last 24 > hrs.? > > Thanks, > skm > > On Wednesday, October 15, 2014 12:54:13 AM UTC-7, Itamar Syn-Hershko wrote: > > > No - you should definitely use the snapshot and restore as its the most > > stable and efficient way for backups there is. > > > > -- > > > > Itamar Syn-Hershko > > [http://code972.com](http://code972.com) | @synhershko [https://twitter.com/synhershko](https://twitter.com/synhershko) > > Freelance Developer & Consultant > > Author of RavenDB in Action [http://manning.com/synhershko/](http://manning.com/synhershko/) > > > > On Wed, Oct 15, 2014 at 1:12 AM, skm [reply...@gmail.com](mailto:reply...@gmail.com) wrote: > > > > > Hello List, > > > > > > Going through the current documentation I found that snapshot/restore > > > mechanism is one type of backup strategy that we can use for ES clusters. > > > Any other recommendations? > > > > > > Using the following > > > > > > 1.elasticsearch- > > > "version" : { > > > "number" : "1.3.4", > > > > > > 1. AWS-cloud-plugin > > > 2. curator > > > > > > curator snapshot --repository mys3\_repository --all-indices (weekend) > > > curator snapshot --repository mys3\_repository --most-recent 1 (every > > > week day) > > > > > > The above would be run as cron jobs from one of the nodes in the cluster. > > > > > > Let me know of recommendations for hot backup for Elasticsearch cluster. > > > > > > Thanks, > > > skm > > > > > > -- > > > 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). > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae% > > > [40googlegroups.com](http://40googlegroups.com) > > > [https://groups.google.com/d/msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/fdb9ebae-0352-491c-bca6-dc905cd623ae%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/e42872cd-7f44-4ada-b1d5-e988edac60e0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e42872cd-7f44-4ada-b1d5-e988edac60e0%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/e42872cd-7f44-4ada-b1d5-e988edac60e0%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/e42872cd-7f44-4ada-b1d5-e988edac60e0%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/CAHTr4ZtbuP1qpXXDpV-zrkdhuuO6DACq32-LF45z%3DQ9s2QA4Ag%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtbuP1qpXXDpV-zrkdhuuO6DACq32-LF45z%3DQ9s2QA4Ag%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![skm](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@skm](https://discuss.elastic.co/u/skm)\ **Post date:** [October 15, 2014, 3:07pm UTC](https://discuss.elastic.co/t/hot-backup-strategy-for-elasticsearch/20251/5 "2014-10-15T15:07:18Z")
Thank you! I run the snapshot commands couple times and see the same size snapshots in s3 bucket. Shouldn't it be smaller if this is incremental? there is no change in the data between these time periods. Thanks, skm On Tuesday, October 14, 2014 3:12:45 PM UTC-7, skm wrote: > Hello List, > > Going through the current documentation I found that snapshot/restore > mechanism is one type of backup strategy that we can use for ES clusters. > Any other recommendations? > > Using the following > > 1.elasticsearch- > "version" : { > "number" : "1.3.4", > > 1. AWS-cloud-plugin > 2. curator > > curator snapshot --repository mys3\_repository --all-indices (weekend) > curator snapshot --repository mys3\_repository --most-recent 1 (every week > day) > > The above would be run as cron jobs from one of the nodes in the cluster. > > Let me know of recommendations for hot backup for Elasticsearch cluster. > > Thanks, > skm -- 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/3f5f834a-98ed-4f6f-9772-abfdc85eb077%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3f5f834a-98ed-4f6f-9772-abfdc85eb077%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [October 15, 2014, 4:57pm UTC](https://discuss.elastic.co/t/hot-backup-strategy-for-elasticsearch/20251/6 "2014-10-15T16:57:36Z")
Incremental means that it has only to copy differences. As you said, nothing was indexed. So nothing new (or less) was copied. David > Le 15 oct. 2014 à 17:07, skm [replysonika@gmail.com](mailto:replysonika@gmail.com) a écrit : > > Thank you! > > I run the snapshot commands couple times and see the same size snapshots in s3 bucket. Shouldn't it be smaller if this is incremental? there is no change in the data between these time periods. > > Thanks, > skm > > > On Tuesday, October 14, 2014 3:12:45 PM UTC-7, skm wrote: > > Hello List, > > > > Going through the current documentation I found that snapshot/restore mechanism is one type of backup strategy that we can use for ES clusters. Any other recommendations? > > > > Using the following > > > > 1.elasticsearch- > > "version" : { > > "number" : "1.3.4", > > > > 1. AWS-cloud-plugin > > 2. curator > > > > curator snapshot --repository mys3\_repository --all-indices (weekend) > > curator snapshot --repository mys3\_repository --most-recent 1 (every week day) > > > > The above would be run as cron jobs from one of the nodes in the cluster. > > > > Let me know of recommendations for hot backup for Elasticsearch cluster. > > > > Thanks, > > skm > > -- > 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/3f5f834a-98ed-4f6f-9772-abfdc85eb077%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/3f5f834a-98ed-4f6f-9772-abfdc85eb077%40googlegroups.com). > 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/B29432AE-60C8-4407-9CC5-880E9AE424BE%40pilato.fr](https://groups.google.com/d/msgid/elasticsearch/B29432AE-60C8-4407-9CC5-880E9AE424BE%40pilato.fr). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![skm](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@skm](https://discuss.elastic.co/u/skm)\ **Post date:** [October 15, 2014, 6:33pm UTC](https://discuss.elastic.co/t/hot-backup-strategy-for-elasticsearch/20251/7 "2014-10-15T18:33:11Z")
Thank you! On Tuesday, October 14, 2014 3:12:45 PM UTC-7, skm wrote: > Hello List, > > Going through the current documentation I found that snapshot/restore > mechanism is one type of backup strategy that we can use for ES clusters. > Any other recommendations? > > Using the following > > 1.elasticsearch- > "version" : { > "number" : "1.3.4", > > 1. AWS-cloud-plugin > 2. curator > > curator snapshot --repository mys3\_repository --all-indices (weekend) > curator snapshot --repository mys3\_repository --most-recent 1 (every week > day) > > The above would be run as cron jobs from one of the nodes in the cluster. > > Let me know of recommendations for hot backup for Elasticsearch cluster. > > Thanks, > skm -- 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/0703c2b5-e645-4e70-b3bc-f714db48a5c6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0703c2b5-e645-4e70-b3bc-f714db48a5c6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:55am UTC](https://discuss.elastic.co/t/hot-backup-strategy-for-elasticsearch/20251/8 "2017-07-06T00:55:58Z")