# Elastic upgrade hosted on GCP **URL:** \ **Category:** Elasticsearch\ **Created:** [May 8, 2020, 11:37am UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711 "2020-05-08T11:37:44Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Atlas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atlas/32/67961_2.png) [@Atlas](https://discuss.elastic.co/u/Atlas)\ **Post date:** [May 8, 2020, 11:37am UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/1 "2020-05-08T11:37:44Z")
Hi there, I am pretty new to Elasticsearch and I ran into an Upgrade task that gave me some doubts. I have a 3-nodes Cluster running Elasticsearch on Google Cloud (as a Google Click to Deploy deployment) ad I must upgrade my stack which currently is a 5.6.8 to the latest 7.6.2. I suppose my biggest problem is reindexing, since it seems to be my only valuable data on the cluster. I was scouting on [elastic.co](http://elastic.co) documentation and I was wondering which was the best way to upgrande and reindex between : a) Upgrade to 6.8, install Kibana and run Kibana Agest to automatically reindex to 7.6.2, upgrade then to 7.6.2 b) Set up a new 7.6.2 cluster and just reindex from remote I was going with option b) but I have some doubts since I read that the reindex operation is manual and I have 200+ indexes with 1000+ documents and it scared me a little. If there are other alternatives I am open to discussion 😉 Thanks in advance ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 10, 2020, 11:35pm UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/2 "2020-05-10T23:35:28Z")
Either will work, it's what you are comfy with that is important. > [@Atlas](#): > > 200+ indexes with 1000+ documents That's a really high index to document ratio. You may want to revisit that approach and merge some of these with a reindex? ---
**Author:** ![Atlas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atlas/32/67961_2.png) [@Atlas](https://discuss.elastic.co/u/Atlas)\ **Post date:** [May 11, 2020, 8:38am UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/3 "2020-05-11T08:38:54Z")
Ok Thanks. When reindexing from remote, is there a way to do it automatically or do I have to make a single API call for each index I want to restore? I am referring to [https://www.elastic.co/guide/en/elasticsearch/reference/7.6/reindex-upgrade-remote.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/reindex-upgrade-remote.html) as a guide. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 11, 2020, 9:22am UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/4 "2020-05-11T09:22:21Z")
You can use wildcards, but yes, at the moment it's manual. You could do some simple scripting to automate each call though. ---
**Author:** ![Atlas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atlas/32/67961_2.png) [@Atlas](https://discuss.elastic.co/u/Atlas)\ **Post date:** [May 11, 2020, 9:35am UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/5 "2020-05-11T09:35:23Z")
That's what I thought thanks. After reindexing I expect to have all my old indices and documents back where I left them, with a newer version of ES right? I suppose i shouldn't worry about restoring some indices from a backup after that. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 11, 2020, 10:08am UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/6 "2020-05-11T10:08:37Z")
You should have a backup anyway, it's good habit and risk mitigation. But yes, pending any problems that may crop up, that's the goal 🙂 ---
**Author:** ![Atlas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atlas/32/67961_2.png) [@Atlas](https://discuss.elastic.co/u/Atlas)\ **Post date:** [May 11, 2020, 11:10am UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/7 "2020-05-11T11:10:32Z")
Yes sure. I was asking because I already have a backup and I tried to restore it from Google Cloud Storage( with the repository-gcs plugin) after doing an upgrade to a single node from 5.6 to 6.8 but I noticed that a lot of indices where missing even if the process got no error. I guess this is due to the fact that the different versions of ES require a reindex before upgrading, am I right? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 11, 2020, 10:29pm UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/8 "2020-05-11T22:29:52Z")
> [@Atlas](#): > > I guess this is due to the fact that the different versions of ES require a reindex before upgrading, am I right? Some versions do, yes. [Reindex before upgrading | Elasticsearch Guide [7.6] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/reindex-upgrade.html) has more on that. ---
**Author:** ![Atlas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atlas/32/67961_2.png) [@Atlas](https://discuss.elastic.co/u/Atlas)\ **Post date:** [May 14, 2020, 12:17pm UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/9 "2020-05-14T12:17:19Z")
Is there a way to remove a backed up index manually from the repo? I did a snapshot on GCS but I can't find the index with the id I have, I don't understand how indices are backed up on Google Cloud Storage. Thanks in advance ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 14, 2020, 10:52pm UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/10 "2020-05-14T22:52:18Z")
You would need to delete the snapshot itself, manually removing files is likely to cause other issues. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 11, 2020, 10:52pm UTC](https://discuss.elastic.co/t/elastic-upgrade-hosted-on-gcp/231711/11 "2020-06-11T22:52:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.