All Apps and Add-ons

Splunk DB Storage configuration support. (Remote Storage)

ibakal
New Member

Hi All,
We have a certain configuration for deployment which Includes an old storage which supports only CIFS UNC path.

My Question is:
What are the the consequences of defining the Index DB's on a remote CIFS Storage?
Is it feasible?
Will I encounter any limitations beside possible poor performance?

Thanks,
Igal.

Tags (3)
0 Karma

yannK
Splunk Employee
Splunk Employee

consequences of slow and non reliable storage for the splunk indexes are :

  • unreliable data (corrupted data in hot buckets)
  • poor indexing and search performance. Therefore remote mounts, NFS, etc... are not recommended.

For UNC, CIFS you should run some tests. In general local hard drives are the way to go.
And In case of lack of space, keep the hot buckets in the homePath on local/fast drived local and the coldPath on the slow/remote storage.
read the indexes.conf configuration to understand how to achieve this.

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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...