# Hot, Warm Setup Storage Based
**URL:** https://discuss.elastic.co/t/hot-warm-setup-storage-based/202974
**Category:** Elasticsearch
**Created:** [October 10, 2019, 8:17am UTC](https://discuss.elastic.co/t/hot-warm-setup-storage-based/202974 "2019-10-10T08:17:09Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@tomx1](https://discuss.elastic.co/u/tomx1)
#### Post date: [October 10, 2019, 8:17am UTC](https://discuss.elastic.co/t/hot-warm-setup-storage-based/202974/1 "2019-10-10T08:17:09Z")
Hey,
we are planning to setup a new cluster with 5 hardware servers. Each server will use a 2TB PCIe SSD and ~10TB of SAS Storage. We are collecting logs and timeseries. After a few days data should be moved to the SAS storage... I wonder if this is possible without having to setup an explicit Elasticsearch instance / node (as VM or via Docker). So my idea is not to have hot and warm nodes but having hot and warm storage managed by a single Elasticsearch node.
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [October 10, 2019, 8:22am UTC](https://discuss.elastic.co/t/hot-warm-setup-storage-based/202974/2 "2019-10-10T08:22:25Z")
You cannot really control the allocation of shards within a single node. It's best to set up distinct nodes for each storage class and then use [allocation filtering](https://www.elastic.co/guide/en/elasticsearch/reference/current/allocation-filtering.html) (or [ILM](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html)) to move shards from one class to another. Note that you can run multiple nodes on the same VM.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 7, 2019, 8:22am UTC](https://discuss.elastic.co/t/hot-warm-setup-storage-based/202974/3 "2019-11-07T08:22:25Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.