# Snapshot and Restore - Cluster **URL:** \ **Category:** Elasticsearch\ **Created:** [May 22, 2019, 3:25pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267 "2019-05-22T15:25:59Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\ **Post date:** [May 22, 2019, 3:25pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/1 "2019-05-22T15:25:59Z")
Is there a way we could do a snapshot of a cluster without restarting the cluster after config changes ? please let me know. ---
**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:** [May 22, 2019, 4:44pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/2 "2019-05-22T16:44:56Z")
It depends of what you mean by "after config changes". If it's `elasticsearch.yml`, then no, you need to restart. ---
**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\ **Post date:** [May 22, 2019, 5:03pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/3 "2019-05-22T17:03:57Z")
Is there a way to do backup and restore without the config changes so we do not have to restart ? ---
**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:** [May 22, 2019, 5:16pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/4 "2019-05-22T17:16:25Z")
What kind of repository? ---
**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\ **Post date:** [May 22, 2019, 5:25pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/5 "2019-05-22T17:25:35Z")
its a file system ---
**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:** [May 22, 2019, 6:27pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/6 "2019-05-22T18:27:02Z")
So no. If the shared FS is not defined yet, you can't do that. ---
**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\ **Post date:** [May 22, 2019, 6:37pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/7 "2019-05-22T18:37:44Z")
Instead of file system is there anything that i could use to accomplish without restarting the cluster ? ---
**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:** [May 22, 2019, 7:18pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/8 "2019-05-22T19:18:10Z")
No. Unless you already installed plugins like azure, s3, gcs, hdfs... ---
**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\ **Post date:** [May 22, 2019, 7:20pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/9 "2019-05-22T19:20:22Z")
if i use s3 repo , shall i do the backup and restore without restarting the cluster ? ---
**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:** [May 22, 2019, 7:33pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/10 "2019-05-22T19:33:44Z")
May be. It depends on: - The elasticsearch version you have - If the `repository-s3` plugin is installed yet What is the output of: ```auto GET /_cat/plugins?v ``` BTW, what is the problem of restarting? You can do that by following the rolling upgrade procedure (without upgrading). ---
**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\ **Post date:** [May 22, 2019, 7:59pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/11 "2019-05-22T19:59:57Z")
1. We have elastic version 6.2.2 2. s3 plugin not installed yet 3. No plugins installed 4. We are exploring ways to do backup and restore with out doing cluster restart ... if there is a possibility we shall want to do it that way let us know if backup and restore is possible by anyways without cluster restart ... ---
**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:** [May 22, 2019, 8:21pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/12 "2019-05-22T20:21:41Z")
Unless I was unclear, this is not possible. You can export all documents though but this is not a backup as per say. You did not answer my question BTW: > BTW, what is the problem of restarting? You can do that by following the rolling upgrade procedure (without upgrading). ---
**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\ **Post date:** [May 22, 2019, 8:24pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/13 "2019-05-22T20:24:00Z")
would we not lose data(not a lot though) while doing rolling restart of the nodes ? also we do not want to do this on the production cluster ---
**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\ **Post date:** [May 22, 2019, 8:25pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/14 "2019-05-22T20:25:48Z")
also even with S3 plugin we need to restart the nodes [https://www.elastic.co/guide/en/elasticsearch/plugins/current/repository-s3.html](https://www.elastic.co/guide/en/elasticsearch/plugins/current/repository-s3.html) ---
**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:** [May 22, 2019, 8:45pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/15 "2019-05-22T20:45:42Z")
> [@aniaks](#): > > even with S3 plugin we need to restart the nodes Yes. To install the plugin. Then under some conditions you can create a new repository without restarting even if you didn't configure the credentials. See [S3 repository plugin | Elasticsearch Plugins and Integrations [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/plugins/current/repository-s3-usage.html) > [@aniaks](#): > > would we not lose data(not a lot though) while doing rolling restart of the nodes ? As long as you follow the instructions that should be ok. ---
**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\ **Post date:** [May 23, 2019, 2:35pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/16 "2019-05-23T14:35:07Z")
Per your suggestions above - To do the steps per the url i have to install s3 plugin. which still required a restart. I understand from all the above conversation that for shard file system or s3 we require a rolling restart. ---
**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:** [May 23, 2019, 2:46pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/17 "2019-05-23T14:46:51Z")
That is correct. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 20, 2019, 2:46pm UTC](https://discuss.elastic.co/t/snapshot-and-restore-cluster/182267/18 "2019-06-20T14:46:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.