Admin Manual

 


How Splunk Works

Use WORM (Write Once Read Many) volumes for Splunk's datastore

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

Use WORM (Write Once Read Many) volumes for Splunk's datastore

Splunk can use WORM (Write Once Read Many) volumes for its index datastores. There are a few configurations that must be made in indexes.conf in order to use WORM volumes. When using a WORM volume for index datastore, Splunk will need to be configured to push data to its warm, and cold databases differently.


In a typical Splunk datastore configuration (with multiple-write disks), Splunk manages its index datastore by reading and writing into the hot database. It then pushes data to the warm database, where it is written and read multiple times. Finally, it pushes data to the cold database, where is it written once and stored until it is pushed to frozen (only requiring reads to do so).


In a write-once datastore scenario, data from the index is never pushed to the warm database. Data is pushed directly to the cold database because it is written once and never required to be written again.


Set up a WORM datastore

This documentation applies to the following versions of Splunk: 3.0 , 3.0.1 , 3.0.2 , 3.1 , 3.1.1 , 3.1.2 , 3.1.3 , 3.1.4 View the Article History for its revisions.


You must be logged into splunk.com in order to post comments. Log in now.

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.

Feedback submitted, thanks!