# Best practices for validating elasticsearch snapshots **URL:** \ **Category:** Elasticsearch\ **Created:** [September 10, 2020, 9:54pm UTC](https://discuss.elastic.co/t/best-practices-for-validating-elasticsearch-snapshots/248240 "2020-09-10T21:54:11Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![proton](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@proton](https://discuss.elastic.co/u/proton)\ **Post date:** [September 10, 2020, 9:54pm UTC](https://discuss.elastic.co/t/best-practices-for-validating-elasticsearch-snapshots/248240/1 "2020-09-10T21:54:12Z")
We used verify the snapshots on daily bases to make sure they are in good state i.e has no corrupted data. We do this by spinning up a new cluster and restoring it to validate the we have at least one good snapshot. However, as the data grows this becomes increasing complex - we have grown to 100+ nodes and 120+ TB of data - restoring one snapshot can take up to 15 hours and we need to spin up another production size cluster with 100 nodes for just validating a snapshot. We can move the validation to weekly/bi-weekly but wondering if there are better approaches to validating than spinning up prod size cluster. I was looking forward to this but the issue is now closed: [Validate snapshot via dry-run restore](https://github.com/elastic/elasticsearch/issues/11083). Is there anything similar that exists? Based on what i've read elastic has a checksum "check" at each snapshot but recently we still had a corrupted index and hence would like to do this additional validation. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 8, 2020, 9:54pm UTC](https://discuss.elastic.co/t/best-practices-for-validating-elasticsearch-snapshots/248240/2 "2020-10-08T21:54:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.