Deployment Architecture

Migrating to using volumes in indexes.conf

supersleepwalke
Communicator

Now that Splunk 4.2 introduced the concept of volumes for storing indexes, I'd like to change my configs to use it. (Our storage solution matches their example, fast local RAID 0+1 for hot/warm buckets, a NAS for cold storage.)

Configure index size with volumes

If I change my indexes.conf to using the volume concept, and make sure that they all end up pointing to the same directories as my original config, will that work properly? Will buckets still end up in the same place as before, and retirement still work seamlessly?

1 Solution

jbsplunk
Splunk Employee
Splunk Employee

As long as your volumes are all pointing to the folders you'd like them to use, everything should go seemlessly once you hit the threshold specified for rotation. You will need to restart once you apply these changes.

View solution in original post

jbsplunk
Splunk Employee
Splunk Employee

As long as your volumes are all pointing to the folders you'd like them to use, everything should go seemlessly once you hit the threshold specified for rotation. You will need to restart once you apply these changes.

Get Updates on the Splunk Community!

Splunk Life | Happy Pride Month!

Happy Pride Month, Splunk Community! 🌈 In the United States, as well as many countries around the ...

SplunkTrust | Where Are They Now - Michael Uschmann

The Background Five years ago, Splunk published several videos showcasing members of the SplunkTrust to share ...

Admin Your Splunk Cloud, Your Way

Join us to maximize different techniques to best tune Splunk Cloud. In this Tech Enablement, you will get ...