Skip to content
Start freeMenu

§ Databases · Search

Elasticsearch backups, natively.

A snapshot into a fresh repository per run, made through the REST API from the Xtic server — no tool runs on the node and no secret reaches a command line.

What Xtic runs

Snapshot API
PUT /_snapshot/xtic-<run>/snap?wait_for_completion=true  {"indices":"*,-.*","include_global_state":true}

Shown with placeholders. Credentials never appear on a command line: they reach the tool through the environment, a file descriptor or a short-lived file in memory.

Restore paths

  • Alongside: indices restored under a new prefix
  • Original indices: closed or deleted first, after approval
  • Selective: an index pattern per restore

Verification

Snapshot state SUCCESS with no failed shards; cluster health after restore. Every artifact is also hashed, and the stored copy is read back and compared before the run counts as verified.

Version rule

Same or newer version, one major apart at most.

Good to know

  • path.repo must be set on every master and data node — a prerequisite with a rolling restart
  • Multi-node clusters need a shared filesystem for the repository
  • Licence and editions: No licence needed for snapshots.

More databases