Splunk® SOAR (On-premises)

Administer Splunk SOAR (On-premises)

The classic playbook editor will be deprecated in early 2025. Convert your classic playbooks to modern mode.
After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
This documentation does not apply to the most recent version of Splunk® SOAR (On-premises). For documentation on the most recent version, go to the latest release.

Upgrade or maintain warm standby instances

In order to perform system maintenance or to upgrade on a warm standby pair, warm standby must be disabled.

  1. Disable warm standby on the primary.
  2. Disable warm standby on the warm standby.
  3. Perform system maintenance or upgrade for both instances. See upgrade overview and prerequisites in Install and Upgrade .
  4. Create a warm standby pair. See Create a warm standby.

If you make any changes to warm standby using different flags, warm standby must be deactivated and then reconfigured on both the primary instance and the standby instance for the changes to take effect.

Last modified on 30 November, 2023
Recreate warm standby after a failover   Manage warm standby features and options

This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.1.0, 5.2.1, 5.3.1, 5.3.2

Acrobat logo Download manual
Acrobat logo Download this page

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