<?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: Indexing question on a heavy forwarder in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-question-on-a-heavy-forwarder/m-p/91527#M19034</link>
    <description>&lt;P&gt;That seems to work.  My next question, is do I get hit twice for the data coming from the development site.  For indexing it twice?&lt;/P&gt;</description>
    <pubDate>Wed, 09 Oct 2013 21:30:20 GMT</pubDate>
    <dc:creator>marvatwork</dc:creator>
    <dc:date>2013-10-09T21:30:20Z</dc:date>
    <item>
      <title>Indexing question on a heavy forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-question-on-a-heavy-forwarder/m-p/91525#M19032</link>
      <description>&lt;P&gt;I have a main indexer in one location (production) that gets inputs from all the systems located in that production location.  I have a heavy-forwarder at another location (development) that gets inputs from all the systems at this second location.  If I want to keep a local copy of the index at the developement site before forwarding it to the main indexer, do I need another license?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2013 20:38:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-question-on-a-heavy-forwarder/m-p/91525#M19032</guid>
      <dc:creator>marvatwork</dc:creator>
      <dc:date>2013-10-09T20:38:32Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing question on a heavy forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-question-on-a-heavy-forwarder/m-p/91526#M19033</link>
      <description>&lt;P&gt;They can share the license. Set the development HF to be a license slave to the production Indexer. On the HF go to Manager -&amp;gt; Licensing (for Splunk 5.x). Click 'Change to slave'. Configure as needed. Don't know if there's a difference in 6.x.&lt;/P&gt;

&lt;P&gt;Then set up the development HF to forward its events as well as store them locally. Manager -&amp;gt; Forwarding &amp;amp; Receiving. Change to relevant settings in Forwarding Defaults and in Configure Forwarding. Again this is for 5.x - 6.x might be exactly the same.&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2013 21:17:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-question-on-a-heavy-forwarder/m-p/91526#M19033</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-10-09T21:17:08Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing question on a heavy forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-question-on-a-heavy-forwarder/m-p/91527#M19034</link>
      <description>&lt;P&gt;That seems to work.  My next question, is do I get hit twice for the data coming from the development site.  For indexing it twice?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2013 21:30:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-question-on-a-heavy-forwarder/m-p/91527#M19034</guid>
      <dc:creator>marvatwork</dc:creator>
      <dc:date>2013-10-09T21:30:20Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing question on a heavy forwarder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexing-question-on-a-heavy-forwarder/m-p/91528#M19035</link>
      <description>&lt;P&gt;No because it is not indexed twice.  It is indexed once and then transferred.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2013 21:45:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexing-question-on-a-heavy-forwarder/m-p/91528#M19035</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2013-10-09T21:45:28Z</dc:date>
    </item>
  </channel>
</rss>

