# Not able to take snapshot

**URL:** <https://discuss.elastic.co/t/not-able-to-take-snapshot/25208>\
**Category:** Elasticsearch\
**Created:** [July 9, 2015, 6:29am UTC](https://discuss.elastic.co/t/not-able-to-take-snapshot/25208 "2015-07-09T06:29:19Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [July 9, 2015, 4:06pm UTC](https://discuss.elastic.co/t/not-able-to-take-snapshot/25208/8 "2015-07-09T16:06:08Z")

</div>

> [@Alessandro\_Piroddi\_A](#):
>
> 2015-07-09 17:42:52,594 ERROR Failed to verify all nodes have repository access.

This message indicates that not all nodes in your cluster have write access to the repository, and that is why Curator fails to make the snapshot. Curator performs a repository availability check before attempting a backup as a safety check.

If you are 100% certain that this message is in error (and it shouldn't be with a regular fs repository--occasionally s3 and azure repos are slower to respond so they give a false-negative), upgrade to Curator 3.2.0 and use the [--skip-repo-validation](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/skip-repo-validation.html) flag.

---

_[View the full topic](https://discuss.elastic.co/t/not-able-to-take-snapshot/25208)._