Splunk® SOAR (On-premises)

Administer Splunk SOAR (On-premises)

As of version 6.4.0, the visual editor for classic playbooks is no longer part of Splunk SOAR. Before upgrading, convert your classic playbooks to modern mode. Your classic playbooks will continue to run and you can view and edit them in the SOAR Python code editor.
For details, see:

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.3.3, 5.3.4, 5.3.5, 5.3.6, 5.4.0, 5.5.0, 6.0.0, 6.0.1, 6.0.2, 6.1.0, 6.1.1, 6.2.0, 6.2.1, 6.2.2, 6.3.0, 6.3.1, 6.4.0

Acrobat logo Download manual
Acrobat logo Download this page

Please expect delayed responses to documentation feedback while the team migrates content to a new system. We value your input and thank you for your patience as we work to provide you with an improved content experience!

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