# \#snapshot-and-restore **URL:** https://discuss.elastic.co/tag/snapshot-and-restore/89.md [Latest](https://discuss.elastic.co/latest.md) · [Categories](https://discuss.elastic.co/categories.md) · [Tags](https://discuss.elastic.co/tags.md) --- ## [How to reliably verify a snapshot restore succeeded? Failed shards disappear from \_recovery](https://discuss.elastic.co/t/how-to-reliably-verify-a-snapshot-restore-succeeded-failed-shards-disappear-from-recovery/389912)
**Author:** [@ciprianamza](https://discuss.elastic.co/u/ciprianamza)\ **Replies:** 10\ **Last updated:** [August 30, 2026, 4:03pm UTC](https://discuss.elastic.co/t/how-to-reliably-verify-a-snapshot-restore-succeeded-failed-shards-disappear-from-recovery/389912 "2026-08-30T16:03:41Z")
Hello, I'd like to raise a possible problem I recently ran into in an internal application, and which I see the current Curator implementation mirrors as well (curator/curator/utils.py at v5.8.4 · elastic/curator · GitH… --- ## [Elasticsearch 7.17.28 Critical Bugs](https://discuss.elastic.co/t/elasticsearch-7-17-28-critical-bugs/387493)
**Author:** [@Abdullah\_Shah](https://discuss.elastic.co/u/Abdullah_Shah)\ **Replies:** 4\ **Last updated:** [July 9, 2026, 8:40am UTC](https://discuss.elastic.co/t/elasticsearch-7-17-28-critical-bugs/387493 "2026-07-09T08:40:31Z")
Anyone still using Elasticsearch 7.17.28 I'm facing some issues and would like to see if it's a elasticsearch issue or something else Issues like Snapshot repo permission issue Desc: Elasticsearch loses repo access… --- ## [Elasticsearch 9.2.1 snapshot visible in repository but restore fails with snapshot\_missing\_exception](https://discuss.elastic.co/t/elasticsearch-9-2-1-snapshot-visible-in-repository-but-restore-fails-with-snapshot-missing-exception/386829)
**Author:** [@shantia](https://discuss.elastic.co/u/shantia)\ **Replies:** 8\ **Last updated:** [June 15, 2026, 1:59pm UTC](https://discuss.elastic.co/t/elasticsearch-9-2-1-snapshot-visible-in-repository-but-restore-fails-with-snapshot-missing-exception/386829 "2026-06-15T13:59:41Z")
I have an Elasticsearch 9.2.1 cluster configured with Snapshot Lifecycle Management (SLM) that takes nightly snapshots to an S3 repository. The snapshots are successfully created, and I can see all snapshot metadata in t… --- ## [S3 compatible storage are not able to mounted for snapshot](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444)
**Author:** [@Rajesh\_Kannan](https://discuss.elastic.co/u/Rajesh_Kannan)\ **Replies:** 11\ **Last updated:** [May 27, 2026, 11:05am UTC](https://discuss.elastic.co/t/s3-compatible-storage-are-not-able-to-mounted-for-snapshot/386444 "2026-05-27T11:05:50Z")
We are trying to mount the s3 storage( S3 compatible DataCore (caringo)) bucket on elastic 9.3.0 using the below command and we are getting "s3\_exception: A header you provided implies functionality that is not implement… --- ## [Unable to create snapshots with cifs share 9.4.0](https://discuss.elastic.co/t/unable-to-create-snapshots-with-cifs-share-9-4-0/386271)
**Author:** [@expErg](https://discuss.elastic.co/u/expErg)\ **Replies:** 4\ **Last updated:** [May 12, 2026, 7:19am UTC](https://discuss.elastic.co/t/unable-to-create-snapshots-with-cifs-share-9-4-0/386271 "2026-05-12T07:19:04Z")
Hello, Since upgrading to 9.4.0, we are experiencing snapshot failures on our CIFS-mounted shared repository. Timeline: Last successful snapshot: May 6, before the upgrade Upgrade to 9.4.0 performed: May 6 at 12:00 P… --- ## [Advice on snapshot and restore setup for elasticsearch DR scenario](https://discuss.elastic.co/t/advice-on-snapshot-and-restore-setup-for-elasticsearch-dr-scenario/385873)
**Author:** [@fffasttFGHb3t](https://discuss.elastic.co/u/fffasttFGHb3t)\ **Replies:** 1\ **Last updated:** [April 13, 2026, 6:55pm UTC](https://discuss.elastic.co/t/advice-on-snapshot-and-restore-setup-for-elasticsearch-dr-scenario/385873 "2026-04-13T18:55:09Z")
We currently have an elasticsearch cluster deployed on-prem kubernetes with the elastic operator. Our main goals are exactly as described in the documentation: Regularly back up a cluster with no downtime Recover data… --- ## [Architecture Validation: Backing up ES Clusters to Local Disk without NAS (using S3 Gateway sidecar)](https://discuss.elastic.co/t/architecture-validation-backing-up-es-clusters-to-local-disk-without-nas-using-s3-gateway-sidecar/384020)
**Author:** [@Maciek\_Pilawski](https://discuss.elastic.co/u/Maciek_Pilawski)\ **Replies:** 7\ **Last updated:** [March 27, 2026, 6:24am UTC](https://discuss.elastic.co/t/architecture-validation-backing-up-es-clusters-to-local-disk-without-nas-using-s3-gateway-sidecar/384020 "2026-03-27T06:24:48Z")
The Context I am a C++ developer working on an on-premise Visual Analytics application. Our service (DocumentStore) manages an Elasticsearch cluster (handling logs, events, configuration). We need to implement a Backup & … --- ## [Error Migration 8.19.12 -\> 9.1.3](https://discuss.elastic.co/t/error-migration-8-19-12-9-1-3/385410)
**Author:** [@M1ghty1](https://discuss.elastic.co/u/M1ghty1)\ **Replies:** 5\ **Last updated:** [March 11, 2026, 12:24pm UTC](https://discuss.elastic.co/t/error-migration-8-19-12-9-1-3/385410 "2026-03-11T12:24:55Z")
I am currently migrating from elasticsearch 8.19.12 to 9.1.3. I fixed the issues in upgrade assistant in 8.19.12, created a snapshot which is valid (status = SUCCESS). But when i try to import the snapshot in 9.1.3 i ge… --- ## [Long-term snapshot compatibility across major versions (10+ year archive use case)](https://discuss.elastic.co/t/long-term-snapshot-compatibility-across-major-versions-10-year-archive-use-case/385068)
**Author:** [@jiriNovotny](https://discuss.elastic.co/u/jiriNovotny)\ **Replies:** 9\ **Last updated:** [February 16, 2026, 8:01pm UTC](https://discuss.elastic.co/t/long-term-snapshot-compatibility-across-major-versions-10-year-archive-use-case/385068 "2026-02-16T20:01:31Z")
Hello, I’m looking for clarification regarding the functionality described in the documentation about reading indices from older Elasticsearch versions: Currently, our process is as follows: We store indices as sna… --- ## [Corrupted S3 Repository: 1.3M Metadata lines & snapshot\_missing\_exception (Cluster size: 6.5 TB)](https://discuss.elastic.co/t/corrupted-s3-repository-1-3m-metadata-lines-snapshot-missing-exception-cluster-size-6-5-tb/384970)
**Author:** [@Disha\_Vala](https://discuss.elastic.co/u/Disha_Vala)\ **Replies:** 1\ **Last updated:** [February 9, 2026, 12:31pm UTC](https://discuss.elastic.co/t/corrupted-s3-repository-1-3m-metadata-lines-snapshot-missing-exception-cluster-size-6-5-tb/384970 "2026-02-09T12:31:41Z")
Hi Elastic Team, I am facing a repository corruption issue on Elasticsearch 8.5.3 and would appreciate guidance on how to perform a "surgical" repair of our snapshot metadata. The Situation: Cluster Scale: Our live cl… --- ## [Snapshot disaster recovery settings only](https://discuss.elastic.co/t/snapshot-disaster-recovery-settings-only/383589)
**Author:** [@juancamiloll](https://discuss.elastic.co/u/juancamiloll)\ **Replies:** 2\ **Last updated:** [November 21, 2025, 3:41pm UTC](https://discuss.elastic.co/t/snapshot-disaster-recovery-settings-only/383589 "2025-11-21T15:41:53Z")
Thanks to the valuable help of @leandrojmp I was able to successfully configure what was necessary to use the “Snapshot and restore” feature. I have another question: I don't have enough space for the snapshot to save… --- ## [Repository\_verification\_exception](https://discuss.elastic.co/t/repository-verification-exception/383588)
**Author:** [@juancamiloll](https://discuss.elastic.co/u/juancamiloll)\ **Replies:** 3\ **Last updated:** [November 21, 2025, 2:23pm UTC](https://discuss.elastic.co/t/repository-verification-exception/383588 "2025-11-21T14:23:43Z")
I am in the process of configuring the “Snapshot and restore” functionality. I have a cluster of 3 servers for Elasticsearch. From the available options, “Shared File System” has been selected. I took one of the se… --- ## [Persistent Reindex Failure from Source-Only Snapshot: unexpected docvalues type NONE for field '\_ignored' error](https://discuss.elastic.co/t/persistent-reindex-failure-from-source-only-snapshot-unexpected-docvalues-type-none-for-field-ignored-error/383178)
**Author:** [@Rizaldi\_Sanjaya](https://discuss.elastic.co/u/Rizaldi_Sanjaya)\ **Replies:** 2\ **Last updated:** [November 21, 2025, 4:14am UTC](https://discuss.elastic.co/t/persistent-reindex-failure-from-source-only-snapshot-unexpected-docvalues-type-none-for-field-ignored-error/383178 "2025-11-21T04:14:38Z")
Hello, I am attempting to restore a data stream from a source-only snapshot and then reindex it into a new, functional data stream, as required by the source-only documentation. The restore operation completes successf… --- ## [Migrate data to a new cluster with minimal interruption](https://discuss.elastic.co/t/migrate-data-to-a-new-cluster-with-minimal-interruption/383294)
**Author:** [@Ror](https://discuss.elastic.co/u/Ror)\ **Replies:** 7\ **Last updated:** [November 17, 2025, 11:04am UTC](https://discuss.elastic.co/t/migrate-data-to-a-new-cluster-with-minimal-interruption/383294 "2025-11-17T11:04:55Z")
Hi, I need to migrate multiple TB of data to a new cluster. Since this is production data, I’d like to avoid interruption as much as possible which can be tricky based on the volume of data. I have a simple infrastructu… --- ## [Migration Strategy (ES7 → ES8) via Dual‑Write + Snapshot Restore + Selective Merge by updated\_at](https://discuss.elastic.co/t/migration-strategy-es7-es8-via-dual-write-snapshot-restore-selective-merge-by-updated-at/383235)
**Author:** [@Aditya\_Rathi](https://discuss.elastic.co/u/Aditya_Rathi)\ **Replies:** 10\ **Last updated:** [November 5, 2025, 4:41pm UTC](https://discuss.elastic.co/t/migration-strategy-es7-es8-via-dual-write-snapshot-restore-selective-merge-by-updated-at/383235 "2025-11-05T16:41:51Z")
Environment / Versions: Source cluster: Elasticsearch 7.x ( live on production ) Target cluster: Elasticsearch 8.x Data volume: ~1 TB across ~100+ indices Write throughput: ~53 requests/sec, ~1,100 docs/sec (… --- ## [Elasticsearch snapshot to remote nas via nfs](https://discuss.elastic.co/t/elasticsearch-snapshot-to-remote-nas-via-nfs/382095)
**Author:** [@amine\_ghallab](https://discuss.elastic.co/u/amine_ghallab)\ **Replies:** 3\ **Last updated:** [October 30, 2025, 2:34pm UTC](https://discuss.elastic.co/t/elasticsearch-snapshot-to-remote-nas-via-nfs/382095 "2025-10-30T14:34:36Z")
Hello, I am running an Elasticsearch cluster on Kubernetes using the Elastic Cloud on Kubernetes (ECK) operator. Currently, my Elasticsearch data volume is reaching 80% usage, so I would like to configure a snapshot re… --- ## [Snapshot and Restore settings only](https://discuss.elastic.co/t/snapshot-and-restore-settings-only/382930)
**Author:** [@juancamiloll](https://discuss.elastic.co/u/juancamiloll)\ **Replies:** 1\ **Last updated:** [October 26, 2025, 5:53am UTC](https://discuss.elastic.co/t/snapshot-and-restore-settings-only/382930 "2025-10-26T05:53:40Z")
At the moment, I don't have the capacity to take a snapshot of the ingested data or the indexes as such. I'm sure that 100GB isn't enough to back up ingested data. But thinking about disaster recovery, I would like to h… --- ## [Peer Recovery does not respect indices.recovery.use\_snapshots=false or use\_for\_peer\_recovery=false - misleading documentation? (ES 8.13.4)](https://discuss.elastic.co/t/peer-recovery-does-not-respect-indices-recovery-use-snapshots-false-or-use-for-peer-recovery-false-misleading-documentation-es-8-13-4/382879)
**Author:** [@doitMLU](https://discuss.elastic.co/u/doitMLU)\ **Replies:** 5\ **Last updated:** [October 22, 2025, 4:18pm UTC](https://discuss.elastic.co/t/peer-recovery-does-not-respect-indices-recovery-use-snapshots-false-or-use-for-peer-recovery-false-misleading-documentation-es-8-13-4/382879 "2025-10-22T16:18:41Z")
Hi everyone, We recently had a big spike in S3 transfers and subsequently costs, which let me to troubleshoot the configuration of our elastic stack. I’ve found the cluster setting indices.recovery.use\_snapshots which d… --- ## [Running into "Request rate too high 503" S3 error during snapshots](https://discuss.elastic.co/t/running-into-request-rate-too-high-503-s3-error-during-snapshots/382062)
**Author:** [@indu\_s](https://discuss.elastic.co/u/indu_s)\ **Replies:** 1\ **Last updated:** [September 19, 2025, 7:22am UTC](https://discuss.elastic.co/t/running-into-request-rate-too-high-503-s3-error-during-snapshots/382062 "2025-09-19T07:22:28Z")
I’m running Elastic v8.8.2 on Kubernetes and sometimes, snapshots only partially succeed with error message AmazonS3Exception\\\[Please reduce your request rate. (Service: Amazon S3; Status Code: 503; Error Code: SlowDown;.… --- ## [Having issue to re run the snapshot](https://discuss.elastic.co/t/having-issue-to-re-run-the-snapshot/381723)
**Author:** [@Amirul\_Ento](https://discuss.elastic.co/u/Amirul_Ento)\ **Replies:** 1\ **Last updated:** [September 8, 2025, 9:09am UTC](https://discuss.elastic.co/t/having-issue-to-re-run-the-snapshot/381723 "2025-09-08T09:09:40Z")
Hi guys, I’m new to ELK. I got this issue recently. It actually is my mistake. I’m running a snapshot using elasticsearch curator where snapshot date based on range. Everything look normal since February until July. I… --- ## [Using the same snapshot repository for SLM and Frozen Tier](https://discuss.elastic.co/t/using-the-same-snapshot-repository-for-slm-and-frozen-tier/381345)
**Author:** [@gueguet57](https://discuss.elastic.co/u/gueguet57)\ **Replies:** 1\ **Last updated:** [August 27, 2025, 7:55am UTC](https://discuss.elastic.co/t/using-the-same-snapshot-repository-for-slm-and-frozen-tier/381345 "2025-08-27T07:55:30Z")
Hello all, In my Elastic setup (ECK), I’ve already created a snapshot repository that I use for the Frozen data tier and searchable snapshots. Now, I’d like to configure Snapshot Lifecycle Management (SLM) to automatic… --- ## [Shared File System - Repository Issues](https://discuss.elastic.co/t/shared-file-system-repository-issues/381136)
**Author:** [@Armindo77](https://discuss.elastic.co/u/Armindo77)\ **Replies:** 7\ **Last updated:** [August 20, 2025, 2:28pm UTC](https://discuss.elastic.co/t/shared-file-system-repository-issues/381136 "2025-08-20T14:28:31Z")
Hello, Hope you guys are doing well! During the last few years, we have been using the Snapshot & Restore feature, over a Shared File System via SMB, and everything seemed to work well. We did some restores earlier thi… --- ## [Copy ES snapshot to another ES](https://discuss.elastic.co/t/copy-es-snapshot-to-another-es/381045)
**Author:** [@Shahram](https://discuss.elastic.co/u/Shahram)\ **Replies:** 0\ **Last updated:** [August 14, 2025, 1:12pm UTC](https://discuss.elastic.co/t/copy-es-snapshot-to-another-es/381045 "2025-08-14T13:12:13Z")
Hello, I have 2 ES9.0.4 with exactily the same configuration and setup. In ES1: I created one index and put some dummy data as: get test/\_search { "took": 0, "timed\_out": false, "\_shards": { "total": 1, "successful"… --- ## [\[v8.17.6\] Azure Managed Identity Not Working – CredentialUnavailableException](https://discuss.elastic.co/t/v8-17-6-azure-managed-identity-not-working-credentialunavailableexception/380335)
**Author:** [@kshanuy](https://discuss.elastic.co/u/kshanuy)\ **Replies:** 3\ **Last updated:** [August 12, 2025, 2:05pm UTC](https://discuss.elastic.co/t/v8-17-6-azure-managed-identity-not-working-credentialunavailableexception/380335 "2025-08-12T14:05:49Z")
We are trying to use User Assigned Managed Identity (UAMI) for snapshot repository authentication on Elasticsearch v8.17.6 running on Azure Virtual Machines Scale Set (Windows VM). We followed the official docs: https… --- ## [Snapshot Recovery Results in Empty Index for Dense Vector Embeddings (v8.18.2)](https://discuss.elastic.co/t/snapshot-recovery-results-in-empty-index-for-dense-vector-embeddings-v8-18-2/380168)
**Author:** [@Khanh\_Chuong\_Le](https://discuss.elastic.co/u/Khanh_Chuong_Le)\ **Replies:** 1\ **Last updated:** [August 12, 2025, 1:33pm UTC](https://discuss.elastic.co/t/snapshot-recovery-results-in-empty-index-for-dense-vector-embeddings-v8-18-2/380168 "2025-08-12T13:33:02Z")
I am experiencing an issue with Elasticsearch version 8.18.2 on a self-managed setup. I've set up an index with vector embeddings, templated as dense vectors. The index contains thousands of documents and search operatio… --- ## [Indices with ILM policies are not included in Snapshot and Restore Operations](https://discuss.elastic.co/t/indices-with-ilm-policies-are-not-included-in-snapshot-and-restore-operations/380454)
**Author:** [@Rajesh\_Kannan](https://discuss.elastic.co/u/Rajesh_Kannan)\ **Replies:** 7\ **Last updated:** [August 8, 2025, 5:20am UTC](https://discuss.elastic.co/t/indices-with-ilm-policies-are-not-included-in-snapshot-and-restore-operations/380454 "2025-08-08T05:20:40Z")
There are approximately 4,000 indices in Elasticsearch, all of which are in an open state. However, during the scheduled backup, only 1,660 indices were successfully backed up, while the remaining ones were ignored. Upon… --- ## [Optimizing Elasticsearch Snapshot Performance to S3-Compatible Object Storage](https://discuss.elastic.co/t/optimizing-elasticsearch-snapshot-performance-to-s3-compatible-object-storage/380461)
**Author:** [@Dipayan](https://discuss.elastic.co/u/Dipayan)\ **Replies:** 3\ **Last updated:** [July 29, 2025, 10:19pm UTC](https://discuss.elastic.co/t/optimizing-elasticsearch-snapshot-performance-to-s3-compatible-object-storage/380461 "2025-07-29T22:19:45Z")
Hello, I’m currently conducting performance testing for Elasticsearch snapshots targeting an S3-compatible object storage system. System Configuration: Elasticsearch Cluster: 2 nodes (master + data) CPU: 8 cores RAM: … --- ## [File system repository returning error](https://discuss.elastic.co/t/file-system-repository-returning-error/379330)
**Author:** [@JSElasticDiscuss](https://discuss.elastic.co/u/JSElasticDiscuss)\ **Replies:** 3\ **Last updated:** [June 27, 2025, 8:57am UTC](https://discuss.elastic.co/t/file-system-repository-returning-error/379330 "2025-06-27T08:57:42Z")
Hello, I have confirmed a valid path in my path.repo setting, but now when I do a 'verify repository' it gives me an error: { "name": "ResponseError", "message": "repository\_verification\_exception\\n\\tCaused by:\\n\\t… --- ## [S3 Repo verification exception (Failed to connect to service endpoint)](https://discuss.elastic.co/t/s3-repo-verification-exception-failed-to-connect-to-service-endpoint/379244)
**Author:** [@staubt](https://discuss.elastic.co/u/staubt)\ **Replies:** 5\ **Last updated:** [June 18, 2025, 8:09am UTC](https://discuss.elastic.co/t/s3-repo-verification-exception-failed-to-connect-to-service-endpoint/379244 "2025-06-18T08:09:29Z")
Hello I'm using snapshotting for backup/restore. There I recreate each time the repository since the location in S3 can change. For the authentication I use two different clients "backup" and "restore". At the moment … --- ## [Backup repository sizes - snapshot repository v. disk space use; why the difference?](https://discuss.elastic.co/t/backup-repository-sizes-snapshot-repository-v-disk-space-use-why-the-difference/378716)
**Author:** [@kmp](https://discuss.elastic.co/u/kmp)\ **Replies:** 3\ **Last updated:** [May 30, 2025, 3:57pm UTC](https://discuss.elastic.co/t/backup-repository-sizes-snapshot-repository-v-disk-space-use-why-the-difference/378716 "2025-05-30T15:57:18Z")
I'm curious whether anyone knows what the underlying mechanism is causing this... My (small) environment has replication across multiple nodes in the cluster, so snapshotting isn't something that's seemed important for … [Next page](https://discuss.elastic.co/tag/snapshot-and-restore/89.md?match_all_tags=true&page=1&tags%5B%5D=snapshot-and-restore)