# Snapshot creation to s3 is failing with unknown field name min\_version

**URL:** <https://discuss.elastic.co/t/snapshot-creation-to-s3-is-failing-with-unknown-field-name-min-version/220990>\
**Category:** Elasticsearch\
**Created:** [February 26, 2020, 9:19am UTC](https://discuss.elastic.co/t/snapshot-creation-to-s3-is-failing-with-unknown-field-name-min-version/220990 "2020-02-26T09:19:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sai\_Birada](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sai_birada/32/142367_2.png) [@Sai\_Birada](https://discuss.elastic.co/u/Sai_Birada)\
**Post date:** [February 26, 2020, 9:19am UTC](https://discuss.elastic.co/t/snapshot-creation-to-s3-is-failing-with-unknown-field-name-min-version/220990/1 "2020-02-26T09:19:50Z")

</div>

Hi,  
I created a s3 repository and verified that its getting connected by verify repository.  
Verification status : Connected  
However, when I try to put a snapshot, its throwing parse exception.

PUT /\_snapshot/elk-snapshot/snapshot\_1?wait\_for\_completion=true

{  
"error": {  
"root\_cause": [  
{  
"type": "parse\_exception",  
"reason": "unknown field name [min\_version]"  
}  
],  
"type": "parse\_exception",  
"reason": "unknown field name [min\_version]"  
},  
"status": 400  
}

---

<div class="post-metadata">

**Author:** ![Sai\_Birada](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sai_birada/32/142367_2.png) [@Sai\_Birada](https://discuss.elastic.co/u/Sai_Birada)\
**Post date:** [February 26, 2020, 11:18am UTC](https://discuss.elastic.co/t/snapshot-creation-to-s3-is-failing-with-unknown-field-name-min-version/220990/2 "2020-02-26T11:18:27Z")

</div>

Seems to be a bug with elasticsearch-7.2.0, The exact same steps working just fine with elasticsearch-7.6.0.

Currently I am locked up in a loop with a scenario, where I need to upgrade my elasticsearch-7.2.0 to elasticsearch-7.6.0 to use the feature of auto snapshotting to s3, and I need to post atleast one snapshot to s3 first to try upgrading the cluster to 7.6.0, as the upgradation process is risky.

I already bought a platinum license, any suggestion regarding the way to move forward is highly appreciated.

---

<div class="post-metadata">

**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\
**Post date:** [February 26, 2020, 12:04pm UTC](https://discuss.elastic.co/t/snapshot-creation-to-s3-is-failing-with-unknown-field-name-min-version/220990/3 "2020-02-26T12:04:43Z")

</div>

Hi @Sai_Birada

The problem you're seeing is due to the fact that you are trying to create a snapshot from a `7.2` cluster into a repository that has already been written (snapshot-create or -delete) to by a `7.6` cluster. The `7.6` cluster will have upgraded the repository metadata to a format only understood by `7.6+` because it didn't find any pre 7.6 snapshots in the repo.

You will have to create the snapshot from the `7.2` cluster to a fresh repository (fresh path in S3) that has not yet been touched by `7.6`.

---

<div class="post-metadata">

**Author:** ![Sai\_Birada](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sai_birada/32/142367_2.png) [@Sai\_Birada](https://discuss.elastic.co/u/Sai_Birada)\
**Post date:** [February 26, 2020, 12:50pm UTC](https://discuss.elastic.co/t/snapshot-creation-to-s3-is-failing-with-unknown-field-name-min-version/220990/4 "2020-02-26T12:50:01Z")

</div>

Thans @Armin_Braun, That info helps a lot. So all I need to do is create a fresh repo, backup the data there, and proceed with the cluster upgrade.

---

<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:** [March 25, 2020, 12:50pm UTC](https://discuss.elastic.co/t/snapshot-creation-to-s3-is-failing-with-unknown-field-name-min-version/220990/5 "2020-03-25T12:50:02Z")

</div>

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