Deployment Architecture

Backup for indexer?

kalyanilandge
New Member

Hello ,
I need to upgrade the version on splunk indexer from 6.2 to 6.3.1, with the clustered enviornment for that i need to take the backup-
Is this sufficient? or in additin to this what all things required?
$SPLUNK-HOME/var/lib/splunk/default/db/*
$SPLUNK-HOME/etc/

Tags (1)
0 Karma

woodcock
Esteemed Legend

Just backup everything; the software is so small compared to the data that it is insignificant. Besides, if you need to restore, you will be restoring the old software anyway (because there was a problem with the upgrade).

The process should be this:

Block port 9997 and 9998 on the Indexer so that incoming data cannot arrive from forwarders.
Remove the Indexer from all Search Heads as a Search Peer (now ALL searches will be missing a little bit of data so let people know by updating `web.conf` with a warning message).
You have now successfully isolated this 1 Indexer.
Do your backup (copy everything).
Upgrade the software by reinstalling it OVER the original location.
Start splunk.
Answer the questions (you should almost always say `Yes` to every question).
Re-add the Indexer to one Search Head and see that old data is still available in your search results (see `splunk_server` field).
If everything is OK, unblock port 9997 and 9998 on the Indexer and see that new data is available in your search results.
Re-add the Indexer to all Search Heads,
Done.

If you are in a clustered environment, it will be a little different.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...