Deployment Architecture

DR deployer storage setup

ankithreddy777
Contributor

Do we need to use the shared storage for Deployer and DR Deployer. Is there any better solution to sync data between two Deployers if we don't use shared storage . What is the standard solution used by splunk teams to maintain DR Deployment servers or Deployers up to date with primary counterparts.

s2_splunk
Splunk Employee
Splunk Employee

I haven't run into a lot of situations where DR comes up for a SHC Deployer, but I would say the best practice for deployment server and deployer alike is to store your Splunk configuration in a source control system (the likes of Git, Perforce, etc.) and checkout from there. This removes the need to worry about keeping things in synch and gives you easy an change auditing, versioning and backout mechanism.

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!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...