Elasticsearch logo Elasticsearch 7 · 8 · OpenSearch · Elastic Cloud

Elasticsearch Backup Tool

Back up Elasticsearch and OpenSearch indices on a schedule — mappings, settings and every document — without registering a snapshot repository or installing anything on the cluster.

Works with Elasticsearch 7 and 8, OpenSearch and Elastic Cloud, with username/password or API-key authentication. Every export is compressed and encrypted with AES-256 before it is stored on your PC, NAS, cloud bucket or SFTP server.

Free Download See how it works
elasticsearch backup tool running a scheduled backup of search indices
products · backed up 2 min ago
REST API/ mappings + settings/ search_after + PIT/ _bulk restore/ API key auth/ streaming gzip/ AES-256-GCM/ Amazon S3/

Everything You Need for Reliable Elasticsearch Backup

7 · 8
Elasticsearch & OpenSearch
Indices
Mappings & analyzers kept
AES-256
Encryption Security
Automated
Scheduled Backup
Video tutorial

Watch How to Backup Elasticsearch Indices Automatically

Free Download Watch on YouTube
Why It Matters

Why Use an Elasticsearch Backup Tool

Search is often the first thing users touch and the last thing anyone backs up. Elasticsearch snapshots need a repository registered on the cluster and stay in the cluster’s own storage — on Elastic Cloud, in the provider’s. A wrong DELETE on an index, a failed reindex or a mapping change with no way back means rebuilding from source data, if it still exists.

⚠️

Deleted or Overwritten Indices

DELETE /products* with a wildcard, an ingest job that recreates an index from an empty source, or an alias switched to the wrong target — the index is gone in a second. A backup from last night brings it back with the same mapping.

💽

Node & Cluster Failure

Single-node clusters and small deployments have no replica to fall back on. When the disk or host dies, the only copy dies with it unless an export was stored off the cluster.

🧰

Bad Reindex & Mapping Migrations

Mappings cannot be changed in place, so migrations mean reindexing — and a wrong analyzer or field type is only discovered afterwards. A backup taken before the change is the rollback.

☁️

Cloud Outages & Plan Changes

Elastic Cloud and Amazon OpenSearch Service keep snapshots in storage you do not control. An independent, encrypted export is the copy you own if the deployment is deleted, downgraded or unavailable.

📋

Compliance & Retention

Order, customer and audit-log indices often have to be reproducible for years. Retention tiers keep daily, weekly, monthly and yearly copies automatically, so history is a restore away.

🛡️

Ransomware & Exposed Clusters

Unauthenticated clusters reachable from the internet are wiped by automated attacks within hours. Encrypted backups kept off the cluster are the clean copy you restore from once access is locked down.

Key Features

Elasticsearch Backup Software - Key Features

Everything you need to back up Elasticsearch and OpenSearch indices automatically and restore them anywhere.

No Snapshot Repository Needed

Snapshots require a repository registered on the cluster and write into the cluster’s own storage — a task for an administrator, and on Elastic Cloud the repository is theirs. This tool exports over the plain REST API instead, so nothing is configured or installed on the cluster.

Mappings & Settings Preserved

Each index’s mapping and settings are captured with the documents, so a restored index has the same field types, analyzers and shard configuration and searches exactly like the original. Cluster-owned settings such as uuid and allocation rules are left out on purpose.

Elasticsearch 7, 8 & OpenSearch

One tool for Elasticsearch 7, Elasticsearch 8, OpenSearch 1 and 2, Elastic Cloud and Amazon OpenSearch Service. The REST calls it needs — mapping, settings, search, bulk — are stable across all of them.

API Key or Password Authentication

Set HTTPS to yes (Elasticsearch 8 and Elastic Cloud require it) and authenticate with a username and password or an API key. Credentials are stored in the Windows Credential Manager, never in a plain-text file.

Stable Paging While the Index Changes

Documents are paged out with a point-in-time search and search_after, 1,000 per request. The export sees a consistent view even while documents are being indexed, and never holds a scroll context open that could expire mid-backup.

Automatic Scheduled Backup

Set a run time and switch on the daily, weekly, monthly or yearly tiers you want. Each tier is also its retention: keep the last 7 daily and 4 weekly copies and older ones are pruned for you. The job runs on its own from the system tray.

Flexible Storage Options

Store index backups on your PC, a NAS share, OneDrive, Amazon S3, Wasabi, Backblaze B2, Cloudflare R2, MinIO, SFTP or FTP — and add a secondary destination so every run is copied to two places.

Compression & AES-256 Encryption

JSON lines compress extremely well — typically 80–90% smaller — and the file is then encrypted with AES-256-GCM using a key derived from your password. Customer data in a shared bucket is unreadable without it.

15-Day Free Trial

Try every feature of the Elasticsearch backup software free for 15 days — no credit card, no hidden charges. If it fits, continue for just $9 per month, billed annually, with a 14-day money-back guarantee.

How It Works

How to Backup Elasticsearch Indices Automatically?

The Elasticsearch Backup Tool turns snapshot repositories and curl scripts into a four-step wizard: connect to the cluster, choose where the backup goes, set the plan, and the software handles every run from then on.

select elasticsearch in the backup wizard connect to elasticsearch cluster over https and list indices select the destination to store elasticsearch backup set elasticsearch backup schedule, retention and encryption

The software exports each selected index with its mapping, settings and documents, compresses and encrypts the file, and stores it at the chosen location on every scheduled run.

Full step-by-step guide

Works Everywhere Elasticsearch Runs

Choose where your cluster lives

Connect the tool to Elasticsearch or OpenSearch wherever it is hosted — your own servers, containers, Kubernetes, Elastic Cloud or Amazon OpenSearch Service. Only the REST endpoint and a login are needed:

Self-Hosted ES 8 Elastic Cloud OpenSearch Amazon OpenSearch Service Docker Elasticsearch Kubernetes / ECK Elasticsearch 7

Self-Hosted Elasticsearch 8

Elasticsearch 8 turns on HTTPS and authentication by default. Set HTTPS to yes and use the elastic superuser or, better, a dedicated user with read and monitor privileges on the indices you back up.

Step 2 Connection
Hostes01.acme.internal
Port9200
Usernameelastic
Password••••••••••
HTTPSyes
Test & list indices Connected

Elastic Cloud

Elastic Cloud deployments expose an HTTPS endpoint on port 443. Paste the Elasticsearch endpoint from the deployment page and authenticate with an API key created in Kibana.

Step 2 Connection
Hostacme-prod.es.eu-west-1.aws.found.io
Port443
API keyVnVhQ2ZHY0JDZGJrU…
HTTPSyes
Test & list indices Connected

Snapshots on Elastic Cloud live in the provider’s storage — this export is the copy you own.

OpenSearch

Self-hosted OpenSearch 1 or 2 works with the same option. Use the admin user or a role with read access to the indices, and set HTTPS to yes when the security plugin is enabled.

Step 2 Connection
Hostsearch01.acme.internal
Port9200
Usernameadmin
Password••••••••••
HTTPSyes
Test & list indices Connected

Amazon OpenSearch Service

A managed OpenSearch domain with fine-grained access control accepts a master username and password over HTTPS on port 443. Connect from inside the VPC or over a VPN.

Step 2 Connection
Hostsearch-acme-abc123.eu-west-1.es.amazonaws.com
Port443
Usernamebackup_user
Password••••••••••
HTTPSyes
Test & list indices Connected

Docker Elasticsearch

Elasticsearch inside a Docker container is backed up over the network — use the compose service name or the port you mapped to the host. Nothing needs to be mounted into the container.

Step 2 Connection
Hostlocalhost
Port9200
Usernameelastic
Password••••••••••
HTTPSyes
Test & list indices Connected

Kubernetes / ECK

A cluster deployed with the Elastic Cloud on Kubernetes operator is reachable through its HTTP service inside the cluster, or through an ingress or port-forward from your PC.

Step 2 Connection
Hostquickstart-es-http.default.svc.cluster.local
Port9200
Usernameelastic
Password••••••••••
HTTPSyes
Test & list indices Connected

Elasticsearch 7

Elasticsearch 7 clusters often run without TLS or authentication on an internal network. Leave HTTPS at no and the credentials empty, and the tool connects the same way.

Step 2 Connection
Hostes7.acme.internal
Port9200
Username
Password
HTTPSno
Test & list indices Connected

Mappings with a custom type name are handled for 7.x.

Inside Elasticsearch Backup Utility

Elasticsearch Index Backup Workflow

Every backup follows the same simple, secure workflow. From exporting an index over REST to storing the encrypted file, each step is designed to keep your data safe and restorable.

1 · Export
mapping + settings + docs
2 · Compress
80-90% smaller
3 · Encrypt
AES-256
4 · Store
retention & logs

Export the index over REST

For each index the tool fetches the mapping and settings, then pages every document out with a point-in-time search and search_after — 1,000 documents per request — so the export sees a stable view while the index keeps changing and never holds a scroll context open. Everything is written as JSON lines into one file: the header with mapping and settings first, then the documents.

# what the app runs — plain REST, no plugins, no repository GET /products/_mapping · GET /products/_settings POST /products/_pit?keep_alive=5m · POST /_search size=1000, search_after 48,210 docs → products_full_03-45-00.esjsonl

Compress Backup

Before saving, the file is compressed in a stream, typically by 80–90% — JSON documents repeat their field names, and gzip loves that. It is never loaded into memory as a whole, so a large index is handled with the same small footprint as a tiny one.

# streamed in chunks — never loaded into RAM products_full_03-45-00.esjsonl → products_full_03-45-00.esjsonl.gz 148 MB → 23 MB (84% smaller)

AES-256 Encryption

After compression the backup is encrypted with AES-256-GCM, using a key derived from your password with scrypt. Every 64 KB chunk gets its own nonce and authentication tag, so tampering is detected and the file is unreadable without the key.

key = scrypt(password, salt) # AES-256-GCM · 64 KB chunks · unique nonce each

Store and Retention

The encrypted file is uploaded to your chosen destination (and to the secondary one, if set), verified by checksum, and logged. Retention tiers delete outdated copies automatically so storage never fills up with files nobody needs.

upload → s3://acme-offsite/Search_indices_nightly/products/… prune: keep 7 daily · 4 weekly · write log

The app runs this for you — there is nothing to type.

The part that matters

A backup you can't restore is just wasted disk

Recovering an index takes four steps in the app: choose the job, choose the point in time, choose what to do with it, review. The tool downloads the file, decrypts it, decompresses it, recreates the index from the saved mapping and settings (cluster-owned settings such as uuid and allocation rules are left out on purpose), then bulk-loads the documents with _bulk — into the original index name or a new one, on any Elasticsearch or OpenSearch cluster you can reach. Press play to watch every step.

Restore into products_v2 first, compare a few searches with production, then switch the alias — a zero-downtime rehearsal that never touches the live index.

Restore: products from Wasabi offsite
Locate backupfind the key in the destination
Downloadpull the encrypted object · 23 MB
Decrypt & verifyAES-256-GCM integrity check
Decompressrestore the original export · 148 MB
Recreate & _bulk loadmapping + settings, then 48,210 documents
sqlbackup · encrypt · elasticsearch
Plaintextproducts_full_20260825.esjsonl.gz
scrypt(password, salt) → 256-bit key · fresh nonce
Ciphertext…
FormatMAGIC(9) · SALT(16) · [ LEN · NONCE(12) · CT+TAG ] × N
256-bitAES key
96-bitnonce / chunk
64 KBchunk size
Security

Watch How Elasticsearch Backup Tool Protects Your Index Backups

Your Elasticsearch backups contain the data your business runs on, so protecting them through the whole backup journey matters. Here, every file is compressed, checksummed and encrypted on your PC before it leaves, and stays protected while it is transferred and stored.

Secure Credential Storage

Your Elasticsearch credentials and connection details are kept in the Windows Credential Manager, never in a plain-text configuration file. The settings file only stores a reference to the entry, which keeps passwords out of reach of anyone browsing the disk.

Backup Integrity Verification

When a Elasticsearch backup is created and sent to a storage location (local, NAS, cloud, SFTP), things can still go wrong on the way:

  • Part of the backup file may be damaged in transit.
  • The file may be stored incompletely because of a network problem.
  • Someone may have modified the backup file without permission.

Checksum verification compares the stored file against the one that was written. If it is corrupted, incomplete or altered, the job is flagged as failed instead of quietly succeeding — so the Elasticsearch backup you rely on is one that will actually restore.

Direct Backup Flow — No Third-Party Servers

The Elasticsearch backup never passes through any of our servers. Everything happens between your machine and the storage location you chose, and the file is encrypted before it leaves. You keep full control over where your backups live and who can open them.

Your data, your storage

Your data. Your choice.
Your storage.

The Elasticsearch backup tool is a desktop application, not a hosted service — it runs on your machine and writes each backup straight to the storage you picked. Nobody charges you per gigabyte, and no copy of your Elasticsearch data ever sits on somebody else’s server.

Choose any destination — or several at once
This PCany folder
External driveUSB or disk
NASnetwork share
OneDriveyour account
Amazon S3your own bucket
S3-compatibleWasabi · B2 · R2 · MinIO
FTPyour own server
SFTPyour own server
No per-GB fee from us Encrypted before it leaves Send to several at once

No storage bill from us

You pay us once for the software — never for gigabytes. Point a job at a folder on your own PC or NAS and the storage costs nothing at all. Prefer the cloud? Use your own Amazon S3, Wasabi, Backblaze B2, Cloudflare R2, MinIO or OneDrive account and pay their rate directly, with no markup in between. Back up 10 GB or 10 TB — the price of the software does not move.

Your Elasticsearch data never passes through us

This is a desktop application. It runs on your machine, connects straight to your Elasticsearch server and writes the backup straight to the destination you chose. Nothing is uploaded to our servers on the way, so we never hold a copy of your data — and it is encrypted with AES-256 before it leaves, so even the storage provider only ever sees ciphertext.

Your passwords stay on your machine

Database passwords are never written into a configuration file and never sent anywhere. They are kept in the Windows Credential Manager, and the settings file only stores a reference to the entry. If you switch on the optional online monitoring, it reports job status only — name, success or failure, size and duration. Never your data, never your credentials.

How It Compares

Elasticsearch Backup Tool vs Snapshots & Other Tools

CapabilityPrapl SQL Backup ToolOther Tools
Backup Automation Automatically ScheduledRequire manual setup
Deployment Support Self-hosted ES 7/8, OpenSearch, Docker, Kubernetes, Elastic Cloud & Amazon OpenSearchLimited
Storage Destination Local/NAS, OneDrive, S3, Wasabi, Backblaze, R2, MinIO, SFTP & FTPLimited storage options
Data security AES-256 before the file leaves your PCGood
Backup Compression YesSupported but limited
Backup Monitoring Dashboard, email & cloud alerts No
Setup Process Simple wizard, four stepsComplex
You hold the keys Always No
Storage cost Your own storage · no per-GB feeOften rented per GB
Why Trust This Elasticsearch Backup Tool with Your Critical Data

Built to Keep Your Indices Recoverable

Designed for Real Backup Challenges

Elasticsearch sits under applications where downtime and data loss have real consequences. This backup tool exists to make regular backups effortless, remove the manual steps people forget, and make sure a restorable copy of your data is always within reach when something goes wrong.

01. Experience

Transparent Backup Process

You should always know how your backups are made and protected. The Elasticsearch backup workflow is simple, documented on this page step by step, and built on Elasticsearch’s own, publicly documented interfaces rather than on anything proprietary or hidden.

02. Authoritativeness

Powered by Trusted Technologies

Every backup is made with REST APIs Elasticsearch and OpenSearch document and support: the mapping and settings APIs for structure, point-in-time search with search_after for documents, and the bulk API for restores. On top of that the tool adds streaming compression and AES-256-GCM encryption before the file reaches its destination.

03. Expertise

Your Backup & Your Encryption Key

Your Elasticsearch backup belongs to you, not to the software. Files are encrypted before they are stored and only your key can unlock them. The tool keeps no password and no hidden access to your backups — they remain under your control, wherever you decide to keep them.

04. Trustworthiness

Sources & further reading

SQLBackup builds directly on Elasticsearch’s own, documented APIs. Verify our approach against the official docs:

Client Feedback

What Clients Are Saying After Using the Elasticsearch Backup Tool

Who It's For

Designed for Every Elasticsearch Deployment

🔎

Search & E-commerce Teams

Product, catalog and content indices get a nightly, encrypted copy with mappings intact — so a deleted index or a bad reindex is an incident, not a rebuild from source.

🏢

SaaS & Software Companies

Whether search runs on your own nodes, in Elastic Cloud or on Amazon OpenSearch, keep every index’s backups organised, encrypted and visible from one dashboard.

🛡️

Security-Focused Organizations

Backups are encrypted with your key before they leave the PC, credentials and API keys stay in the Windows Credential Manager, and nothing is uploaded to a third-party service.

🧪

Development & Testing Teams

Restore a production index into a staging cluster to test analyzers, mapping changes and version upgrades against real documents without touching the live cluster.

🖥️

Infrastructure Administrators

Replace curl scripts and forgotten snapshot policies with scheduled jobs, checksum verification, retention tiers and alerts for Docker, Kubernetes, VM and cloud clusters alike.

🤝

Managed Service Providers (MSPs)

Create one job per client cluster with its own schedule and destination. Backups stay separated, encrypted and monitored in one place.

Technical specs

System Requirement & Basic Information

Storage Required
500 MB Minimum (1 GB Recommended)
RAM
1 GB Minimum (2 GB Recommended)
Versions
Elasticsearch 7 and 8 · OpenSearch 1 and 2 · Elastic Cloud, Amazon OpenSearch Service, self-hosted, Docker, Kubernetes · HTTPS with username/password or API key · system indices skipped
Backup format
JSON lines (.esjsonl): index mapping and settings header followed by every document · restored with the _bulk API
Backup types
Full (per index)
Compression
Streaming gzip — constant memory, no temp bloat · or password-protected ZIP
Encryption
AES-256-GCM, key via scrypt, per-file salt, per-chunk nonce · secrets in the Windows Credential Manager
Destinations
Local / NAS, OneDrive, Amazon S3, S3-compatible (Wasabi, Backblaze B2, Cloudflare R2, MinIO), SFTP, FTP · optional secondary copy
Scheduling & retention
Manual / daily / weekly / monthly / yearly tiers · keep-last-N per tier · checksum verification
Platforms
Windows 10/11 · desktop app, runs from the system tray
Questions & Answers

Frequently Asked Questions

Follow the steps below to store a Elasticsearch backup on your computer:
  1. Run Prapl SQL Backup Tool on your PC.
  2. Click on New Backup and select Elasticsearch.
  3. Enter the host and port, set HTTPS to yes for Elasticsearch 8 or a cloud deployment, provide a username and password or an API key, click Test & list databases and tick the indices to back up.
  4. Choose the Local/NAS option and enter the folder to save the backup in.
  5. Set the plan and click Save & run now.

No. Snapshots need a repository configured on the cluster and write into the cluster’s own storage. This tool exports indices over the plain REST API to your PC, so nothing is configured or installed on the cluster.

Yes. OpenSearch 1 and 2, self-hosted or as Amazon OpenSearch Service, work with the same Elasticsearch option in the wizard. The REST calls the tool uses are the same on both products.

Yes. Use the Elasticsearch endpoint from your deployment page on port 443, set HTTPS to yes and authenticate with an API key or a username and password. The export streams to your PC, independent of the provider’s snapshots.

Yes. Each index’s mapping and settings are saved with the documents and applied again on restore, so field types, analyzers and shard settings match the original. Cluster-owned settings such as uuid, creation date and allocation rules are deliberately left out so the restore works on any cluster.

Yes. A restore can recreate the original index name or a new one (for example products_v2) on the same cluster or on any other Elasticsearch or OpenSearch cluster you can reach, then bulk-loads the documents.

No. When you choose AES-256 protection the backup is encrypted before it is stored, and it can only be opened with the encryption password. Without it the file is unreadable ciphertext — on your PC, on a NAS or in a cloud bucket.

Backup time depends on the size of the data, the speed of the server and of the destination, and whether compression and encryption are enabled. Small databases finish in seconds or minutes; large ones take longer but stream in the background without freezing your PC, and the Dashboard shows live progress and speed.
One tool, every database

Also backs up your other databases

One flat price covers every engine on the machine. Explore the others:

PostgreSQL

pg_dump / pg_restore

MySQL

mysqldump

MariaDB

mariadb-dump

SQL Server

BACKUP DATABASE

Oracle

schema export / Data Pump

SQLite

online backup API

MongoDB

mongodump

Redis

SCAN + DUMP / RESTORE

ClickHouse

HTTP · FORMAT Native

Elasticsearch

You're here

Automate Elasticsearch Index Backup

Create a backup of your Elasticsearch data and save it to local or cloud storage. Download the Elasticsearch Backup Tool and use every feature free for 15 days — no credit card required. If it fits, subscribe for just $9/month with a 14-day money-back guarantee.

Free Download Buy Now
15-day free trial 14-day money-back No auto-renewal