Configuring hot standby

Configure a master node to run in hot standby mode. Hot standby enables a secondary node to run in parallel with the primary master server and keep an up-to-date copy of the data on the primary server. In the event of a primary master node failure, the secondary node assumes the responsibility of the master node. Configuring hot standby is required in order to achieve failover. Without hot standby enabled, the IBM® Sametime® Video Manager can run but the master node would need to be running as well.

1. Configure the primary node by completing the following steps:
   1. From the directory /root/replication_scripts, run the following script:

      sh HotStandby_config.sh primary IP address of secondary node

      For example, enter the following command:

      sh HotStandby_config.sh primary 2.2.2.2

   2. To stop and start the SolidDB process in hot standby mode, run following script using the variable start, stop, or restart according to what you are trying to accomplish:

      sh solidDB_primary.sh start|stop|restart

      For example, to stop SolidDB, enter the following command:

      sh solidDB_primary.sh stop

      Note: After configuring hot standby, do not use the SolidDB standalone scripts.
2. Configure the secondary node by completing the following steps:
   1. From /root/replication_scripts, run the following script:

      sh HotStandby_config.sh secondary IP address of primary node

      For example, enter the following command:

      sh HotStandby_config.sh primary 1.1.1.1

   2. To stop and start the SolidDB process in hot standby mode, run following script using the variable start, stop, or restart according to what you are trying to accomplish:

      sh solidDB_secondary.sh start|stop|restart

      For example, to stop SolidDB, enter the following command:

      sh solidDB_primary.sh stop

      Note: After configuring hot standby, do not use the SolidDB standalone scripts.