POST / restore

POST /_restore
{"accepted":true}

Check: GET /_cat/recovery

curl -X POST --insecure https://elastic:your-pass@localhost:9200/_snapshot/your-snap-repo/your-snapshot/_restore
{"accepted":true}

{"error":{"root_cause":[{"type":"snapshot_restore_exception","reason":"[your-snap-repo:snapshot-2022.07.12/2bu2MmlcSiOtd3tPjhwqrQ] cannot restore index [reputation] 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":"[your-snap-repo:snapshot-2022.07.12/2bu2MmlcSiOtd3tPjhwqrQ] cannot restore index [reputation] 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}

Solution: Close index: /_close

Related

• Elasticsearch curl URLs

/_close

• /_cat/indices
• /_cat/shards
• /_cat/allocation
• /_cat/plugins
• /_cat/recovery
• /_cat/snapshot
• /_cat/repositories
• /_cat/health
• /_cat/templates
• Elasticsearch snapshot repositories

See also

• Elasticsearch, installation, ELK, Elastic X-Pack, elasticsearch.yml, logs, ECK, Elasticsearch curl URLs, Elastisearch REST APIs, /_cat/, /_cluster/, /_xpack/, QueryShardException, Elasticsearch index, ELK backup and restore, elasticsearch-cli, Elasticsearch versions, ElasticSearch Snapshot Lifecycle Management (SLM), Low disk watermark, Elasticsearch storage, Elasticsearch users, Elasticsearch roles, search context, shards, Elastic Cloud, Elastic Licensing, ElasticSearch alerts, ESQL

https://www.elastic.co/guide/en/elasticsearch/reference/current/cat-templates.html