Deployment Architecture

Restoring only selected indexes, backup best practices


Hello. We are planning an upgrade from Splunk 7.2.1 to Splunk 8.0.x. For best practices, we'd like to back up our indexes prior to the upgrade, but we're having an issue: our backup solutions can never keep up with the amount of incoming data, and we can't (won't) turn Splunk off for a long enough time to freeze incoming traffic for a full backup. It's many terabytes of data...

Some indexes are more important than others, so I was kicking around backing up just the 'critical' indexes. If we upgrade and the indexes become corrupted, we could still restore the important indexes.

Is that sound logic? Can indexes be restored piece-meal like that?

Our environment is simple: one Indexer/Search head with a bunch of UFs.

Also, if anyone has any recommendations for backing up Splunk indexes, please let me know. I've read Splunk's docs as well as posts on here on how to do it but, as I mentioned, the backups just can't keep up with the incoming stream.


0 Karma


Are your indexers clustered?

If this reply helps you, an upvote would be appreciated.
0 Karma


They are not. Simple environment. One indexer, bunch of forwarders. I'll update the original post with that info.

0 Karma
Don’t Miss Global Splunk
User Groups Week!

Free LIVE events worldwide 2/8-2/12
Connect, learn, and collect rad prizes
and swag!