migrating the deployment server



we have a deployment server and some forwarders pointing to it. We might have to migrate the deployment server to a new one as the Old server needs to go down.

What is the best process to migrate the deployment server ?
Will the clients re-download the apps or will there be duplicate set of apps in the clients after pointing to the new server ?

Labels (1)
0 Karma


How do you have your deployment server defined on each system? That can change what you need to do.

If you have an app on your deployment server that is used to point to the deployment server it is quite easy. You'd want to copy you deployment apps over to the new deployment server, as well as making sure you copy your server classes over as well. Then from an app and server class perspective, your deployment server should be the same. On the new deployment server you would want to alter the app used to point to your deployment server to reflect the address of the new deployment server. Once those details are in place, you change the app on the old deployment server and as clients check in they will get the app pointing to the new server and begin checking in there instead of the old one. Clients will stop checking in by attrition.

The setting you are looking to change is in deploymentclient.conf and looks like:

targetUri = deploymentserver:8089

If the deploymentclient.conf setting is defined in $SPLUNK_HOME/etc/system/local, the change can be a bit more difficult but can explain if needed.

0 Karma


Hi there! Would you mind to explain this scenario:

"If the deploymentclient.conf setting is defined in $SPLUNK_HOME/etc/system/local, the change can be a bit more difficult but can explain if needed."

I'm looking for applying this Splunk Deployment Server migration from an old server to a new one soon!

Thanks for any feedback that you can provide me with!

0 Karma


you have two options for migration. In both options, you touch the client.

option 1 (easy) - use a software distribution system, (landesk, sccm, puppet, etc) to change the value for the targetUri. Simply update the file

option 2 (preferred) - Create a TA specifically to manage the UF client settings. Add the deploymentclient.conf file to that TA. Use a software distribution system to remove the /etc/system/local/deploymentclient.conf and copy the TA files to the client. This setting is now part of the client build and if you even need to move the deployment server, you can by simply updating the TA. This also means that any new installs must have this TA as part of the package.

0 Karma


When installing the UF on a system, the first parameter in the command line is: DEPLOYMENT_SERVER=""

This automatically places the deploymentclient.conf in the /etc/system/local folder, which deployment server does not manage. We are looking to write an external deployment script to manage the Splunk deployment server. {yeah that sounds weird}. I don't like this idea because Splunk should be able to manage Splunk. Are there other methods available? /system/local will win the conflict of any TA/App we create for deployment client.

0 Karma

Ultra Champion

A good thread at Need steps to migrate from old deployment server to new deployment server

It says

-- The problem is that deploymentclient.conf is located in $SPLUNK_HOME/etc/system/local) and this folder isn't managed by Deployment Server.

In most implementations that's the case, which makes such a migration tricky.

0 Karma
Did you miss .conf21 Virtual?

Good news! The event's keynotes and many of its breakout sessions are now available online, and still totally FREE!