Elasticsearch Restore

Opster Team

May 22, 2022 | 1 min read


In addition to reading this guide, we recommend you run the Elasticsearch Health Check-Up. It will detect issues and improve your Elasticsearch performance by analyzing your shard sizes, threadpools, memory, snapshots, disk watermarks and more.

The Elasticsearch Check-Up is free and requires no installation.

Overview

In Elasticsearch, restore refers to the snapshot restore mechanism, which returns indices or clusters to a previous, saved state. You can restore the entire cluster from the snapshot or restore an individual index or selected indices.

Examples

To restore the whole snapshot:

POST /_snapshot/my_backup/snapshot-01-11-2019/_restore

To restore an individual index:

POST /_snapshot/my_backup/snapshot-01-11-2019/_restore
{
  "indices": "my_index"
}

Notes

  • If you are using a security tool like Searchguard, the snapshot restore capability must be enabled in elasticsearch.yml. Otherwise, it will throw a security exception.

Common issues

  • If an index or indices already exist with the same names as those you are going to restore, they need to either be closed or deleted before you can restore from a snapshot. Otherwise, the restore operation will fail due to an error that the index already exists.

Related log errors to this ES concept


Failed to update restore state
Store cannot be marked as corrupted
Cant read metadata from store; will not reuse local files during restore
Failed to restore snapshot
Failed to delete file during snapshot cleanup
Cant calculate hash from blog for file
Failed to list directory some of files might not be deleted
Failed to update snapshot status for
Failed to update snapshot status to
Restore is done
Failed to sync restore state after master switch

Find and fix issues Elasticsearch issues, try AutoOps

Watch product tour

Try For Free
Skip to content