Restore a snapshot
Added in 0.0.0
Restore a snapshot of a cluster or data streams and indices.
You can restore a snapshot only to a running cluster with an elected master node. The snapshot repository must be registered and available to the cluster. The snapshot and cluster versions must be compatible.
To restore a snapshot, the cluster's global metadata must be writable. Ensure there are't any cluster blocks that prevent writes. The restore operation ignores index blocks.
Before you restore a data stream, ensure the cluster contains a matching index template with data streams enabled. To check, use the index management feature in Kibana or the get index template API:
GET _index_template/*?filter_path=index_templates.name,index_templates.index_template.index_patterns,index_templates.index_template.data_stream
If no such template exists, you can create one or restore a cluster state that contains one. Without a matching index template, a data stream can't roll over or create backing indices.
If your snapshot contains data from App Search or Workplace Search, you must restore the Enterprise Search encryption key before you restore the snapshot.
Path parameters
-
repository
string Required The name of the repository to restore a snapshot from.
-
snapshot
string Required The name of the snapshot to restore.
Query parameters
-
master_timeout
string The period to wait for the master node. If the master node is not available before the timeout expires, the request fails and returns an error. To indicate that the request should never timeout, set it to
-1
. -
wait_for_completion
boolean If
true
, the request returns a response when the restore operation completes. The operation is complete when it finishes all attempts to recover primary shards for restored indices. This applies even if one or more of the recovery attempts fail.If
false
, the request returns a response when the restore operation initializes.
Body
-
feature_states
array[string] The feature states to restore. If
include_global_state
istrue
, the request restores all feature states in the snapshot by default. Ifinclude_global_state
isfalse
, the request restores no feature states by default. Note that specifying an empty array will result in the default behavior. To restore no feature states, regardless of theinclude_global_state
value, specify an array containing only the valuenone
(["none"]
). -
ignore_index_settings
array[string] The index settings to not restore from the snapshot. You can't use this option to ignore
index.number_of_shards
.For data streams, this option applies only to restored backing indices. New backing indices are configured using the data stream's matching index template.
-
include_aliases
boolean If
true
, the request restores aliases for any restored data streams and indices. Iffalse
, the request doesn’t restore aliases. -
include_global_state
boolean If
true
, restore the cluster state. The cluster state includes:- Persistent cluster settings
- Index templates
- Legacy index templates
- Ingest pipelines
- Index lifecycle management (ILM) policies
- Stored scripts
- For snapshots taken after 7.12.0, feature states
If
include_global_state
istrue
, the restore operation merges the legacy index templates in your cluster with the templates contained in the snapshot, replacing any existing ones whose name matches one in the snapshot. It completely removes all persistent settings, non-legacy index templates, ingest pipelines, and ILM lifecycle policies that exist in your cluster and replaces them with the corresponding items from the snapshot.Use the
feature_states
parameter to configure how feature states are restored.If
include_global_state
istrue
and a snapshot was created without a global state then the restore request will fail. -
index_settings
object -
indices
string | array[string] -
partial
boolean If
false
, the entire restore operation will fail if one or more indices included in the snapshot do not have all primary shards available.If true, it allows restoring a partial snapshot of indices with unavailable shards. Only shards that were successfully included in the snapshot will be restored. All missing shards will be recreated as empty.
-
rename_pattern
string A rename pattern to apply to restored data streams and indices. Data streams and indices matching the rename pattern will be renamed according to
rename_replacement
.The rename pattern is applied as defined by the regular expression that supports referencing the original text, according to the
appendReplacement
logic. -
rename_replacement
string The rename replacement string that is used with the
rename_pattern
.
curl \
--request POST 'http://api.example.com/_snapshot/{repository}/{snapshot}/_restore' \
--header "Authorization: $API_KEY" \
--header "Content-Type: application/json" \
--data '"{\n \"indices\": \"index_1,index_2\",\n \"ignore_unavailable\": true,\n \"include_global_state\": false,\n \"rename_pattern\": \"index_(.+)\",\n \"rename_replacement\": \"restored_index_$1\",\n \"include_aliases\": false\n}"'
{
"indices": "index_1,index_2",
"ignore_unavailable": true,
"include_global_state": false,
"rename_pattern": "index_(.+)",
"rename_replacement": "restored_index_$1",
"include_aliases": false
}
{
"indices": "index_1"
}
{
"accepted": true,
"snapshot": {
"indices": [
"string"
],
"snapshot": "string",
"shards": {
"failed": 42.0,
"successful": 42.0,
"total": 42.0,
"failures": [
{
"index": "string",
"node": "string",
"reason": {
"type": "string",
"reason": "string",
"stack_trace": "string",
"caused_by": {},
"root_cause": [
{}
],
"suppressed": [
{}
]
},
"shard": 42.0,
"status": "string"
}
],
"skipped": 42.0
}
}
}