# Rolling back ES database from 7.16 to 7.10 **URL:** \ **Category:** Elasticsearch\ **Created:** [February 25, 2022, 10:14am UTC](https://discuss.elastic.co/t/rolling-back-es-database-from-7-16-to-7-10/298263 "2022-02-25T10:14:49Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![tullhe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tullhe/32/102327_2.png) [@tullhe](https://discuss.elastic.co/u/tullhe)\ **Post date:** [February 25, 2022, 10:14am UTC](https://discuss.elastic.co/t/rolling-back-es-database-from-7-16-to-7-10/298263/1 "2022-02-25T10:14:49Z")
Hello fellow Elasticos I've got an ES database that I accidentally upgraded to 7.16 following a stupid apt-get update For it to remain compatible with my applications, I need to roll it back to 7.10 There doesn't seem to be any offical advice on how to do this, but surely the upgrade cannot be one way. I'll take any route, no matter how convoluted and difficult. Please please is there a way to get my data back into ES 7.10? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [February 25, 2022, 10:19am UTC](https://discuss.elastic.co/t/rolling-back-es-database-from-7-16-to-7-10/298263/2 "2022-02-25T10:19:46Z")
Elasticsearch does not support downgrades. The only way to get back to a pervious version is to spin up an empty cluster and restore a [snapshot](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/snapshot-restore-apis.html) taken before the upgrade. If you do not have a snapshot I believe you will need to reindex from remote into a new empty 7.10 cluster. ---
**Author:** ![tullhe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tullhe/32/102327_2.png) [@tullhe](https://discuss.elastic.co/u/tullhe)\ **Post date:** [February 25, 2022, 10:33am UTC](https://discuss.elastic.co/t/rolling-back-es-database-from-7-16-to-7-10/298263/3 "2022-02-25T10:33:06Z")
Thanks so much for the quick response. So I can see there is some documentation on reindex from remote here: > **[Reindex API | Elasticsearch Guide \[8.0\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html#reindex-from-remote)** How does this work with multi-node setups? (is there anything closer to a runbook/operational guide to how to execute this?) Does the new cluster need to have the same number of nodes, or can it just have a single node with sufficient storage to hold all data from all nodes? Assume that I don't have the same hardware available to spin up a replacement cluster wholesale, and instead need to use the same hardware to host the restored 7.10 nodes. Once the data is moved to the new cluster, is it just a matter of reindex from remote back? How long approximately does reindex from remote take? Eg. is there a way I can estimate downtime based on gb of data? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [February 25, 2022, 10:58am UTC](https://discuss.elastic.co/t/rolling-back-es-database-from-7-16-to-7-10/298263/4 "2022-02-25T10:58:04Z")
> [@tullhe](#): > > How does this work with multi-node setups? (is there anything closer to a runbook/operational guide to how to execute this?) Not that I know of. You need to run it index by index. > [@tullhe](#): > > Does the new cluster need to have the same number of nodes, or can it just have a single node with sufficient storage to hold all data from all nodes? Cluster size does not need to be the same. > [@tullhe](#): > > Assume that I don't have the same hardware available to spin up a replacement cluster wholesale, and instead need to use the same hardware to host the restored 7.10 nodes. > Once the data is moved to the new cluster, is it just a matter of reindex from remote back? Spin up a single 7.10 node if this can hold the data. Once reindexing is complete you can add remove the 7.16 nodes and create new 7.10 nodes that you add to the 7.10 node to form a cluster. > [@tullhe](#): > > How long approximately does reindex from remote take? Eg. is there a way I can estimate downtime based on gb of data? It depends on the data, process and hardware so is impossible to tell. ---
**Author:** ![tullhe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tullhe/32/102327_2.png) [@tullhe](https://discuss.elastic.co/u/tullhe)\ **Post date:** [February 25, 2022, 11:01am UTC](https://discuss.elastic.co/t/rolling-back-es-database-from-7-16-to-7-10/298263/5 "2022-02-25T11:01:31Z")
Thanks. Sorry last Q. Is there a way of running it against all index on the cluster or do they actually need to be specified one by one? Does reindex to remote require downtime? (Or can it run as a background task?) ---
**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:** [February 25, 2022, 11:54am UTC](https://discuss.elastic.co/t/rolling-back-es-database-from-7-16-to-7-10/298263/6 "2022-02-25T11:54:33Z")
What's wrong with using 7.16 instead of an old version? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 25, 2022, 11:55am UTC](https://discuss.elastic.co/t/rolling-back-es-database-from-7-16-to-7-10/298263/7 "2022-03-25T11:55:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.