<?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: How to configure coldToFrozenDir in indexes.conf on multiple indexers to archive indexed data? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-coldToFrozenDir-in-indexes-conf-on-multiple/m-p/200446#M39610</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I needed to know the same answer so I setup Splunk 6.4.8  and tested. To my dismay all buckets from all indexes got to your coldToFrozenDir as db_*.&lt;/P&gt;

&lt;P&gt;Tried:&lt;BR /&gt;
coldToFrozenDir = /media/archive/splunk/$_index_name&lt;BR /&gt;
but it created&lt;BR /&gt;
/media/archive/splunk/\$_index_name/&lt;/P&gt;

&lt;P&gt;Lame.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 15:38:15 GMT</pubDate>
    <dc:creator>ephemeric</dc:creator>
    <dc:date>2020-09-29T15:38:15Z</dc:date>
    <item>
      <title>How to configure coldToFrozenDir in indexes.conf on multiple indexers to archive indexed data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-coldToFrozenDir-in-indexes-conf-on-multiple/m-p/200445#M39609</link>
      <description>&lt;P&gt;So let’s say I have 2 or 3 indexers and I configure the coldToFrozenDir in the indexes.conf…&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
maxWarmDBCount = 200
frozenTimePeriodInSecs = 432000
rotatePeriodInSecs = 30
coldToFrozenDir = "myAmason_server_mount/myfrozenarchive"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Do you do this on each of the indexers or should I do something like this&lt;/P&gt;

&lt;P&gt;Indexer1&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
maxWarmDBCount = 200
frozenTimePeriodInSecs = 432000
rotatePeriodInSecs = 30
coldToFrozenDir = "myAmason_server_mount/myfrozenarchive/index_1"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Indexer2&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
maxWarmDBCount = 200
frozenTimePeriodInSecs = 432000
rotatePeriodInSecs = 30
coldToFrozenDir = "myAmason_server_mount/myfrozenarchive/index_2"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Indexer3&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[default]
maxWarmDBCount = 200
frozenTimePeriodInSecs = 432000
rotatePeriodInSecs = 30
coldToFrozenDir = "myAmason_server_mount/myfrozenarchive/index_3"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I wasn’t sure if the indexer data files would step on each other if I send all the data using coldToFrozenDir option to the same path. i.e "myAmason_server_mount/myfrozenarchive"&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 11:37:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-coldToFrozenDir-in-indexes-conf-on-multiple/m-p/200445#M39609</guid>
      <dc:creator>locose</dc:creator>
      <dc:date>2020-09-29T11:37:45Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure coldToFrozenDir in indexes.conf on multiple indexers to archive indexed data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-coldToFrozenDir-in-indexes-conf-on-multiple/m-p/200446#M39610</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I needed to know the same answer so I setup Splunk 6.4.8  and tested. To my dismay all buckets from all indexes got to your coldToFrozenDir as db_*.&lt;/P&gt;

&lt;P&gt;Tried:&lt;BR /&gt;
coldToFrozenDir = /media/archive/splunk/$_index_name&lt;BR /&gt;
but it created&lt;BR /&gt;
/media/archive/splunk/\$_index_name/&lt;/P&gt;

&lt;P&gt;Lame.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:38:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-configure-coldToFrozenDir-in-indexes-conf-on-multiple/m-p/200446#M39610</guid>
      <dc:creator>ephemeric</dc:creator>
      <dc:date>2020-09-29T15:38:15Z</dc:date>
    </item>
  </channel>
</rss>

