# Taking the snapshot of elasticDB

**URL:** <https://discuss.elastic.co/t/taking-the-snapshot-of-elasticdb/173759>\
**Category:** Elasticsearch\
**Created:** [March 25, 2019, 1:21pm UTC](https://discuss.elastic.co/t/taking-the-snapshot-of-elasticdb/173759 "2019-03-25T13:21:20Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chandan\_Kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandan_kumar/32/42704_2.png) [@Chandan\_Kumar](https://discuss.elastic.co/u/Chandan_Kumar)\
**Post date:** [March 25, 2019, 1:21pm UTC](https://discuss.elastic.co/t/taking-the-snapshot-of-elasticdb/173759/1 "2019-03-25T13:21:20Z")

</div>

Is there a way to quiesce the elasticDB, before taking any snapshots at storage level?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [March 25, 2019, 1:30pm UTC](https://discuss.elastic.co/t/taking-the-snapshot-of-elasticdb/173759/2 "2019-03-25T13:30:09Z")

</div>

Hey,

it's Elasticsearch, not DB 🙂

Can you explain what you want to achieve that is not possible with the [Snapshot/Restore API](https://www.elastic.co/guide/en/elasticsearch/reference/6.6/modules-snapshots.html) - which works perfectly fine while indexing and searching at the same time?

--Alex

---

<div class="post-metadata">

**Author:** ![Chandan\_Kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandan_kumar/32/42704_2.png) [@Chandan\_Kumar](https://discuss.elastic.co/u/Chandan_Kumar)\
**Post date:** [March 25, 2019, 1:50pm UTC](https://discuss.elastic.co/t/taking-the-snapshot-of-elasticdb/173759/3 "2019-03-25T13:50:53Z")

</div>

Okay! Thanks for help

Just trying to find out the way for taking the storage level snapshot using kubernetes volume-snapshot feature in Elasticsearch, like in mysql before taking the storage level snapshot we have to flush the table and take the read lock.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [March 25, 2019, 2:00pm UTC](https://discuss.elastic.co/t/taking-the-snapshot-of-elasticdb/173759/4 "2019-03-25T14:00:02Z")

</div>

I don't recommend using anything other than snapshot/restore for taking snapshots. It is hard to get right in a distributed system (flush everything, disable indexing, ensure no merges happen before taking the snapshot) to trigger such a storage level snapshot, which was the reason to come up with snapshot/restore in the first place.

---

<div class="post-metadata">

**Author:** ![Chandan\_Kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandan_kumar/32/42704_2.png) [@Chandan\_Kumar](https://discuss.elastic.co/u/Chandan_Kumar)\
**Post date:** [March 25, 2019, 2:01pm UTC](https://discuss.elastic.co/t/taking-the-snapshot-of-elasticdb/173759/5 "2019-03-25T14:01:22Z")

</div>

Okay! Thanks @spinscale 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 22, 2019, 2:01pm UTC](https://discuss.elastic.co/t/taking-the-snapshot-of-elasticdb/173759/6 "2019-04-22T14:01:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.