# Restore v1.5 snapshot into v2.1 cluster

**URL:** <https://discuss.elastic.co/t/restore-v1-5-snapshot-into-v2-1-cluster/40967>\
**Category:** Elasticsearch\
**Created:** [February 4, 2016, 1:52pm UTC](https://discuss.elastic.co/t/restore-v1-5-snapshot-into-v2-1-cluster/40967 "2016-02-04T13:52:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Akshay\_Davis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akshay_davis/32/957_2.png) [@Akshay\_Davis](https://discuss.elastic.co/u/Akshay_Davis)\
**Post date:** [February 4, 2016, 1:52pm UTC](https://discuss.elastic.co/t/restore-v1-5-snapshot-into-v2-1-cluster/40967/1 "2016-02-04T13:52:15Z")

</div>

I created a set of snapshots in v1.5 and then upgraded to v2.1. I added the path to the whitelisted set of paths in path.repo and tested creating a snapshot.

That all worked fine, however I am not able to restore any of the snapshots created with the older version of elasticsearch. The snap-{index}.dat and meta-{index}.dat files are missing for the older snapshots, and a snapshot\_missing\_exception is thrown.

Is there anyway to restore these older snapshots?

-Akshay

---

<div class="post-metadata">

**Author:** ![paulkeogh](https://avatars.discourse-cdn.com/v4/letter/p/8dc957/32.png) [@paulkeogh](https://discuss.elastic.co/u/paulkeogh)\
**Post date:** [February 4, 2016, 2:12pm UTC](https://discuss.elastic.co/t/restore-v1-5-snapshot-into-v2-1-cluster/40967/2 "2016-02-04T14:12:15Z")

</div>

The first thing you should do is run the migration plugin to determine if the data is suitable for migration to 2.x;

> **[elastic/elasticsearch-migration](https://github.com/elastic/elasticsearch-migration)**
>
> elasticsearch-migration - This plugin will help you to check whether you can upgrade directly to the next major version of Elasticsearch, or whether you need to make changes to your data and cluste...

but you will need to restore to a 1.5 instance to determine this.

I believe you could also restore to 1.5 and use a logstash input to read from 1.5 and a logstash output to write to 2.1 (but I haven't tested this myself).

---

<div class="post-metadata">

**Author:** ![Akshay\_Davis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akshay_davis/32/957_2.png) [@Akshay\_Davis](https://discuss.elastic.co/u/Akshay_Davis)\
**Post date:** [February 4, 2016, 2:26pm UTC](https://discuss.elastic.co/t/restore-v1-5-snapshot-into-v2-1-cluster/40967/3 "2016-02-04T14:26:26Z")

</div>

Thanks Paul. I had checked the indexes with the migration plugin, but was hoping for an easier way of restoring the data.

Was this listed in the breaking changes for snapshot and restore? I thought I'd gone through them all, but didn't see anything referring to this.

-Akshay

---

<div class="post-metadata">

**Author:** ![Akshay\_Davis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akshay_davis/32/957_2.png) [@Akshay\_Davis](https://discuss.elastic.co/u/Akshay_Davis)\
**Post date:** [February 4, 2016, 3:17pm UTC](https://discuss.elastic.co/t/restore-v1-5-snapshot-into-v2-1-cluster/40967/4 "2016-02-04T15:17:06Z")

</div>

It appears to be a user error on our part. The archive folder was moved and not all the files were transferred. The metadata files were moved but not the snapshot files. Once this was done the restore functions worked as expected in v2.

---

<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:** [July 5, 2017, 11:18pm UTC](https://discuss.elastic.co/t/restore-v1-5-snapshot-into-v2-1-cluster/40967/5 "2017-07-05T23:18:53Z")

</div>