Knowledge Management

Two smartstore S3 objects in single indexer cluster

impurush
Contributor

We are planning to move to Smartstore for the cold storage and we are having the on-prem multisite indexer cluster. We are having two S3 object storage created with our partners.

Can I point out the two different S3 object storage to each site? (I know the suggested solution is to have a single indexer cluster should have single S3 object storage)

What would be the best way to migrate from On-prem to Smartstore. Our configuration around 10 indexers with each 10 TB of data on the daily volume of 300 GB/day.

Thanks in advance!

Labels (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Your indexer cluster should use a single object store for S2.  Use the second as a replicate/backup, but do so in a manner transparent to Splunk.  See https://docs.splunk.com/Documentation/Splunk/8.1.1/Indexer/MultisiteSmartStore#Deploy_multisite_inde...

For the migration steps, see https://docs.splunk.com/Documentation/Splunk/8.1.1/Indexer/MigratetoSmartStore

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Your indexer cluster should use a single object store for S2.  Use the second as a replicate/backup, but do so in a manner transparent to Splunk.  See https://docs.splunk.com/Documentation/Splunk/8.1.1/Indexer/MultisiteSmartStore#Deploy_multisite_inde...

For the migration steps, see https://docs.splunk.com/Documentation/Splunk/8.1.1/Indexer/MigratetoSmartStore

---
If this reply helps you, Karma would be appreciated.
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 ...