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.
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.
This documentation does not apply to the most recent version of Splunk® Data Stream Processor.
For documentation on the most recent version, go to the latest release.
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
- Back up and save the named configuration values set in DSP.
- From the working directory of a node, enter:
./list-configs
- Copy and save the output to your desired location for storing backups.
- From the working directory of a node, enter:
- (Optional) Back up and save any custom secrets stored in DSP.
- 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
- Copy and save the output to your desired location for storing backups.
- From the working directory of a node, enter the following command to get the values associated with the secret keys.
./get-secret <secret-key>
- Copy and save the output to your desired location for storing backups.
- 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.
You now have a copy of your system configurations.
Restore configurations from back up
Follow these steps to restore your DSP system configurations.
- Restore the previous configuration values.
-
From the working directory of a node, enter:
./set-config <PROPERTY_NAME> <VALUE>
- Repeat the previous step until all of the original configuration values have been set.
- Deploy the changes.
./deploy
-
From the working directory of a node, enter:
- Restore any custom secrets.
-
From the working directory of a node, enter:
./set-secret <SECRET_NAME> <VALUE>
- Repeat the previous step until all of the original custom secrets have been set.
- Deploy the changes.
./deploy
-
From the working directory of a node, enter:
See also
Last modified on 10 November, 2020
| Resizing a cluster by adding or removing nodes | Increase internal partitions to improve pipeline throughput |
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
Download manual
Feedback submitted, thanks!