<?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: Archiving frozen data to network drive in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Archiving-frozen-data-to-network-drive/m-p/394158#M6659</link>
    <description>&lt;P&gt;@dkeck Yes.&lt;/P&gt;</description>
    <pubDate>Wed, 09 Jan 2019 08:30:55 GMT</pubDate>
    <dc:creator>sudhir7</dc:creator>
    <dc:date>2019-01-09T08:30:55Z</dc:date>
    <item>
      <title>Archiving frozen data to network drive</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Archiving-frozen-data-to-network-drive/m-p/394156#M6657</link>
      <description>&lt;P&gt;I am trying to archive data to the network drive, I have following stanza in my indexes.conf file.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[indexName]
frozenTimePeriodInSecs = 31622400
coldToFrozenDir = \\netwotkDrive\splunk\indexName\frozendb
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This setting is not working for me.&lt;BR /&gt;
Has anyone else faced a similar situation? Are there any configurational settings I am missing?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jan 2019 05:02:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Archiving-frozen-data-to-network-drive/m-p/394156#M6657</guid>
      <dc:creator>sudhir7</dc:creator>
      <dc:date>2019-01-09T05:02:20Z</dc:date>
    </item>
    <item>
      <title>Re: Archiving frozen data to network drive</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Archiving-frozen-data-to-network-drive/m-p/394157#M6658</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;did you restart after changing this?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jan 2019 07:25:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Archiving-frozen-data-to-network-drive/m-p/394157#M6658</guid>
      <dc:creator>dkeck</dc:creator>
      <dc:date>2019-01-09T07:25:33Z</dc:date>
    </item>
    <item>
      <title>Re: Archiving frozen data to network drive</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Archiving-frozen-data-to-network-drive/m-p/394158#M6659</link>
      <description>&lt;P&gt;@dkeck Yes.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Jan 2019 08:30:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Archiving-frozen-data-to-network-drive/m-p/394158#M6659</guid>
      <dc:creator>sudhir7</dc:creator>
      <dc:date>2019-01-09T08:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: Archiving frozen data to network drive</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Archiving-frozen-data-to-network-drive/m-p/394159#M6660</link>
      <description>&lt;P&gt;I wasn't able to get this to work directly to a network folder as you posted. If you are still working on it, I ended up configuring a folder on each indexer that is a NTFS junction to a remote file share. This way, the splunk service writes as if it is a local file and NTFS takes care of the rest. I'm not sure if it's a supported solution, but my low-volume cluster has been running like this for several years with no apparent issues.&lt;/P&gt;

&lt;P&gt;One thing to note with an indexer cluster is to point the junction to a different folder within the share for each machine to avoid naming collisions (IndexerA's junction should point to \server\share\indexerA and IndexerB's to \server\share\indexerB or some similar scheme).&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2019 20:57:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Archiving-frozen-data-to-network-drive/m-p/394159#M6660</guid>
      <dc:creator>suamme1</dc:creator>
      <dc:date>2019-10-09T20:57:55Z</dc:date>
    </item>
  </channel>
</rss>

