Snapshot and Restore

Snapshot and Restore lets you back up a running Elasticsearch cluster using data and state snapshots. Snapshots are important because they provide a copy of your data in case something goes wrong. If you need to roll back to an older version of your data, you can restore a snapshot from the repository.

To get started, open the main menu, then click Stack Management > Snapshot and Restore. With this UI, you can:

Before using this feature, you should be familiar with how snapshots work. Snapshot and Restore is a good source for more detailed information.

The minimum required permissions to access Snapshot and Restore include:

To add privileges, open the main menu, then click Stack Management > Roles.

A repository is where your snapshots live. You must register a snapshot repository before you can perform snapshot and restore operations.

Kibana supports three repository types out of the box: shared file system, read-only URL, and source-only. For more information on these repositories and their settings, see Repositories. To use other repositories, such as S3, see Repository plugins.

The Repositories view displays a list of registered repositories. Click a repository name to view information about the repository, verify its status, or clean it up.

A snapshot is a backup taken from a running Elasticsearch cluster. You’ll find an overview of your snapshots in the Snapshots view, and you can drill down into each snapshot for further investigation.

If you don’t have any snapshots, you can create them using the create snapshot API.

The information stored in a snapshot is not tied to a specific cluster or a cluster name. This enables you to restore a snapshot made from one cluster to another cluster. You might use the restore operation to:

To get started, go to the Snapshots view, find the snapshot, and click the restore icon in the Actions column. The Restore wizard presents options for the restore operation, including which data streams and indices to restore and whether to change index settings. You can restore an existing index only if it’s closed and has the same number of shards as the index in the snapshot.

Once you initiate the restore, you’re navigated to the Restore Status view, where you can track the current state for each shard in the snapshot.

Use a snapshot lifecycle policy to automate the creation and deletion of cluster snapshots. Taking automatic snapshots:

If you don’t have any snapshot policies, follow the Create policy wizard. It walks you through defining when and where to take snapshots, the settings you want, and how long to retain snapshots.

An overview of your policies is on the Policies view. You can drill down into each policy to examine its settings and last successful and failed run.

You can perform the following actions on a snapshot policy:

Delete snapshots to manage your repository storage space. Find the snapshot in the Snapshots view and click the trash icon in the Actions column. To delete snapshots in bulk, select their checkboxes, and then click Delete snapshots.