Failing Over and Repairing Database Clusters

Learn how to repair and restart the Database 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 Active Node (MASTER) is 172.30.129.110, clicking Disable Node will fail over this node to the Standby Node (SLAVE) 172.30.129.109.

   

   The system updates dynamically, and status of the the Active node (172.30.129.110) changes to DISABLED state.

   

4. Launch the Web Console URL for the Standby (Slave) Node in a new browser, and navigate to Database Cluster section.
   You will notice that the previous Standby node is now displayed here as the Active (MASTER) node.

   

5. Click and expand (if not expanded) the Standby (Slave) node drop down to display the status of this node.
   The node is displayed with a DISABLED state.
6. Click Repair Node Databases to repair the new Standby node and databases and bring these back to operational state.

   

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

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