<?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: Multiple Splunk indexer with same $SPLUNK_DB location in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Splunk-indexer-with-same-SPLUNK-DB-location/m-p/408372#M72402</link>
    <description>&lt;P&gt;Why would you do this?  Working with VMs makes this kind of thing easy so you should not need 2 indexers at the same time.  Your forwarders can buffer events for the short time that it would take to upgrade your VM/splunk and have it come back up.  You are overcomplicating your situation.&lt;/P&gt;</description>
    <pubDate>Sun, 28 Jul 2019 12:48:20 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2019-07-28T12:48:20Z</dc:date>
    <item>
      <title>Multiple Splunk indexer with same $SPLUNK_DB location</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Splunk-indexer-with-same-SPLUNK-DB-location/m-p/408371#M72401</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;
I have $SPLUNK_DB set up in a NAS storage. But the indexer is installed in a VM (say VM1) running on splunk version 6.3.4.&lt;BR /&gt;
Now I want to migrate the indexers to another VM (VM2) with newer splunk version 6.6.12 keeping the same NAS location as $SPLUNK_DB.&lt;BR /&gt;
Is it possible? I have heard that no two indexer will see each other's indexed files. Is that true?&lt;BR /&gt;
In that case what approach I can take to migrate my indexer?&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 01:27:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-Splunk-indexer-with-same-SPLUNK-DB-location/m-p/408371#M72401</guid>
      <dc:creator>sujoybose77</dc:creator>
      <dc:date>2020-09-30T01:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple Splunk indexer with same $SPLUNK_DB location</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Splunk-indexer-with-same-SPLUNK-DB-location/m-p/408372#M72402</link>
      <description>&lt;P&gt;Why would you do this?  Working with VMs makes this kind of thing easy so you should not need 2 indexers at the same time.  Your forwarders can buffer events for the short time that it would take to upgrade your VM/splunk and have it come back up.  You are overcomplicating your situation.&lt;/P&gt;</description>
      <pubDate>Sun, 28 Jul 2019 12:48:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-Splunk-indexer-with-same-SPLUNK-DB-location/m-p/408372#M72402</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-07-28T12:48:20Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple Splunk indexer with same $SPLUNK_DB location</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Splunk-indexer-with-same-SPLUNK-DB-location/m-p/408373#M72403</link>
      <description>&lt;P&gt;Woodcock, We have organization limitations on VM storage that's not enough to hold large amount of indexed data&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2019 19:08:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-Splunk-indexer-with-same-SPLUNK-DB-location/m-p/408373#M72403</guid>
      <dc:creator>sujoybose77</dc:creator>
      <dc:date>2019-07-29T19:08:21Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple Splunk indexer with same $SPLUNK_DB location</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Multiple-Splunk-indexer-with-same-SPLUNK-DB-location/m-p/408374#M72404</link>
      <description>&lt;P&gt;You need to clarify your question.  It doesn't make sense to me.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2019 20:58:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Multiple-Splunk-indexer-with-same-SPLUNK-DB-location/m-p/408374#M72404</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-07-29T20:58:24Z</dc:date>
    </item>
  </channel>
</rss>

