Starting a Server

A server in UNINITIALIZED "INHIBITED" state cannot run the LSMS application and is not available as a standby server. Use the following procedure to change the state of a server from UNINITIALIZED "INHIBITED" to a state where it is available to run the LSMS application.

During the starting process on a given server, the LSMS HA utility checks to see if the other server is in ACTIVE state. Therefore, the state of the server at the end of this procedure will be one of the following:

If the other server is not in the ACTIVE state, this server will transition to ACTIVE state.
If the other server was in the ACTIVE state, this server will perform the following functions:
- Copy the MySQL binary logs from the active server
- Take a snapshot of the active server’s database
- Transition to STANDBY state
- Configure its MySQL to be a slave to the active server’s master
- Start performing MySQL replication

Log in as the lsmsmgr user to the appropriate server, depending on the server states, as follows (for information about logging in as lsmsmgr, see “Logging In to LSMS Server Command Line”):
- If both servers are in UNINITIALIZED "INHIBITED" state, log into the server that you want to make active.
  After you have finished this procedure on that server, repeat this procedure for the other server.
- If one server is in ACTIVE state, log into the server that is not active.
  Note: Do not attempt to change the state of the server while any of the following processes are running on the active server: backups (automatic or manual), running the import command, running the lsmsdb quickaudit command, or creating query server snapshots, all of which use temporary storage space. If you attempt to change the state of the server while any of these processes are running, you may not have enough disk space to complete the process. Since backups can be run automatically, perform the procedure described in “Checking for Running Backups” to ensure that no backups are running.
From the main lsmsmgr interface, select Maintenance > Start Node.
The lsmsmgr interface displays.
Starting a Server
Ensure that the Yes button is highlighted and press Enter.
While the server is being started, the lsmsmgr interface disappears and text similar to the following is displayed on the command line when this procedure is being performed on a server (lsmssec in this example) in UNINITIALIZED "INHIBITED" state while the other server is in ACTIVE state:
```
LSMS starting up on lsmssec...
Checking status from active mate...
Running status on lsmspri node
Copying DB from active mate. Local node will become standby.
  This may take a while
LSMS shutting down lsmssec...
Syncing mate:/mnt/snap/ to /var/TKLC/lsms/db/
Sync'ed
LSMS starting up on lsmssec...
Unihibiting node lsmssec...
Startup of local node successful

Press enter to continue...
```
Note: The text that displays is different when this procedure is being performed when both servers were originally in UNINITIALIZED "INHIBITED" state, but the condition when both servers are in UNINITIALIZED "INHIBITED" state happens only during upgrade.
Press any key.
The lsmsmgr main menu is displayed again.

The state of the server will be as described in the beginning of this section. To display the server state, use the procedure described in Determining the Server Status.