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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...