Difference between revisions of "ELK backup and restore"
Jump to navigation
Jump to search
| (7 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
"error": { "root_cause":[ | "error": { "root_cause":[ | ||
{ | { | ||
| − | "type":"snapshot_restore_exception","reason":"[your_repo:snapshot-2022.07.11/iy0NiQdTSJ6dHTFMkiQJHQ] cannot restore index [.security-7] 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_repo:snapshot-2022.07.11/iy0NiQdTSJ6dHTFMkiQJHQ] cannot restore index [.security-7] 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", | "type":"snapshot_restore_exception", | ||
"reason":"[your_repo:snapshot-2022.07.11/iy0NiQdTSJ6dHTFMkiQJHQ] cannot restore index [.security-7] 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" | "reason":"[your_repo:snapshot-2022.07.11/iy0NiQdTSJ6dHTFMkiQJHQ] cannot restore index [.security-7] 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" | ||
} | } | ||
| + | == Related == | ||
| + | * [[Index]] | ||
| + | * [[Snapshot repository]] | ||
| + | [[/_restore]] | ||
| + | [[/_close]] | ||
== See also == | == See also == | ||
| + | * {{Elasticsearch}} | ||
* {{ELK}} | * {{ELK}} | ||
| − | |||
[[Category:ELK]] | [[Category:ELK]] | ||
| + | [[Category:Backup]] | ||
Latest revision as of 08:10, 12 July 2022
https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshot-restore.html
curl -X POST --insecure https://your_elk_ip:YOUR_PASS@localhost:9200/_snapshot/your_repo/your_latest_snapshot_name/_restore
"error": { "root_cause":[
{
"type":"snapshot_restore_exception","reason":"[your_repo:snapshot-2022.07.11/iy0NiQdTSJ6dHTFMkiQJHQ] cannot restore index [.security-7] 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_repo:snapshot-2022.07.11/iy0NiQdTSJ6dHTFMkiQJHQ] cannot restore index [.security-7] 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"
}
Related[edit]
/_restore /_close
See also[edit]
- 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 - Elastic: ELK,
Elasticsearch,Logstash,Kibana, Installation, AWS Elasticsearch, Elastic SIEM, Elastic Beats,metricbeat,filebeat,journalbeat, Elastisearch Service , Search guard, Elasticsearch logs, curator, ILM, Lumberjack protocol,aws_elasticsearch_domain, KQL,elasticsearch.yml, elasticsearch-plugin, elasticsearch-certutil, Elasticsearch release notes/changelog
Advertising:
