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.
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.
Determine if the main database’s host machine
is down and cannot be restarted.
If the main database’s host machine is up, log into
it and check if the demisto service is down and cannot be restarted.
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.
For each app server:
Stop the service.
sudo systemctl stop demisto
sudo service demisto stop
Manually change the active database address in the
server's local configuration file. The default location of the configuration
Start the service.
sudo systemctl start demisto
sudo service demisto start
Navigate to the URL of the passive server and log in
as an administrator. You are presented with the following page:
Make this the production server
In the Switch Hosts dialog window, type
the text box.
The database monitoring dashboard should appear and the
database server is now active.