Migrating Deployment Servers - How Do Existing Apps Behave?

[stevepraz]

Looking to migrate some forwarders from one deployment server to another. I'm a little curious about how the existing apps deployed to the forwarder will behave.

Does the new deployment server need to have apps with the same name defined so that the existing apps aren't removed? Will apps that have the same name as apps that are already on that forwarder cause a conflict?

[woodcock]

The new deployment server must have apps with the same name AND WITH THE SAME CHECKSUM (e.g. the exact same content), as the old deployment server, otherwise the old apps will be deleted and the new ones will be sent to replace them.

[ddrillic]

The simplicity of the deployment server is lovely.

The documentation explains nicely that it all comes down to serverclass.conf and the deployment app - Deploy apps to clients
As long as each deployment server is responsible for a distinct set of apps and forwarders you are just fine.

[stevepraz]

Ok. I'm a little confused now. Initial answer above said if I move a forwarder from one deployment server to another that both need to have the apps named the same for it to work. Your answer indicates a distinct set of apps is required.

[gcusello]

Deployed apps are in $SPLUNK_HOME/etc/deployment-apps.
The new deployment server must have apps with the same name then the old one, otherwise the old apps will be deleted and the new ones will be installed.
Bye.
Giuseppe