<?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 Splunk Replication a Good BCP Alternative? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Replication-a-Good-BCP-Alternative/m-p/102304#M3785</link>
    <description>&lt;P&gt;We have been working with our architects to determine the most appropriate solution for BCP. Does Splunk replicate non processed information such as dashboards, users etc.? Is it a viable solution for running a BCP instance of Splunk?&lt;/P&gt;</description>
    <pubDate>Wed, 16 Oct 2013 19:33:36 GMT</pubDate>
    <dc:creator>andrewkenth</dc:creator>
    <dc:date>2013-10-16T19:33:36Z</dc:date>
    <item>
      <title>Splunk Replication a Good BCP Alternative?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Replication-a-Good-BCP-Alternative/m-p/102304#M3785</link>
      <description>&lt;P&gt;We have been working with our architects to determine the most appropriate solution for BCP. Does Splunk replicate non processed information such as dashboards, users etc.? Is it a viable solution for running a BCP instance of Splunk?&lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2013 19:33:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Replication-a-Good-BCP-Alternative/m-p/102304#M3785</guid>
      <dc:creator>andrewkenth</dc:creator>
      <dc:date>2013-10-16T19:33:36Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Replication a Good BCP Alternative?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Replication-a-Good-BCP-Alternative/m-p/102305#M3786</link>
      <description>&lt;P&gt;Splunk clustering / index replication does not replicate any search head configuration or knowledge objects like views, lookup tables, etc.  It only replicates the actual indexed data across peer indexers.&lt;/P&gt;

&lt;P&gt;As of current version (6.0) there is still a SPOF in the cluster master - you would need to find some way to make it highly available as well.&lt;/P&gt;

&lt;P&gt;You could deal with the search head data using Search Head pooling, but would need a way to make the NFS highly available.  You might be able to use rsync or something like it to keep a secondary search head configured identically without doing pooling.&lt;/P&gt;

&lt;P&gt;Another gotcha is that clustering has no concept of locality / affinity / topology.  That is, if you have 4 "primary" indexers and 4 "DR" indexers then you need a minimum replication factor of 5 to be sure there is at least one copy of each bucket at the DR site.  &lt;/P&gt;

&lt;P&gt;You will also need substantial bandwidth with very low latency between the primary site and the DR site.  &lt;/P&gt;

&lt;P&gt;You would need something like &lt;CODE&gt;(indexer_throughput * number_of_indexers * (replicationfactor - 1))&lt;/CODE&gt; bandwith available for Splunk.  In the 8 indexer example above with an RF=5, each of 4 indexers at the primary site will be replicating 4 copies of their data to other indexers.  In a worst-case scenario (from a bandwidth perspective), all 4 replicated copies will be to the DR site.  So, if each indexer is processing 500 KBytes/sec of data to be indexed - then 4 indexers, each sending 4 copies of their 500 KBytes/sec data across the WAN to the DR site, will result in 8,000KBytes/sec of total WAN bandwidth needed.&lt;/P&gt;

&lt;P&gt;So there are definitely caveats but it is viable.  I would strongly suggest discussing your planned deployment with a Splunk Architect or Professional Services.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Oct 2013 17:15:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Splunk-Replication-a-Good-BCP-Alternative/m-p/102305#M3786</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2013-10-17T17:15:35Z</dc:date>
    </item>
  </channel>
</rss>

