# Big data on the one server without cluster

**URL:** <https://discuss.elastic.co/t/big-data-on-the-one-server-without-cluster/348512>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [December 3, 2023, 10:26pm UTC](https://discuss.elastic.co/t/big-data-on-the-one-server-without-cluster/348512 "2023-12-03T22:26:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![habajol675](https://avatars.discourse-cdn.com/v4/letter/h/71c47a/32.png) [@habajol675](https://discuss.elastic.co/u/habajol675)\
**Post date:** [December 3, 2023, 10:26pm UTC](https://discuss.elastic.co/t/big-data-on-the-one-server-without-cluster/348512/1 "2023-12-03T22:26:18Z")

</div>

Hello everyone, I am currently studying the work of elastic and plan to transfer the search to elastic. I'm calculating how much space my database will take up and realized that I need several disks. My database will weigh approximately 10-12 terabytes, at the moment I am using the built-in database solution, but I am no longer satisfied with the quality of the results and search settings. I read that elastic supported path.data with the ability to add new disks, but this is now marked obsolete. I have a very nice server with 1TB of RAM and about 100TB of storage, totaling 8TB each. The question is, how can I configure the division of indexes on several disks without using Docker or other virtualization and clustering tools? Can I do this if I only have 1 elastic node?  
A small clarification, everything I use works on Windows and I also plan to install elastic on this system without docker and elastic cluster.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [December 3, 2023, 11:18pm UTC](https://discuss.elastic.co/t/big-data-on-the-one-server-without-cluster/348512/2 "2023-12-03T23:18:50Z")

</div>

Hi @habajol675

Well I think you are kind of answering your own question.

Most of us with such a nice server would run a couple nodes like 3 nodes with separate data paths... 1 node would probably not be as performant, and flexible etc etc.

But that said per the docs [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/important-settings.html#_multiple_data_paths)

> As an alternative to multiple data paths, you can create a filesystem which spans multiple disks with a hardware virtualisation layer such as RAID, or a software virtualisation layer such as Logical Volume Manager (LVM) on Linux or Storage Spaces on Windows. If you wish to use multiple data paths on a single machine then you must run one node for each data path.

Curious why you don't want to use virtualization / Docker, 1 compose file and you could have 3 nodes running very easily...

You Could also probably multiple nodes on bare metal but that would require more work for sure

---

<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:** [December 31, 2023, 11:19pm UTC](https://discuss.elastic.co/t/big-data-on-the-one-server-without-cluster/348512/3 "2023-12-31T23:19:50Z")

</div>

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