Deployment Architecture

Changing cold storage location for a single index

justindett
Path Finder

Hi,

Our default age for all events is 3 months, but there is a specific index that's needs events to still be available for a year. A new storage location has been created and I am ready to make the change in the indexes.conf for this index. But, if I need to keep the existing events, is it just a matter of copying over all the db directories from the old /cold location to the new /cold location?

Thanks

Tags (1)
0 Karma
1 Solution

vliggio
Communicator

Yup, simple as that. Since it's cold data (not being written to), you can copy the files while the indexer(s) is up, make the config changes, and then restart Splunk. Downtime will be minimal, just a normal restart.

View solution in original post

0 Karma

vliggio
Communicator

Yup, simple as that. Since it's cold data (not being written to), you can copy the files while the indexer(s) is up, make the config changes, and then restart Splunk. Downtime will be minimal, just a normal restart.

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...