topic Re: Migrating HOT data to a new drive/faster storage in Deployment Architecture

Migrating HOT data to a new drive/faster storage

ajromero — Fri, 11 Sep 2020 15:39:57 GMT

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

Re: Migrating HOT data to a new drive/faster storage

isoutamo — Fri, 11 Sep 2020 15:54:17 GMT

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

Re: Migrating HOT data to a new drive/faster storage

ajromero — Fri, 11 Sep 2020 16:06:21 GMT

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

thanks

Re: Migrating HOT data to a new drive/faster storage

isoutamo — Fri, 11 Sep 2020 16:14:08 GMT

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.