I am running Splunk 5.0.1, am in a Windows workgroup enviornment, and have 2 Windows 2008R2 servers as indexers for redundancy (indexerA and B). What I am looking to do is to establish a process to, should one server go down, restore the index from the second server. Let's say indexer B goes down for a week and I am ready to bring it back up online this is the process that I would execute...
Indexer A - roll the hot dbs to warm by running the folling command:
$SPLUNK_HOME\Splunk _internal cal /data/indexes/main/roll-hot-buckets -auth admin:
disable splunkd on indexerA
log onto indexer B and map network drive to on indexer A
copy defaultdb from indexer A to indexer B
restart splunk on both instances and both indexes should now have the same exact data
Does this sound correct?
... View more