Splunk® Data Stream Processor

Install and administer the Data Stream Processor

On April 3, 2023, Splunk Data Stream Processor reached its end of sale, and will reach its end of life on February 28, 2025. If you are an existing DSP customer, please reach out to your account team for more information.

All DSP releases prior to DSP 1.4.0 use Gravity, a Kubernetes orchestrator, which has been announced end-of-life. We have replaced Gravity with an alternative component in DSP 1.4.0. Therefore, we will no longer provide support for versions of DSP prior to DSP 1.4.0 after July 1, 2023. We advise all of our customers to upgrade to DSP 1.4.0 in order to continue to receive full product support from Splunk.

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.


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.


  1. Back up and save the named configuration values set in DSP.
    1. From the working directory of a node, enter:
      dsp backup --output <name of backup TAR file>
    2. If you do not use the --output flag, a standard date-based time will be used to name your backup TAR file.

    3. Once your backup is complete, you will be prompted to create and confirm a password to encrypt your backup TAR file. Save this password with your backup TAR file name in a safe location for reference in the event of a restoration.
      Please create a password to encrypt the tarball with:
      Enter password: <password>
      Confirm password: <re entered password>
    4. Save the encrypted TAR file to your desired location for storing backups.

You now have a TAR file copy of your system configurations.

Restore configurations from back up

Follow these steps to restore your DSP system configurations. This restores most cluster configurations and secrets, omitting obsolete configurations or printing out a warning for unexpected configurations. as well as connection secrets, Postgres contents (including pipeline definitions and the DSP license), lookup files, and plugins.

  1. Restore the previous configuration values.
    1. From the working directory of a node, enter:
      dsp restore <TAR file name>
    2. When prompted, enter the TAR file's password to decrypt your backup and begin restoration in your cluster.
    3. Activate your pipelines.

See also

Related topics
Cluster configuration options
Back up, restore, and share pipelines using SPL2
Last modified on 11 January, 2023
Cluster autoscaling for DSP on Google Kubernetes Engine   Increase internal partitions to improve pipeline throughput

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4

Was this topic useful?

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