Product and Software: This article applies to the Linux version of MMS.
MMS presently uses a solid database. The database on this system has a number of valid states.
The five valid states are:
- Standalone: valid state for a standalone system. This is the default state following an installation.
- Primary active: valid state for the database on the primary (active) server in a HA configured pair. This indicates that the primary (active) server's database is in sync with the database on the standby server.
- Primary alone: valid state for the database on the primary (active) server in a HA configured pair. This indicates that the primary (active) server's database is not in sync with the database on the standby server.
- Standby active: valid state for the database on the standby (inactive) server in a HA configured pair. This indicates that the standby server's database is in sync with the database on the Active server.
- Standby alone: valid state for the database on the standby (inactive) server in a HA configured pair. This indicates that the standby server's database is not in sync with the database on the standby server.
To check the state, run the following command on the MMS server in a SSH session:
/opt/aruba/solid/solsql -e "admin command 'hsb state'" dba dba
Sample output from the command:
/opt/aruba/solid/solsql -e "admin command 'hsb state'" dba dba Solid SQL Editor (teletype) v.04.50.0133 (C) Copyright Solid Information Technology Ltd 1993-2007 Connected to default server. RC TEXT -- ---- 0 STANDALONE 1 rows fetched. SOLID SQL Editor exiting.
This command may be run at any time on the active server. However on the standby server, this command will only work after the initial database copy has taken place.