Splunk® Phantom (Legacy)

Administer Splunk Phantom

This documentation does not apply to the most recent version of Splunk® Phantom (Legacy). For documentation on the most recent version, go to the latest release.

Disable warm standby

Warm standby must be disabled in order to:

  • perform systems maintenance
  • set up back up or perform a restore
  • upgrade Splunk Phantom

If warm standby is disabled, you will need to reconfigure warm standby from the beginning.

Disable warm standby procedure

Do these steps as either the root user or a user with sudo permissions.

On the Splunk Phantom primary

  1. Turn off warm standby.
    phenv python2.7 /<PHANTOM_HOME>/bin/setup_warm_standby.pyc --primary-mode --off

On the warm standby

  1. Turn off warm standby.
    phenv python2.7 /<PHANTOM_HOME>/bin/setup_warm_standby.pyc --standby-mode --off
  2. Stop all Splunk Phantom services.
    /<PHANTOM_HOME>/bin/stop_phantom.sh

Warm standby will be disabled, and the cron jobs removed to prevent the rsync jobs from running.

Last modified on 27 May, 2020
Failover to the warm standby   Recreate warm standby after a failover

This documentation applies to the following versions of Splunk® Phantom (Legacy): 4.8

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