# How to migrate from version 7.12 to version 7.16.2?

**URL:** <https://discuss.elastic.co/t/how-to-migrate-from-version-7-12-to-version-7-16-2/293964>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [January 11, 2022, 2:44am UTC](https://discuss.elastic.co/t/how-to-migrate-from-version-7-12-to-version-7-16-2/293964 "2022-01-11T02:44:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![wajika](https://avatars.discourse-cdn.com/v4/letter/w/977dab/32.png) [@wajika](https://discuss.elastic.co/u/wajika)\
**Post date:** [January 11, 2022, 2:44am UTC](https://discuss.elastic.co/t/how-to-migrate-from-version-7-12-to-version-7-16-2/293964/1 "2022-01-11T02:44:47Z")

</div>

7.12 cluster

 ![7.12](https://us1.discourse-cdn.com/elastic/original/3X/e/8/e8db1707a6679f92cfe1cb3d1905af41714c32e4.png)  
 ![7.12 2](https://us1.discourse-cdn.com/elastic/original/3X/d/4/d40f9fee8eb4f3ebefb5449f2728d29393a6829c.png)

7.16

 ![7.16](https://us1.discourse-cdn.com/elastic/original/3X/c/2/c27b35de8d36847facee6be7cfa51542eb7d6858.png)  
 ![7.16 2](https://us1.discourse-cdn.com/elastic/original/3X/c/8/c8a96390cffe7eaed162b3164718069004792125.png)

I made a snapshot on the 7.12 cluster, shared the snapshot using NFS, then created a new 7.16 cluster, mounted the nfs path, and registered the warehouse with the same name on kibana. After the registration, I browsed the snapshot UI and found Didn't find any existing snapshots, is this the wrong way to do it?  
I see that Elasticsearch cloud service has such an [operation case](https://www.elastic.co/guide/en/cloud/current/ec-migrate-from-aws.html), I don't know if it is also suitable for private deployment environment.

Also I have a question, will snapshots keep xpack authorization records?

---

<div class="post-metadata">

**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:** [January 11, 2022, 3:53am UTC](https://discuss.elastic.co/t/how-to-migrate-from-version-7-12-to-version-7-16-2/293964/2 "2022-01-11T03:53:05Z")

</div>

Did you mount the repo on the newer cluster as read-only?

> **[Restore a snapshot | Elasticsearch Guide \[7.16\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.16/snapshots-restore-snapshot.html#restore-different-cluster)**

---

<div class="post-metadata">

**Author:** ![wajika](https://avatars.discourse-cdn.com/v4/letter/w/977dab/32.png) [@wajika](https://discuss.elastic.co/u/wajika)\
**Post date:** [January 11, 2022, 6:38am UTC](https://discuss.elastic.co/t/how-to-migrate-from-version-7-12-to-version-7-16-2/293964/3 "2022-01-11T06:38:03Z")

</div>

Current result

```auto
cat /proc/mounts | grep nfs
192.168.10.141:/home/esdata/snapshot /home/esdata/snapshot nfs4 ro,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.10.26,local_lock=none,addr=192.168.10.141 0 0

```

```auto
PUT _snapshot/local
{
  "type": "fs",
  "settings": {
    "location": "snapshot",
    "readonly": true
  }
}

```

```auto
GET /_snapshot/local/_current
{
  "snapshots" : [],
  "total" : 0,
  "remaining" : 0
}

```

The above is operating on the New Node.

---

<div class="post-metadata">

**Author:** ![wajika](https://avatars.discourse-cdn.com/v4/letter/w/977dab/32.png) [@wajika](https://discuss.elastic.co/u/wajika)\
**Post date:** [January 12, 2022, 8:32am UTC](https://discuss.elastic.co/t/how-to-migrate-from-version-7-12-to-version-7-16-2/293964/4 "2022-01-12T08:32:44Z")

</div>

On the new cluster, I deleted the previously registered repo and created a new type:url repo. The same operation, the prompt I got is still [local:snapshot\_2] snapshot does not exist

```auto
PUT _snapshot/local
{
  "type": "url",
  "settings": {
    "url": "file:/home/esdata/snapshot"
  }
}

POST /_snapshot/local/snapshot_2/_restore
{
  "error" : {
    "root_cause" : [
      {
        "type" : "snapshot_restore_exception",
        "reason" : "[local:snapshot_2] snapshot does not exist"
      }
    ],
    "type" : "snapshot_restore_exception",
    "reason" : "[local:snapshot_2] snapshot does not exist"
  },
  "status" : 500
}

```

---

<div class="post-metadata">

**Author:** ![wajika](https://avatars.discourse-cdn.com/v4/letter/w/977dab/32.png) [@wajika](https://discuss.elastic.co/u/wajika)\
**Post date:** [January 12, 2022, 8:46am UTC](https://discuss.elastic.co/t/how-to-migrate-from-version-7-12-to-version-7-16-2/293964/5 "2022-01-12T08:46:53Z")

</div>

I noticed that [other people's solutions](https://stackoverflow.com/questions/54598720/elastic-search-snapshot-restore-another-cluster/70678529#70678529) are to directly overwrite the data of nodeA to the data of nodeB, but I saw in the elastic documentation that nodeB can only mount the NFS directory in read-only mode. Is my understanding wrong?

---

<div class="post-metadata">

**Author:** ![wajika](https://avatars.discourse-cdn.com/v4/letter/w/977dab/32.png) [@wajika](https://discuss.elastic.co/u/wajika)\
**Post date:** [January 21, 2022, 7:52am UTC](https://discuss.elastic.co/t/how-to-migrate-from-version-7-12-to-version-7-16-2/293964/6 "2022-01-21T07:52:31Z")

</div>

I installed the cluster of version 7.16.3. I replaced the snapshot directory generated by version 7.12.0 with the directory created in advance by version 7.16.3, and then prompted that "[local:beifen/WMgGeuykR-KMhD96mwcnRw]" was missing. In this case, it should be It is not possible to directly use the method of directory replacement.

I want a more professional answer.

---

<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:** [February 18, 2022, 7:52am UTC](https://discuss.elastic.co/t/how-to-migrate-from-version-7-12-to-version-7-16-2/293964/7 "2022-02-18T07:52:58Z")

</div>

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