Splunk Enterprise Security

How to move the entire configuration from one HF to new HF server?

saibal_das
Explorer

Due to some issue, We have to discontinue our existing Heavy Forwarder and move all the sources, data inputs, Splunk TA Apps/add-on one new server where we have already installed Heavy forwarder.

Both of the heavy forwarders are having the same version and present in Linux environment only. So just need to understand how can we easily move all the existing conf files, Splunk TA Apps/add-on and data inputs. So that without hampering any data loss we can move the HF server.

Please add the splunk doc link as well if possible which we can use for linux environment. 

0 Karma
1 Solution

PickleRick
SplunkTrust
SplunkTrust

Most of the config should work pretty much the same so moving config should work.

But there are some small things to check:

1. I'd double check whether any scripted/modular inputs don't leave some state information behind.

2. I suppose you're moving to another IP and hostname so verify whether your indexers can accept data from the new forwarder. Check your firewall rules of course as well as any rules limiting inputs from IP and subject names in case you're using mutual TLS.

3. Remember to reconfigure your UFs sending to HFs so they include the new one in their load-balancing group.

View solution in original post

somesoni2
Revered Legend

Once you've made sure that both HF are equivalent (network/firewall/hardware/software are same), then you can justStop Splunk on old HF , take a backup of $SPLUNK_HOME (/opt/Splunk) on old HF and copy/restore it to new HF. and start/restart on new HF. 

saibal_das
Explorer

Thank you for the overview. It works for me. @somesoni2 

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Most of the config should work pretty much the same so moving config should work.

But there are some small things to check:

1. I'd double check whether any scripted/modular inputs don't leave some state information behind.

2. I suppose you're moving to another IP and hostname so verify whether your indexers can accept data from the new forwarder. Check your firewall rules of course as well as any rules limiting inputs from IP and subject names in case you're using mutual TLS.

3. Remember to reconfigure your UFs sending to HFs so they include the new one in their load-balancing group.

saibal_das
Explorer

Thank you for mentioning the small thing. It helps me to understand in a better way and it works for me. @PickleRick 

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

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...