<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Splunk Standalone High availability setup required servers. in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Standalone-High-availability-setup-required-servers/m-p/692107#M28331</link>
    <description>&lt;P&gt;Honestly - I have no idea what those tables are supposed to represent.&lt;/P&gt;&lt;P&gt;I understand that there are two separate "zones" and you have some servers in them. How many servers and what roles do they have? Is there any connectivity between those zones or are they completely air-gapped? If so then how do you handle licensing?&lt;/P&gt;&lt;P&gt;What do you mean by "implement high availability"? On which layer? Architecting an environment from scratch is usually a relatively big and important task so while this forum is a good place for asking general architecture-related questions it's not a replacement for the work of properly trained Splunk Pre-sales team or Splunk Partner engineers.&lt;/P&gt;</description>
    <pubDate>Mon, 01 Jul 2024 14:19:33 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2024-07-01T14:19:33Z</dc:date>
    <item>
      <title>Splunk Standalone High availability setup required servers.</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Standalone-High-availability-setup-required-servers/m-p/692085#M28330</link>
      <description>&lt;P&gt;Hi team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently we are implemented the Standalone below servers,&lt;/P&gt;&lt;P&gt;Zone-1&lt;/P&gt;&lt;TABLE width="665"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="117"&gt;&lt;P&gt;Environment&lt;/P&gt;&lt;/TD&gt;&lt;TD width="235"&gt;&lt;P&gt;Server Name&lt;/P&gt;&lt;/TD&gt;&lt;TD width="160"&gt;&lt;P&gt;IP&lt;/P&gt;&lt;/TD&gt;&lt;TD width="153"&gt;&lt;P&gt;Splunk Role&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="117"&gt;&lt;P&gt;DEV&lt;/P&gt;&lt;/TD&gt;&lt;TD width="65"&gt;&lt;P&gt;L4&lt;/P&gt;&lt;/TD&gt;&lt;TD width="170"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD width="160"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD width="153"&gt;&lt;P&gt;Search Head+ Indexer&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="117"&gt;&lt;P&gt;QA&lt;/P&gt;&lt;/TD&gt;&lt;TD width="65"&gt;&lt;P&gt;L4&lt;/P&gt;&lt;/TD&gt;&lt;TD width="170"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD width="160"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD width="153"&gt;&lt;P&gt;Search Head + Indexer&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="65"&gt;&lt;P&gt;L4&lt;/P&gt;&lt;/TD&gt;&lt;TD width="170"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD width="160"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD width="153"&gt;&lt;P&gt;Deployment Server&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE width="695px"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="102.969px"&gt;&lt;P&gt;&lt;STRONG&gt;Zone-2&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD width="57.934px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD width="236.493px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD width="98.8368px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD width="197.656px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="102.969px"&gt;&lt;P&gt;Environment&lt;/P&gt;&lt;/TD&gt;&lt;TD width="294.427px"&gt;&lt;P&gt;Server Name&lt;/P&gt;&lt;/TD&gt;&lt;TD width="98.8368px"&gt;&lt;P&gt;IP&lt;/P&gt;&lt;/TD&gt;&lt;TD width="197.656px"&gt;&lt;P&gt;Splunk Role&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="102.969px"&gt;&lt;P&gt;DEV&lt;/P&gt;&lt;/TD&gt;&lt;TD width="57.934px"&gt;&lt;P&gt;L4&lt;/P&gt;&lt;/TD&gt;&lt;TD width="236.493px"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD width="98.8368px"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD width="197.656px"&gt;&lt;P&gt;Search Head + Indexer&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="102.969px"&gt;&lt;P&gt;QA&lt;/P&gt;&lt;/TD&gt;&lt;TD width="57.934px"&gt;&lt;P&gt;L4&lt;/P&gt;&lt;/TD&gt;&lt;TD width="236.493px"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD width="98.8368px"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD width="197.656px"&gt;&lt;P&gt;Search Head + Indexer&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In our environment, only 2 Indexer + Search head server is there on the same instance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How to Implement the High Availability Servers?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;please help me the process.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2024 12:43:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Standalone-High-availability-setup-required-servers/m-p/692085#M28330</guid>
      <dc:creator>vijreddy30</dc:creator>
      <dc:date>2024-07-01T12:43:17Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Standalone High availability setup required servers.</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Standalone-High-availability-setup-required-servers/m-p/692107#M28331</link>
      <description>&lt;P&gt;Honestly - I have no idea what those tables are supposed to represent.&lt;/P&gt;&lt;P&gt;I understand that there are two separate "zones" and you have some servers in them. How many servers and what roles do they have? Is there any connectivity between those zones or are they completely air-gapped? If so then how do you handle licensing?&lt;/P&gt;&lt;P&gt;What do you mean by "implement high availability"? On which layer? Architecting an environment from scratch is usually a relatively big and important task so while this forum is a good place for asking general architecture-related questions it's not a replacement for the work of properly trained Splunk Pre-sales team or Splunk Partner engineers.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2024 14:19:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Standalone-High-availability-setup-required-servers/m-p/692107#M28331</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-07-01T14:19:33Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Standalone High availability setup required servers.</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Standalone-High-availability-setup-required-servers/m-p/692138#M28332</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/240303"&gt;@vijreddy30&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;see in the Splunk Validated Architectures document (&lt;A href="https://www.splunk.com/en_us/pdfs/tech-brief/splunk-validated-architectures.pdf" target="_blank"&gt;https://www.splunk.com/en_us/pdfs/tech-brief/splunk-validated-architectures.pdf&lt;/A&gt;) what Splunk means for HA and how to implement it.&lt;/P&gt;&lt;P&gt;For your requirements, it's really difficoult to answer to your question!&lt;/P&gt;&lt;P&gt;Maybe there are some replication mechanisms, based on VM-Ware, to do this, but I'm not an expert on VM-Ware and this isn't the location for this question.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2024 16:21:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Standalone-High-availability-setup-required-servers/m-p/692138#M28332</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-07-01T16:21:53Z</dc:date>
    </item>
  </channel>
</rss>

