mirror of
https://github.com/iSharkFly-Docs/opensearch-docs-cn
synced 2025-03-08 05:20:20 +00:00
f225c77c34
* Added snapshot management Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Snapshot management v2 Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Added snapshot management Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Added user roles Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Added SME comments Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Changed dashboards access from index management to snapshot management Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> * Editorial comments Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>
28 lines
971 B
Markdown
28 lines
971 B
Markdown
---
|
|
layout: default
|
|
title: Snapshots
|
|
nav_order: 65
|
|
has_children: true
|
|
redirect_from: /opensearch/snapshots/
|
|
has_toc: false
|
|
---
|
|
|
|
# Snapshots
|
|
|
|
Snapshots are backups of a cluster's indexes and state. State includes cluster settings, node information, index metadata (mappings, settings, templates, etc.), and shard allocation.
|
|
|
|
Snapshots have two main uses:
|
|
|
|
- **Recovering from failure**
|
|
|
|
For example, if cluster health goes red, you might restore the red indexes from a snapshot.
|
|
|
|
- **Migrating from one cluster to another**
|
|
|
|
For example, if you're moving from a proof-of-concept to a production cluster, you might take a snapshot of the former and restore it on the latter.
|
|
|
|
|
|
You can take and restore snapshots using the [snapshot API]({{site.url}}{{site.baseurl}}/opensearch/snapshots/snapshot-restore).
|
|
|
|
If you need to automate taking snapshots, you can use the [Snapshot Management]({{site.url}}{{site.baseurl}}/opensearch/snapshots/snapshot-management) feature.
|