# How to roll back from ES 6.4.3 to 5.6.12 - using snapshot & restore

**URL:** <https://discuss.elastic.co/t/how-to-roll-back-from-es-6-4-3-to-5-6-12-using-snapshot-restore/155923>\
**Category:** Elasticsearch\
**Created:** [November 8, 2018, 3:50pm UTC](https://discuss.elastic.co/t/how-to-roll-back-from-es-6-4-3-to-5-6-12-using-snapshot-restore/155923 "2018-11-08T15:50:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![juiip](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@juiip](https://discuss.elastic.co/u/juiip)\
**Post date:** [November 8, 2018, 3:50pm UTC](https://discuss.elastic.co/t/how-to-roll-back-from-es-6-4-3-to-5-6-12-using-snapshot-restore/155923/1 "2018-11-08T15:50:36Z")

</div>

I took a snapshot of my cluster in version 5.6.12, upgraded to 6.4.3 but now want to move back to 5.6.12...  
Is it possible to roll back by restoring this snapshot?

I tried running the following command in Kibana:

```
POST /_snapshot/my_backup/snapshot_07-11-2018/_restore
{
  "include_global_state": true
}

```

However I get the following error and don't know what it means?

```
{
  "error": {
    "root_cause": [
      {
        "type": "invalid_index_name_exception",
        "reason": "Invalid index name [.triggered_watches], already exists as alias",
        "index_uuid": "_na_",
        "index": ".triggered_watches"
      }
    ],
    "type": "invalid_index_name_exception",
    "reason": "Invalid index name [.triggered_watches], already exists as alias",
    "index_uuid": "_na_",
    "index": ".triggered_watches"
  },
  "status": 400
}
```

---

<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:** [December 6, 2018, 3:50pm UTC](https://discuss.elastic.co/t/how-to-roll-back-from-es-6-4-3-to-5-6-12-using-snapshot-restore/155923/2 "2018-12-06T15:50:37Z")

</div>

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