Knowledge Management

Migrating Splunk data from NFS to Block storage

brad63
Engager

What is the process from migrating Splunk data from NFS based storage to Block based storage?

Tags (2)

mikelanghorst
Motivator

There's nothing really special about NFS when storing the data there (other than performance issues). I'd just use "rsync -avot" to copy over the data. That way you can run it prior to your cutover time to get it close. Then shutdown, rsync a final time, change your configs, and start. When I'd done similar, though on SAN my multi-TB switchover only took about 15min of downtime.

sowings
Splunk Employee
Splunk Employee

The only comment I'll make here is that if you rsync a bucket in its hot state (a directory name like hot_v1_15) and then later rsync again, but this time the bucket has been moved to warm (a name like db_1381409248_1381408249_15), Splunk will refuse to start because of the collision between the bucket IDs (the _15 at the end).

After your first rsync, but before your cutover, remove any hot buckets from the target system.

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!

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 ...