Deployment Architecture

Splunk Standalone High availability setup required servers.

vijreddy30
Loves-to-Learn Everything

Hi team,

 

Currently we are implemented the Standalone below servers,

Zone-1

Environment

Server Name

IP

Splunk Role

DEV

L4

 

 

Search Head+ Indexer

QA

L4

 

 

Search Head + Indexer

L4

 

 

Deployment Server

 

Zone-2

    

Environment

Server Name

IP

Splunk Role

DEV

L4

 

 

Search Head + Indexer

QA

L4

 

 

Search Head + Indexer

 

In our environment, only 2 Indexer + Search head server is there on the same instance

 

How to Implement the High Availability Servers?

 

please help me the process.

            

Labels (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @vijreddy30 ,

see in the Splunk Validated Architectures document (https://www.splunk.com/en_us/pdfs/tech-brief/splunk-validated-architectures.pdf) what Splunk means for HA and how to implement it.

For your requirements, it's really difficoult to answer to your question!

Maybe there are some replication mechanisms, based on VM-Ware, to do this, but I'm not an expert on VM-Ware and this isn't the location for this question.

Ciao.

Giuseppe

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Honestly - I have no idea what those tables are supposed to represent.

I understand that there are two separate "zones" and you have some servers in them. How many servers and what roles do they have? Is there any connectivity between those zones or are they completely air-gapped? If so then how do you handle licensing?

What do you mean by "implement high availability"? On which layer? Architecting an environment from scratch is usually a relatively big and important task so while this forum is a good place for asking general architecture-related questions it's not a replacement for the work of properly trained Splunk Pre-sales team or Splunk Partner engineers.

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...