Deployment Architecture

Migrating HOT data to a new drive/faster storage

ajromero
Path Finder

We are planing on move our HOT data to  a faster storage. This new drive is already present in our Windows Index, so what is the best way to approach this. We use NetApp for storage

thank you

Labels (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

here is official way to move whole SPLUNK_DB directory to the new place. https://docs.splunk.com/Documentation/Splunk/8.0.5/Indexer/Moveanindex
Of course the actual steps depends on your environment, single indexer, cluster and which kind of service break you can have?

One easy way is add the new drive as own volume and then create new indexes and set their homePath to point that volume. This is doable w/o any service break. Only negative point is that your users must start to use new and old index names on their queries.

r. Ismo

0 Karma

ajromero
Path Finder

I was thinking if possible, can I restore the HOT data from a backup into the new drive?

 

thanks

0 Karma

isoutamo
SplunkTrust
SplunkTrust
As you cannot backup hot data (only warm and cold), you cannot do it.
You can move warm data to the new drive/fs when splunk is down. Then you also must update homePath of those indexes on indexes.conf to point the new directory. Actually this “moves” also hot data to the new drive/fs. If you have clustered environment then this must do at same time to all peers.
Get Updates on the Splunk Community!

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...

Get the T-shirt to Prove You Survived Splunk University Bootcamp

As if Splunk University, in Las Vegas, in-person, with three days of bootcamps and labs weren’t enough, now ...

Wondering How to Build Resiliency in the Cloud?

IT leaders are choosing Splunk Cloud as an ideal cloud transformation platform to drive business resilience,  ...