Failing Over and Repairing Database Clusters

Learn how to repair and restart the Database cluster.

You can use the Database Cluster in the Status section of the Web Console to failover and repair the current master cluster.

To failover and restart the cluster:

  1. Navigate to the Status section of the navigation bar and click Database Cluster to display the Database Cluster page.
  2. Click on the Node (Master) drop down to display the node status.
  3. Click Disable Node to failover the cluster from the current Master node to the Slave node.
    For example, if the Node (Master) is 10.37.231.151, clicking Disable Node will fail over this node to the Node (Slave) 10.37.231.150.

    The system updates dynamically, and the Slave node (10.37.231.150) is displayed as the new Master node. The previous Master node's status changes to Disabled state.
  4. Click the Node (Slave) drop down to display the node (Slave) status.
  5. Click Repair Node Databases to bring the node back to an operational state.

    The Node (Slave) or former Node (Master) status changes to DB_Repair mode. Status for all three databases (Core, Audit, and Message Bus) also displays the Repairing state.

    Tip: Wait for the system to finish the database repair process and update the database status.
  6. Click the Node (Slave) drop down to view the status of the repaired databases.
    If all three databases display an OK status, then the Master and Slave nodes are now fully repaired and operational.