End-of-Life (EoL)

Transition a Standby Server to Active Mode

Follow these steps replace a failed main database.
The following instructions are for replacing the main database in the event of a real disaster scenario. This means that the main database is down and cannot be brought back online. Since the user interface is not available, the procedure involves manual steps.
  1. Manually verify that the main database really is down (as opposed to a connectivity issue for a particular app server). Make sure it will not come back online later.
    1. Determine if the main database’s host machine is down and cannot be restarted.
    2. If the main database’s host machine is up, log into it and check if the demisto service is down and cannot be restarted.
    3. If the demisto service is up, rule out a network or firewall issue by checking if the main database’s machine is accessible from the app server's machine.
  2. For each app server:
    1. Stop the service.
      - CentOS:
      sudo systemctl stop demisto
      - Ubuntu:
      sudo service demisto stop
    2. Manually change the active database address in the server's local configuration file. The default location of the configuration file is
      /etc/demisto.conf
      For example:
    3. Start the service.
      - CentOS:
      sudo systemctl start demisto
      - Ubuntu:
      sudo service demisto start
  3. Navigate to the URL of the passive server and log in as an administrator. You are presented with the following page:
  4. Click the
    Make this the production server
    button.
  5. In the Switch Hosts dialog window, type
    Switch Hosts
    in the text box.
The database monitoring dashboard should appear and the database server is now active.
When the system is back online, you will probably want to set up a new standby server for your main database. See Configure a Live Backup for a Distributed Database Overview for details.

Recommended For You