# Elasticsearch: What's the best way to store big-data cost effective

**URL:** <https://discuss.elastic.co/t/elasticsearch-whats-the-best-way-to-store-big-data-cost-effective/350289>\
**Category:** Elasticsearch\
**Created:** [January 3, 2024, 9:03am UTC](https://discuss.elastic.co/t/elasticsearch-whats-the-best-way-to-store-big-data-cost-effective/350289 "2024-01-03T09:03:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![basiltitus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/basiltitus/32/132851_2.png) [@basiltitus](https://discuss.elastic.co/u/basiltitus)\
**Post date:** [January 3, 2024, 9:03am UTC](https://discuss.elastic.co/t/elasticsearch-whats-the-best-way-to-store-big-data-cost-effective/350289/1 "2024-01-03T09:03:43Z")

</div>

We are using **Basic Elasticsearch v7.4** on a single node with nearly 2TB of data. We planning to increase our retention however we are constrained by it's storage capacity. While adding disks and using **multiple data path** is a choice is not a recommended one or else needs to use **LVM** which I found quite troublesome.

We are considering **Data Tier** and adding new nodes in different tier like ' **cold**' or ' **frozen**'. Is this the best method to achieve this ? I have tested cold tier but does this version of ES support frozen tier? We are not expecting the same search performance for very old data as recently created indices do. Is HDDs best option for node in these tiers to save cost? Is heap memory still a performance factor in these tiers?

What are some alternatives to storing big-data is ES if there is any?

---

<div class="post-metadata">

**Author:** ![grumo35](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grumo35/32/59451_2.png) [@grumo35](https://discuss.elastic.co/u/grumo35)\
**Post date:** [January 3, 2024, 9:26am UTC](https://discuss.elastic.co/t/elasticsearch-whats-the-best-way-to-store-big-data-cost-effective/350289/2 "2024-01-03T09:26:06Z")

</div>

Hello,

The data tiering depends also on your querying, do you have a notion of time or age in your data ?

You could think about frozen and or cold indices if you dont need to acess the data on a regular bassis.

Data tiering is effective way to increase elastic storage capacity based on the fact that you might need to query only last 7 days and 1 time a year the frozen data.

Why would LVM save you any kind of space or increase storage effectiveness ?

Also if you're using enterprise grade storage solutions you should look into storage deduplication technology on your storage hardware it's actually insane how much data this can save you can go as high as 60%+ on some datasets.

---

<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:** [January 31, 2024, 9:26am UTC](https://discuss.elastic.co/t/elasticsearch-whats-the-best-way-to-store-big-data-cost-effective/350289/3 "2024-01-31T09:26:42Z")

</div>

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