Splunk® Data Stream Processor

Install and administer the Data Stream Processor

Acrobat logo Download manual as PDF


On October 30, 2022, all 1.2.x versions of the Splunk Data Stream Processor will reach its end of support date. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see the Upgrade the Splunk Data Stream Processor topic.
Acrobat logo Download topic as PDF

Back up your Splunk Data Stream Processor deployment

It is recommended that you periodically back up the Splunk Data Stream Processor (DSP) system configurations. Doing a back up of a healthy environment enables you to restore from a back up in the event of a disaster.

Prerequisites

You must have system administrator (root) permissions to run DSP installation or cluster management commands. If you do not have these permissions, you can use the sudo command.

Steps

  1. Back up and save the named configuration values set in DSP.
    1. From the working directory of a node, enter:
      ./list-configs
    2. Copy and save the output to your desired location for storing backups.
  2. (Optional) Back up and save any custom secrets stored in DSP.
    1. From the working directory of a node, enter the following command to get a list of secret keys. This command only returns custom secrets. Secrets with default values are not returned.
      ./list-secrets
    2. Copy and save the output to your desired location for storing backups.
    3. From the working directory of a node, enter the following command to get the values associated with the secret keys.
      ./get-secret <secret-key>
    4. Copy and save the output to your desired location for storing backups.

You now have a copy of your system configurations.

Restore configurations from back up

Follow these steps to restore your DSP system configurations.

  1. Restore the previous configuration values.
    1. From the working directory of a node, enter:
      ./set-config <PROPERTY_NAME> <VALUE> 
    2. Repeat the previous step until all of the original configuration values have been set.
    3. Deploy the changes.
      ./deploy
  2. Restore any custom secrets.
    1. From the working directory of a node, enter:
      ./set-secret <SECRET_NAME> <VALUE>
      
    2. Repeat the previous step until all of the original custom secrets have been set.
    3. Deploy the changes.
      ./deploy

See also

Related topics
Cluster configuration options
Back up, restore, and share pipelines using SPL2
Last modified on 10 November, 2020
PREVIOUS
Resizing a cluster by adding or removing nodes
  NEXT
About the Splunk App for DSP

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.0, 1.2.1-patch02, 1.2.1, 1.2.2-patch02, 1.2.4, 1.2.5, 1.3.0, 1.3.1


Was this documentation topic helpful?


You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters