mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-06 13:08:29 +00:00
This commit documents the backup and restore of a cluster's security configuration. It is not possible to only backup (or only restore) security configuration, independent to the rest of the cluster's conf, so this describes how a full configuration backup&restore will include security as well. Moreover, it explains how part of the security conf data resides on the special .security index and how to backup that using regular data snapshot API. Co-Authored-By: Lisa Cawley <lcawley@elastic.co> Co-Authored-By: Tim Vernum <tim@adjective.org>
36 lines
1.5 KiB
Plaintext
36 lines
1.5 KiB
Plaintext
[[backup-cluster-data]]
|
|
=== Back up a cluster's data
|
|
++++
|
|
<titleabbrev>Back up the data</titleabbrev>
|
|
++++
|
|
|
|
As with any software that stores data, it is important to routinely back up your
|
|
data. {es} replicas provide high availability during runtime; they enable you to
|
|
tolerate sporadic node loss without an interruption of service.
|
|
|
|
Replicas do not provide protection from catastrophic failure, however. For that,
|
|
you need a real backup of your cluster—a complete copy in case something goes
|
|
wrong.
|
|
|
|
To back up your cluster's data, you can use the <<modules-snapshots,snapshot API>>.
|
|
|
|
include::{es-repo-dir}/modules/snapshots.asciidoc[tag=snapshot-intro]
|
|
|
|
[TIP]
|
|
====
|
|
If your cluster has {es} {security-features} enabled, when you back up your data
|
|
the snapshot API call must be authorized.
|
|
|
|
The `snapshot_user` role is a reserved role that can be assigned to the user
|
|
who is calling the snapshot endpoint. This is the only role necessary if all the user
|
|
does is periodic snapshots as part of the backup procedure. This role includes
|
|
the privileges to list all the existing snapshots (of any repository) as
|
|
well as list and view settings of all indices, including the `.security` index.
|
|
It does *not* grant privileges to create repositories, restore snapshots, or
|
|
search within indices. Hence, the user can view and snapshot all indices, but cannot
|
|
access or modify any data.
|
|
|
|
For more information, see {stack-ov}/security-privileges.html[Security privileges]
|
|
and {stack-ov}/built-in-roles.html[Built-in roles].
|
|
====
|