# Source Nakisa Database refreshed

**URL:** <https://discuss.elastic.co/t/source-nakisa-database-refreshed/154251>\
**Category:** Elasticsearch\
**Created:** [October 26, 2018, 7:23pm UTC](https://discuss.elastic.co/t/source-nakisa-database-refreshed/154251 "2018-10-26T19:23:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Doug.Meyer](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@Doug.Meyer](https://discuss.elastic.co/u/Doug.Meyer)\
**Post date:** [October 26, 2018, 7:23pm UTC](https://discuss.elastic.co/t/source-nakisa-database-refreshed/154251/1 "2018-10-26T19:23:50Z")

</div>

We are implementing the Nakisa Licensing application which uses ElasticSearch. The developers encountered an issue that led to the restore of the database from a time before the problem. As this is new to us I do not believe there are ElasticSearch snapshots to revert back to. I am looking for a procedure to do a full reload of the indexes.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 27, 2018, 12:43am UTC](https://discuss.elastic.co/t/source-nakisa-database-refreshed/154251/2 "2018-10-27T00:43:00Z")

</div>

I think you would need to chat to the software vendor that integrates into Elasticsearch to ask how to do this.

Without snapshots, that application is the only potential source of the data.

---

<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:** [November 24, 2018, 12:43am UTC](https://discuss.elastic.co/t/source-nakisa-database-refreshed/154251/3 "2018-11-24T00:43:00Z")

</div>

Closed on November 24, 2018, 12:43am UTC

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