# Automating Index refreshes **URL:** \ **Category:** Elasticsearch\ **Created:** [October 2, 2014, 10:18am UTC](https://discuss.elastic.co/t/automating-index-refreshes/20045 "2014-10-02T10:18:21Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![gringogordo](https://avatars.discourse-cdn.com/v4/letter/g/a87d85/32.png) [@gringogordo](https://discuss.elastic.co/u/gringogordo)\ **Post date:** [October 2, 2014, 10:18am UTC](https://discuss.elastic.co/t/automating-index-refreshes/20045/1 "2014-10-02T10:18:21Z")
Hi, I've just taken over support of a web application with a elasticsearch back end. Currently we do intermittent data refreshes by building an es index on a build server, zipping it up, copying it over to UAT, stopping Tomcat and elastic search, copying over the new index structure, doing some minor config (change the top level folder name (in the data folder) from app\_dev to app\_uat to app\_live) and then restarting the services. I'm pretty new to this but I'm wondering if anyone has any opinions on the best way to automate this process ? We would rather continue to rebuild the index on the build server if possible but I'm guessing there may be a better way to do a data refresh than to build a convoluted dos script (we are using a windows environment) Any suggestions or help much appreciated. Thanks Ben. -- 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/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [October 2, 2014, 10:38am UTC](https://discuss.elastic.co/t/automating-index-refreshes/20045/2 "2014-10-02T10:38:00Z")
Look into snapshot/restore > **[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. Jörg On Thu, Oct 2, 2014 at 12:18 PM, gringogordo [benkdishman@gmail.com](mailto:benkdishman@gmail.com) wrote: > Hi, > > I've just taken over support of a web application with a elasticsearch > back end. Currently we do intermittent data refreshes by building an es > index on a build server, zipping it up, copying it over to UAT, stopping > Tomcat and Elasticsearch, copying over the new index structure, doing some > minor config (change the top level folder name (in the data folder) from > app\_dev to app\_uat to app\_live) and then restarting the services. > > I'm pretty new to this but I'm wondering if anyone has any opinions on the > best way to automate this process ? We would rather continue to rebuild > the index on the build server if possible but I'm guessing there may be a > better way to do a data refresh than to build a convoluted dos script (we > are using a windows environment) > > Any suggestions or help much appreciated. > > Thanks > > Ben. > > -- > 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/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%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/CAKdsXoEgQ%2BWTbythMacJ1UGMRGFY%2B9W0mXXV1sSRW\_f\_bKodNQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoEgQ%2BWTbythMacJ1UGMRGFY%2B9W0mXXV1sSRW_f_bKodNQ%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![gringogordo](https://avatars.discourse-cdn.com/v4/letter/g/a87d85/32.png) [@gringogordo](https://discuss.elastic.co/u/gringogordo)\ **Post date:** [October 7, 2014, 4:03pm UTC](https://discuss.elastic.co/t/automating-index-refreshes/20045/3 "2014-10-07T16:03:18Z")
Many thanks for this. I've realised now we are running a fairly old version (0.90.11) which I don't think has this functionality (?). I guess I'll push on anyway but out of interest do you think I'll encounter many issues upgrading from 0.90 to 1.3 ? Thanks On Thursday, October 2, 2014 11:38:05 AM UTC+1, Jörg Prante wrote: > Look into snapshot/restore > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-snapshots.html) > > Jörg > > On Thu, Oct 2, 2014 at 12:18 PM, gringogordo \<[benkd...@gmail.com](mailto:benkd...@gmail.com) > \\> wrote: > > > Hi, > > > > I've just taken over support of a web application with a elasticsearch > > back end. Currently we do intermittent data refreshes by building an es > > index on a build server, zipping it up, copying it over to UAT, stopping > > Tomcat and Elasticsearch, copying over the new index structure, doing some > > minor config (change the top level folder name (in the data folder) from > > app\_dev to app\_uat to app\_live) and then restarting the services. > > > > I'm pretty new to this but I'm wondering if anyone has any opinions on > > the best way to automate this process ? We would rather continue to > > rebuild the index on the build server if possible but I'm guessing there > > may be a better way to do a data refresh than to build a convoluted dos > > script (we are using a windows environment) > > > > Any suggestions or help much appreciated. > > > > Thanks > > > > Ben. > > > > -- > > 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/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b3c005b6-6471-4b2a-ac50-ed072a45b527%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/32ce2897-828a-475a-a187-7d9cc75f971b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/32ce2897-828a-475a-a187-7d9cc75f971b%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:57am UTC](https://discuss.elastic.co/t/automating-index-refreshes/20045/4 "2017-07-06T00:57:51Z")