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:
Disable warm standby for Splunk SOAR (On-premises)
Disable warm standby to perform the following tasks:
- Perform system maintenance
- Configure a backup or restore your system
- Upgrade
If you want to enable warm standby again after disabling it, you must recreate it. See Create a warm standby.
To disable warm standby, you must run commands on both the primary Splunk SOAR (On-premises) system and the warm standby system.
- Log in to the primary system from the command line as the phantom user.
- On the primary system, run the following command to turn off warm standby. phenv python /<PHANTOM_HOME>/bin/setup_warm_standby.pyc --primary-mode --off
- Log in to the warm standby system from the command line as the phantom user.
- On the warm standby system, run the following command to turn off warm standby. This command also disables the cron jobs for warm standby. phenv python /<PHANTOM_HOME>/bin/setup_warm_standby.pyc --standby-mode --off
- Restart PostgreSQL. <$PHANTOM_HOME>/phsvc restart postgresql
- Continuing on the warm standby system, run the following command to stop all services. /<PHANTOM_HOME>/bin/stop_phantom.sh
Warm standby is now disabled, and cron jobs are removed to prevent rsync jobs from running.
See also:
To perform tasks while warm standby is disabled, refer to the following resources:
- backup and restore overview
- upgrade overview and prerequisites
- System maintenance and updates in security information
Failover to the warm standby | Recreate warm standby after a failover |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 6.2.2, 6.3.0
Feedback submitted, thanks!