<?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 What about archiving/offline storage? in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/What-about-archiving-offline-storage/m-p/13921#M157</link>
    <description>&lt;P&gt;What is the recommended way to export/archive a large amount of historical data for retention or offline storage?  I would like to clean old data from splunk but still maintain our regulatory requirements on retention.&lt;/P&gt;</description>
    <pubDate>Thu, 20 May 2010 21:25:55 GMT</pubDate>
    <dc:creator>jones4bob</dc:creator>
    <dc:date>2010-05-20T21:25:55Z</dc:date>
    <item>
      <title>What about archiving/offline storage?</title>
      <link>https://community.splunk.com/t5/Reporting/What-about-archiving-offline-storage/m-p/13921#M157</link>
      <description>&lt;P&gt;What is the recommended way to export/archive a large amount of historical data for retention or offline storage?  I would like to clean old data from splunk but still maintain our regulatory requirements on retention.&lt;/P&gt;</description>
      <pubDate>Thu, 20 May 2010 21:25:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/What-about-archiving-offline-storage/m-p/13921#M157</guid>
      <dc:creator>jones4bob</dc:creator>
      <dc:date>2010-05-20T21:25:55Z</dc:date>
    </item>
    <item>
      <title>Re: What about archiving/offline storage?</title>
      <link>https://community.splunk.com/t5/Reporting/What-about-archiving-offline-storage/m-p/13922#M158</link>
      <description>&lt;P&gt;The coldToFrozenScript (also specified in indexes.conf) runs just before the frozen data is erased. The default script simply writes the name of the directory being erased to the log file $SPLUNK_HOME/var/log/splunk/splunkd_stdout.log. If you want to archive frozen data rather than delete it, you'll need to substitute your own archiving script.&lt;/P&gt;

&lt;P&gt;To substitute your own script, add the following stanza to $SPLUNK_HOME/etc/system/local/indexes.conf:&lt;/P&gt;

&lt;P&gt;[]
coldToFrozenScript = &lt;/P&gt;

&lt;P&gt;Note the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;* &amp;lt;index&amp;gt; specifies which index to archive.
* &amp;lt;script&amp;gt; specifies the archiving script.
      o Define the &amp;lt;$script&amp;gt; path relative to $SPLUNK_HOME/bin. The script needs to be located in that directory or a subdirectory. 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Splunk ships with two archiving scripts that you can modify (or you can create your own):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;* compressedExport.sh: Export with tsidx files compressed as gz.
* flatfileExport.sh: Export as a flat text file (not recommended for current performance and resource issues -- it can take a long time, and use a lot of ram, 2-3GB, while running). 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 02 Jun 2010 23:50:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/What-about-archiving-offline-storage/m-p/13922#M158</guid>
      <dc:creator>dcroteau</dc:creator>
      <dc:date>2010-06-02T23:50:38Z</dc:date>
    </item>
  </channel>
</rss>

