migrating splunk db _connect on application version 3.14.1 to new server with application version 4.0

[pjac1029]

I'm migrating splunk db _connect on application version 3.14.1 to new server with application version 4.0.

Given the source and destination are on different versions of splunk db connect, can I successfully migrate the kvstores so I can preserve the current rising column values of the inputs?

thanks in advance.

[livehybrid]

Hi @pjac1029 

As @PrewinThomas said, you should first upgrade to 3.18 first. If you didnt intend on migrating anything from the KV Store etc then you could go straight to the latest version as there would be no config/state to be upgraded - however to retain this it needs to go through the upgrade path to ensure that any changes to the state are updated correctly.

The following docs detail how to perform backup/restore for DB Connect in order for you to migrate to a new server: https://help.splunk.com/en/splunk-cloud-platform/connect-relational-databases/deploy-and-use-splunk-...

🌟 Did this answer help you? If so, please consider:

• Adding karma to show it was useful
• Marking it as the solution if it resolved your issue
• Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

[PrewinThomas]

@pjac1029 

Splunk recommends upgrading to 3.18.0 first, then to 4.0, to ensure a smoother transition.

#https://docs.splunk.com/Documentation/DBX/latest/DeployDBX/MigratefromDBConnectv1

So i would recommend to follow the same and then backup the kvstore and import the same to the new server.

Regards,
Prewin
If this answer helped you, please consider marking it as the solution or giving a Karma. Thanks!

[pjac1029]

To confirm, I should upgrade Splunk DB Connect on the destination host, first to version 3.18 then to version 4.0 and THEN migrate from the source host (still on db connect version 3.14).

thanks