Deployment Architecture

Re-indexing cold data

loatswil
Path Finder

We have some year old cold data that has been restored from tape. We would like to re-index and search this data.

What is the best way to do this?

I have looked at the "oneshot" method but it appears to be designed for a single log file. This is an entire "colddb" directory from an indexer.

Thanks!

Tags (2)
0 Karma
1 Solution

yannK
Splunk Employee
Splunk Employee

You do not need to reindex buckets, just make them searchable.
Use the same procedure than restoring frozen buckets : copy them to your thawedPath location.
see http://docs.splunk.com/Documentation/Splunk/6.0.3/Indexer/Restorearchiveddata

Remark : you could copy them back to the coldPath, but the retention rules (size and time) will immediately apply, and the buckets can be deleted. So the thawedPath is the best solution.

View solution in original post

yannK
Splunk Employee
Splunk Employee

You do not need to reindex buckets, just make them searchable.
Use the same procedure than restoring frozen buckets : copy them to your thawedPath location.
see http://docs.splunk.com/Documentation/Splunk/6.0.3/Indexer/Restorearchiveddata

Remark : you could copy them back to the coldPath, but the retention rules (size and time) will immediately apply, and the buckets can be deleted. So the thawedPath is the best solution.

Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...