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
Get Updates on the Splunk Community!

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...