# Elasticsearch restoring got conflicts with the internal system indices

**URL:** <https://discuss.elastic.co/t/elasticsearch-restoring-got-conflicts-with-the-internal-system-indices/337586>\
**Category:** Elasticsearch\
**Tags:** snapshot-and-restore\
**Created:** [July 4, 2023, 6:56pm UTC](https://discuss.elastic.co/t/elasticsearch-restoring-got-conflicts-with-the-internal-system-indices/337586 "2023-07-04T18:56:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Z](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mike_z/32/122216_2.png) [@Mike\_Z](https://discuss.elastic.co/u/Mike_Z)\
**Post date:** [July 4, 2023, 6:56pm UTC](https://discuss.elastic.co/t/elasticsearch-restoring-got-conflicts-with-the-internal-system-indices/337586/1 "2023-07-04T18:56:41Z")

</div>

We are trying to restore a snapshot made previously, using the following command:

```shell
POST /_snapshot/my_backup/my_snapshot_2023.06.30/_restore

```

However, the command keeps getting errors saying `... index [.xxxxxx] because an open index with same name already exists in the cluster. ...`. The index name `.xxxxxx` indicates an internal system index.

```plaintext
{
  "error": {
    "root_cause": [
      {
        "type": "snapshot_restore_exception",
        "reason": "[my_backup:my_snapshot_2023.06.30/Pl0QeAojSgq1p6PYI_JdDg] cannot restore index [.ds-ilm-history-5-2023.02.17-000001] because an open index with same name already exists in the cluster. Either close or delete the existing index or restore the index under a different name by providing a rename pattern and replacement name"
      }
    ],
    "type": "snapshot_restore_exception",
    "reason": "[my_backup:my_snapshot_2023.06.30/Pl0QeAojSgq1p6PYI_JdDg] cannot restore index [.ds-ilm-history-5-2023.02.17-000001] because an open index with same name already exists in the cluster. Either close or delete the existing index or restore the index under a different name by providing a rename pattern and replacement name"
  },
  "status": 500
}

```

The Elasticsearch instance under the test is running on a local virtual machine, and we have backups of the virtual machine. So, we can try any command, if necessary, without risk.

**Our Question:**

- The command `GET /_cat/indices` does not show any of the internal indices. So, how to list all the internal system indices?

- We are new to the backup and restore function, so we wonder if there was anything wrong when taking the snapshot before. We used the command `PUT /_snapshot/my_backup/%3Cmy_snapshot_%7Bnow%2Fd%7D%3E`, and not sure if we should include additional arguments to ignore the system indices.

We will highly appreciate any hints and suggestions.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [July 4, 2023, 8:32pm UTC](https://discuss.elastic.co/t/elasticsearch-restoring-got-conflicts-with-the-internal-system-indices/337586/2 "2023-07-04T20:32:16Z")

</div>

Hi @Mike_Z What version are you on?

If you are trying to test a full restore please take a look [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-restore-snapshot.html#restore-entire-cluster)

Otherwise just list the indices/data streams you are trying to restore using the [indices](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-restore-snapshot.html#restore-index-data-stream) parameter which can take wildcards / multi-target syntax.

Since you are not setting either the restore is trying to restore everything without instructions.

If you only want to snapshot and restore data / certain indices and data streams then you could name them when creating the snapshot

---

<div class="post-metadata">

**Author:** ![Mike\_Z](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mike_z/32/122216_2.png) [@Mike\_Z](https://discuss.elastic.co/u/Mike_Z)\
**Post date:** [July 5, 2023, 11:25pm UTC](https://discuss.elastic.co/t/elasticsearch-restoring-got-conflicts-with-the-internal-system-indices/337586/3 "2023-07-05T23:25:50Z")

</div>

Resolved the issue with @stephenb 's advice:

I should restore only the `my-index-00001` index, not to restore the entire cluster. However, the "Restore an entire cluster" procedure works anyway.

I also verified the procedure of restoring a specific index.

Thank you again for the help.

---

<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:** [August 2, 2023, 11:26pm UTC](https://discuss.elastic.co/t/elasticsearch-restoring-got-conflicts-with-the-internal-system-indices/337586/4 "2023-08-02T23:26:00Z")

</div>

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