# Elastic Search Setup Requirements?

**URL:** <https://discuss.elastic.co/t/elastic-search-setup-requirements/76051>\
**Category:** Elasticsearch\
**Created:** [February 22, 2017, 2:22pm UTC](https://discuss.elastic.co/t/elastic-search-setup-requirements/76051 "2017-02-22T14:22:42Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![esanchez](https://avatars.discourse-cdn.com/v4/letter/e/71e660/32.png) [@esanchez](https://discuss.elastic.co/u/esanchez)\
**Post date:** [February 22, 2017, 2:22pm UTC](https://discuss.elastic.co/t/elastic-search-setup-requirements/76051/1 "2017-02-22T14:22:43Z")

</div>

Hello everyone,

I have been trying to search around here for whats needed in order to run Elastic search properly. I wanted to use windows server 2012 r2 64 bit with 2 disks with 100 GB. For those of you who have this setup already can you please guide me and tell me what you think.

Thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 24, 2017, 10:12am UTC](https://discuss.elastic.co/t/elastic-search-setup-requirements/76051/2 "2017-02-24T10:12:13Z")

</div>

Run it to do what?

---

<div class="post-metadata">

**Author:** ![esanchez](https://avatars.discourse-cdn.com/v4/letter/e/71e660/32.png) [@esanchez](https://discuss.elastic.co/u/esanchez)\
**Post date:** [February 28, 2017, 2:30pm UTC](https://discuss.elastic.co/t/elastic-search-setup-requirements/76051/3 "2017-02-28T14:30:14Z")

</div>

its our first venture using elastic search, we are looking to collect syslog files from 50 to 60 wireless controllers. I am thinking of setting up 2 thin provisioned disks at 100GB each. Do you think that should be fine ? Thank you for your response I appreciate your help.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 28, 2017, 7:41pm UTC](https://discuss.elastic.co/t/elastic-search-setup-requirements/76051/4 "2017-02-28T19:41:20Z")

</div>

Depends on how large the data is from these controllers and how long you want to keep it for./

---

<div class="post-metadata">

**Author:** ![esanchez](https://avatars.discourse-cdn.com/v4/letter/e/71e660/32.png) [@esanchez](https://discuss.elastic.co/u/esanchez)\
**Post date:** [March 1, 2017, 3:54pm UTC](https://discuss.elastic.co/t/elastic-search-setup-requirements/76051/5 "2017-03-01T15:54:20Z")

</div>

I am not sure how large the data would be but we would like to retain about a month's worth of the data. Any guideline would be helpful. I understand that every environment scenario.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 1, 2017, 11:10pm UTC](https://discuss.elastic.co/t/elastic-search-setup-requirements/76051/6 "2017-03-01T23:10:58Z")

</div>

Well if you don't know how much data there is it's impossible to say if this will work.  
You might just need to start up a cluster, push data to it, and then figure it out.

---

<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:** [March 29, 2017, 11:11pm UTC](https://discuss.elastic.co/t/elastic-search-setup-requirements/76051/7 "2017-03-29T23:11:22Z")

</div>

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