<?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: What needs to be setup for Disaster Recovery search head? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/What-needs-to-be-setup-for-Disaster-Recovery-search-head/m-p/226932#M8523</link>
    <description>&lt;P&gt;Hi ankithreddy777, &lt;/P&gt;

&lt;P&gt;I think you can just deploy search head clustering for HA (high availability) and DR (disaster recovery). &lt;BR /&gt;
For information about the search head clustering architecture, please refer to documentation: &lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.1/DistSearch/SHCarchitecture"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.1/DistSearch/SHCarchitecture&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Hope this helps, thanks!&lt;BR /&gt;
Hunter&lt;/P&gt;</description>
    <pubDate>Wed, 11 Jan 2017 17:27:05 GMT</pubDate>
    <dc:creator>hunters_splunk</dc:creator>
    <dc:date>2017-01-11T17:27:05Z</dc:date>
    <item>
      <title>What needs to be setup for Disaster Recovery search head?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/What-needs-to-be-setup-for-Disaster-Recovery-search-head/m-p/226931#M8522</link>
      <description>&lt;P&gt;I have to set one search head at a primary data centre and another at a DR (Disaster Recovery) data centre.  What things need to be setup for DR search head that replicates original search head and can be used immediately during Disaster Recovery?&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2017 16:55:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/What-needs-to-be-setup-for-Disaster-Recovery-search-head/m-p/226931#M8522</guid>
      <dc:creator>ankithreddy777</dc:creator>
      <dc:date>2017-01-11T16:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: What needs to be setup for Disaster Recovery search head?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/What-needs-to-be-setup-for-Disaster-Recovery-search-head/m-p/226932#M8523</link>
      <description>&lt;P&gt;Hi ankithreddy777, &lt;/P&gt;

&lt;P&gt;I think you can just deploy search head clustering for HA (high availability) and DR (disaster recovery). &lt;BR /&gt;
For information about the search head clustering architecture, please refer to documentation: &lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.1/DistSearch/SHCarchitecture"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.1/DistSearch/SHCarchitecture&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Hope this helps, thanks!&lt;BR /&gt;
Hunter&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2017 17:27:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/What-needs-to-be-setup-for-Disaster-Recovery-search-head/m-p/226932#M8523</guid>
      <dc:creator>hunters_splunk</dc:creator>
      <dc:date>2017-01-11T17:27:05Z</dc:date>
    </item>
    <item>
      <title>Re: What needs to be setup for Disaster Recovery search head?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/What-needs-to-be-setup-for-Disaster-Recovery-search-head/m-p/226933#M8524</link>
      <description>&lt;P&gt;@ankithreddy777 - Did the answer provided by hunters help provide a solution to your question? If yes, please don't forget to resolve this post by clicking "Accept". If no, please leave a comment with more feedback. Thanks!&lt;/P&gt;</description>
      <pubDate>Sun, 22 Jan 2017 03:26:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/What-needs-to-be-setup-for-Disaster-Recovery-search-head/m-p/226933#M8524</guid>
      <dc:creator>aaraneta_splunk</dc:creator>
      <dc:date>2017-01-22T03:26:38Z</dc:date>
    </item>
  </channel>
</rss>

