Verify database status

Database health

This procedure ensures that the database is in a healthy state.

1. Log in on any unified node (multinode unified topology) / database node (modular cluster topology).

2. Run the following command:

   database config

3. Verify that the stateStr of each node is one of the following values:

   • stateStr: PRIMARY

   • stateStr: ARBITER

   • stateStr: SECONDARY

4. If any node has a stateStr not listed above, contact VOSS L2 helpdesk.

   Important

   Provisioning must not take place if any of the database nodes are in the following states:

   • STARTUP

   • STARTUP2

   • RECOVERING

Primary database

This procedure ensures that the primary database is the correct node

1. Log in on any unified node (multinode unified topology) / database node (modular cluster topology).

2. Run the following commands:

   database primary

   and

   cluster run database database primary

3. Ensure the IP address matches the intended primary database expected.

4. If a failover has occurred for any reason and the primary database has changed from what is expected, refer to the “Check General Cluster Health” section.

Database weights

Database weights are used to determine how a new primary node is elected in the event of database primary node failover. Although any values can be used, recommended weights are:

• For 4 database nodes: weight of 40/30/20/10

• For 6 database nodes: weight of 60/50/40/30/20/10

These weight numbers ensure that if a re-provision occurs (when the primary data center goes offline for an indeterminate time), the remaining nodes have weights that will allow a new primary to be chosen.

1. Log in on any unified node (multinode unified topology) / database node (modular cluster topology).

2. Run the following commands:

   database config

3. Verify that weights are set with highest numbers in primary Data Center (DC), and lesser weights in secondary DC.

4. To resolve any issues, fix database weights to have the highest numbers at primary DC.