# Upgradation process from version 7.x to 8.5

**URL:** <https://discuss.elastic.co/t/upgradation-process-from-version-7-x-to-8-5/321018>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [December 12, 2022, 10:30am UTC](https://discuss.elastic.co/t/upgradation-process-from-version-7-x-to-8-5/321018 "2022-12-12T10:30:41Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abj\_Ins](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@Abj\_Ins](https://discuss.elastic.co/u/Abj_Ins)\
**Post date:** [December 12, 2022, 10:30am UTC](https://discuss.elastic.co/t/upgradation-process-from-version-7-x-to-8-5/321018/1 "2022-12-12T10:30:41Z")

</div>

Hi Team,

Expecting the Upgradation process in detail.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [December 12, 2022, 3:38pm UTC](https://discuss.elastic.co/t/upgradation-process-from-version-7-x-to-8-5/321018/2 "2022-12-12T15:38:08Z")

</div>

which version of 7.x ?

you need minimum 7.17 to upgrade to 8.5

I just upgraded mine, 7.17.1 to 8.5.3  
shutdown elasticsearch cluster, all logstash, all kibana  
save all config for refrence  
upgraded elasticsearch  
started elastic cluster, once up  
upgraded kibana  
started kibana(you will most problem here as some config option change, you will have to check log file for it)  
started logstash

---

<div class="post-metadata">

**Author:** ![Abj\_Ins](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@Abj\_Ins](https://discuss.elastic.co/u/Abj_Ins)\
**Post date:** [December 13, 2022, 6:01am UTC](https://discuss.elastic.co/t/upgradation-process-from-version-7-x-to-8-5/321018/3 "2022-12-13T06:01:41Z")

</div>

Thanks Sachin.

_ **It would be helpful if we get detailed information about upgradation from 7.16 to 7.17** _

We have installed ELK on our local machine (with no clusters and having single node) having ELK version 7.16.

Planning to upgrade from 7.16 to 7.17 first and then ultimately need to upgrade to the latest version 8.5.

While upgrading from 7.16 to 7.17, we are stuck with repository creation.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/4/04540a1cbf57ab29ab19c0f905bfb5c27b3ad21f.png)  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/7/5706bf2870e22d9d67a160fe4bb7709da5e00ecc.png)  
Which one to choose as highlighted above and expecting steps to registering the repository.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![jeeva042](https://avatars.discourse-cdn.com/v4/letter/j/aca169/32.png) [@jeeva042](https://discuss.elastic.co/u/jeeva042)\
**Post date:** [December 13, 2022, 6:52am UTC](https://discuss.elastic.co/t/upgradation-process-from-version-7-x-to-8-5/321018/4 "2022-12-13T06:52:27Z")

</div>

Hello @Abj_Ins,

If you are confused about the snapshot creation option, before starting the upgrade, enable the snapshot repository via the Kibana UI or via dev tools in Kibana using the following queries:

### Shared file system repository:

```auto
PUT /_snapshot/my_fs_backup
{
  "type": "fs",
  "settings": {
    "location": "/mount/backups/my_fs_backup_location",
    "compress": true
  }
}

```

### Read-only URL repository

```auto
PUT /_snapshot/my_read_only_url_repository
{
  "type": "url",
  "settings": {
    "url": "file:/mount/backups/my_fs_backup_location"
  }
}

```

You can refer here for more details:  
[Snapshot and restore](https://www.bookstack.cn/read/elasticsearch-7.9-en/8220cfb6c2f28b72.md) and [here](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/snapshot-restore-apis.html)

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [December 13, 2022, 4:18pm UTC](https://discuss.elastic.co/t/upgradation-process-from-version-7-x-to-8-5/321018/5 "2022-12-13T16:18:51Z")

</div>

if this system is not in production and you have done minimum work.  
then I will suggest just upgrade without running backup.

you have not even said more about your installation

systmctl stop elasticsearch  
systemctl stop kibana  
systemctl stop logstash

use rpm and upgrade all three and start in same fashion  
systemctl start elasticsearch ( make sure it is up by using curl)  
curl -u user:passwd -XGET [http://servername:9200/\_cluster/health?pretty](http://servername:9200/_cluster/health?pretty)  
systemctl start kibana ( go to kibana page and make sure it works)  
systemctl start logstash

---

<div class="post-metadata">

**Author:** ![Abj\_Ins](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@Abj\_Ins](https://discuss.elastic.co/u/Abj_Ins)\
**Post date:** [December 22, 2022, 11:54am UTC](https://discuss.elastic.co/t/upgradation-process-from-version-7-x-to-8-5/321018/6 "2022-12-22T11:54:36Z")

</div>

Thanks @jeeva042 for the update.

Tried with File **Shared file System Repository** code as mentioned above then all existing user created objects are not able to see (Dashboards/data view) in Kibana. ELK setup looks like fresh installation.

1. What could be the cause for such a behavior.
2. How can we restore it back.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 19, 2023, 11:54am UTC](https://discuss.elastic.co/t/upgradation-process-from-version-7-x-to-8-5/321018/7 "2023-01-19T11:54:42Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
