# Backing up elasticsearch using open source dump tool or official snapshot **URL:** \ **Category:** Elasticsearch\ **Created:** [February 11, 2018, 2:51pm UTC](https://discuss.elastic.co/t/backing-up-elasticsearch-using-open-source-dump-tool-or-official-snapshot/119378 "2018-02-11T14:51:51Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![digirave](https://avatars.discourse-cdn.com/v4/letter/d/85e7bf/32.png) [@digirave](https://discuss.elastic.co/u/digirave)\ **Post date:** [February 11, 2018, 2:51pm UTC](https://discuss.elastic.co/t/backing-up-elasticsearch-using-open-source-dump-tool-or-official-snapshot/119378/1 "2018-02-11T14:51:51Z")
I am reviewing two options for backing up elasticsearch right now. 1. Unofficial dump tool > **[taskrabbit/elasticsearch-dump](https://github.com/taskrabbit/elasticsearch-dump)** > > elasticsearch-dump - Import and export tools for elasticsearch Seems real easy to use. 1. Official snapshot [https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html) Seems not that hard to use, but will probably have to setup a nfs in our case. I am curious whether anyone has experience in using the open source dump tool mentioned above. Would it lock the database so the data is in a safe state, point-in-time view state? What tool would you recommend for a light small cluster? Thank you. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 11, 2018, 2:51pm UTC](https://discuss.elastic.co/t/backing-up-elasticsearch-using-open-source-dump-tool-or-official-snapshot/119378/2 "2018-03-11T14:51:53Z")
Closed on March 11, 2018, 2:51pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.