# Netapp & elasticsearch?

**URL:** <https://discuss.elastic.co/t/netapp-elasticsearch/390020>\
**Category:** Elasticsearch\
**Created:** [August 31, 2026, 8:43am UTC](https://discuss.elastic.co/t/netapp-elasticsearch/390020 "2026-08-31T08:43:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![smm](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@smm](https://discuss.elastic.co/u/smm)\
**Post date:** [August 31, 2026, 8:43am UTC](https://discuss.elastic.co/t/netapp-elasticsearch/390020/1 "2026-08-31T08:43:32Z")

</div>

I would like to run an Elastic stack on VMware VMs. These VMs should run on NetApp via iSCSI/FC with XFS. It is a good or a bad idea? Does it work as good as local storage?

Any input, shared story / experience about this would be great!  
Many thanks.

---

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [August 31, 2026, 12:24pm UTC](https://discuss.elastic.co/t/netapp-elasticsearch/390020/2 "2026-08-31T12:24:15Z")

</div>

The recommendation is to use local SSD/NVMe/fast storage. NetApp is not local storage.

I’m a fan of NetApp but it’s “horses for courses” and IMO NetApp is not the best fit for _most_ Elastic use cases.

I recall answering on [this](https://discuss.elastic.co/t/high-sustained-read-traffic-from-elasticsearch-hot-pods/385508) thread:

and though it was never really clear exactly what the issue was there, the network attached storage didn’t help troubleshooting and obviously limits performance.

---

<div class="post-metadata">

**Author:** ![smm](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@smm](https://discuss.elastic.co/u/smm)\
**Post date:** [September 1, 2026, 4:47am UTC](https://discuss.elastic.co/t/netapp-elasticsearch/390020/3 "2026-09-01T04:47:01Z")

</div>

Thank you Kevin for your insight!  
kind regards  
Stefano