Backup and restore Splunk DB Connect version 3.10.0 or higher

Go through the given scenario to understand how to create a DB Connect backup and restore it.

Scenario:

• We have two servers, A and B.
• Splunk DB Connect is installed and configured in server A.
• We need to migrate Splunk DB Connect from server A to B.

Backup and restore:

1. Install Splunk DB Connect in server B.
2. Make sure all Splunk JDBC Add-ons present in server A are installed in B.
3. Backup the input's checkpoints from the KV Store in server A: $SPLUNK_HOME/bin/splunk backup kvstore -collectionName dbx_db_input -archiveName <backup-name>. The backup file will be stored in $SPLUNK_HOME/var/lib/splunk/kvstorebackup/<backup-name>.tar.gz.
4. Copy the input's checkpoint backup to $SPLUNK_HOME/var/lib/splunk/kvstorebackup in server B.
5. Restore the input's checkpoints to the KV Store in server B: $SPLUNK_HOME/bin/splunk restore kvstore -collectionName dbx_db_input -archiveName <backup-name>.tar.gz.
6. Backup the secrets from the KV Store in server A: $SPLUNK_HOME/bin/splunk backup kvstore -collectionName secret -archiveName <backup-name>. The backup file will be stored in $SPLUNK_HOME/var/lib/splunk/kvstorebackup/<backup-name>.tar.gz.
7. Copy the secret's backup to $SPLUNK_HOME/var/lib/splunk/kvstorebackup in server B.
8. Restore the secrets to the KV Store in server B: $SPLUNK_HOME/bin/splunk restore kvstore -collectionName secret -archiveName <backup-name>.tar.gz.
9. Stop Splunk.
10. Copy each *.conf files from $SPLUNK_HOME/etc/apps/splunk_app_db_connect/local from server A to B.
11. Copy each *.jar from $SPLUNK_HOME/etc/apps/splunk_app_db_connect/drivers from server A to B.
12. Start Splunk.