Hi @msmadhu,
Splunk does not offer native clustering for Deployment Servers (DS) in the same way it does for indexers or search heads. High availability (HA) for the DS is typically achieved using external components (Typically a load balancer).
The common approach involves:
- Setting up two (or more) independent Deployment Server instances.
- Using a network load balancer (LB) in front of these instances.
- Configuring deployment clients (Universal Forwarders) to point to the virtual IP (VIP) or hostname of the load balancer.
- Keeping the configuration ($SPLUNK_HOME/etc/deployment-apps/) synchronized between the DS instances. This can be done manually, via scripting, or using shared storage (e.g., NFS), though shared storage requires careful implementation.
This architecture relies on external systems (load balancer, potentially shared storage or sync scripts) and requires careful management to ensure configurations are consistent across DS instances.
You can find guidance on HA strategies in the Splunk Enterprise Admin Manual: Protect against loss of the deployment server
🌟 Did this answer help you? If so, please consider:
- Adding kudos 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
