Getting Data In

How to migrate old instance to new instance on-premises?

FEZ_40
Loves-to-Learn Lots

I am trying to accomplish a few actions. 

1. Move the stand alone server from one location to a different location.

2. Upgrade from old server w/unsupported  Splunk version to new server with the latest version all running in Windows.

3. Make sure the systems reporting to the old console report into the new one. 

4. Eventually decommission old instance. 

It was recommended to me to make the new instance the search head and connect to the old instance as a search peer, but then I started to see the following errors in the new instance:

 "Problem replicating config (bundle) to search peer ' X.X.X.X:8089 ', Upload bundle="C:\Program Files\Splunk\var\run\hostname-1654707664.bundle" to peer name=hostname uri=https://X.X.X.X:8089 failed; http_status=409 http_description="Conflict".

Then, I tried to . Point the Universal Forwarders to the new instance, adding the CLI commands, since no outputs.conf was in the old instance. 

and got the following errors: 

RED - the health status for the splunkd service. 

RED - TCPOUTAutoLB-Q

RED - TailReader-0

I really appreciate all the help. 

Thank you,

 

Labels (1)
Tags (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Guided Onboarding with Auto-schema Is Now Generally Available

  We are excited to announce the General Availability of Guided Onboarding with Auto-Schematization ...

ATTENTION: We’re Moving! (AGAIN!)

The Splunk Community Slack is undergoing a system migration to keep our workspace secure and ...

Deep Dive: Optimizing Telemetry Pipelines in Splunk Observability Cloud

In this session, we will peel back the layers of Splunk Observability Cloud’s cost-optimization features. ...