Reporting

What about archiving/offline storage?

jones4bob
Explorer

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.

Tags (2)
0 Karma
1 Solution

dcroteau
Splunk Employee
Splunk Employee

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.

To substitute your own script, add the following stanza to $SPLUNK_HOME/etc/system/local/indexes.conf:

[] coldToFrozenScript =

Note the following:

* <index> specifies which index to archive.
* <script> specifies the archiving script.
      o Define the <$script> path relative to $SPLUNK_HOME/bin. The script needs to be located in that directory or a subdirectory. 

Splunk ships with two archiving scripts that you can modify (or you can create your own):

* 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). 

View solution in original post

dcroteau
Splunk Employee
Splunk Employee

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.

To substitute your own script, add the following stanza to $SPLUNK_HOME/etc/system/local/indexes.conf:

[] coldToFrozenScript =

Note the following:

* <index> specifies which index to archive.
* <script> specifies the archiving script.
      o Define the <$script> path relative to $SPLUNK_HOME/bin. The script needs to be located in that directory or a subdirectory. 

Splunk ships with two archiving scripts that you can modify (or you can create your own):

* 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). 
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)

Hello Splunkers,   So you searched, “what is the name of the usb key inserted by bob smith?”  Not gonna lie… ...

Automating Threat Operations and Threat Hunting with Recorded Future

    Automating Threat Operations and Threat Hunting with Recorded Future June 29, 2026 | Register   Is your ...