# How to manage storage and purging elasticsearch

**URL:** <https://discuss.elastic.co/t/how-to-manage-storage-and-purging-elasticsearch/203171>\
**Category:** Elasticsearch\
**Created:** [October 11, 2019, 7:30am UTC](https://discuss.elastic.co/t/how-to-manage-storage-and-purging-elasticsearch/203171 "2019-10-11T07:30:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cuaralan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cuaralan/32/55756_2.png) [@cuaralan](https://discuss.elastic.co/u/cuaralan)\
**Post date:** [October 11, 2019, 7:30am UTC](https://discuss.elastic.co/t/how-to-manage-storage-and-purging-elasticsearch/203171/1 "2019-10-11T07:30:23Z")

</div>

Hello,  
I am new to the forum although I have been working with ELK for a while now. I have done several tests and we are already thinking about implementing a real solution, but my bosses have had some doubts about how ElasticSearch manages the enormous amount of information that it raises.

How do you manage the storage of such heavy logs?  
Does it allow historification?  
Does it allow definition of periodic erase policies, use of secondary storage, etc.?

Thank you very much for your help

---

<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 8, 2019, 7:30am UTC](https://discuss.elastic.co/t/how-to-manage-storage-and-purging-elasticsearch/203171/2 "2019-11-08T07:30:29Z")

</div>

Closed on November 8, 2019, 7:30am UTC

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