The Server Lifecycle

SHUTDOWN. In this state, the server is configured but inactive. 

STARTING. When you start a server, it takes the following actions:Retrieves its configuration data.  

STANDBY. (Available only if you have configured an administration port.) You can issue a command that starts a server and places it in this state. In this state, a server has initialized all of its services and applications and can accept administration commands and participate in cluster communication. It is not accessible for requests that come from external clients.

A typical use of the STANDBY state is to keep a server available as a "hot" backup, especially in a high-availability or mission-critical environment. When you need to use the backup server, you can quickly resume its ability to process client requests. 

RUNNING. In this state, a server offers its services to clients and can operate as a full member of a cluster

SHUTDOWN. You can move a server into this state either from the RUNNING state or the STANDBY state. As it transitions to SHUTDOWN, a server goes through the SHUTTING_DOWN state

FAILED. If one or more critical services become dysfunctional during the lifetime of server, the server transitions to the FAILED state. Your only option to recover from the FAILED state is to shut down the server. You can set up a server to restart itself if critical services become dysfunctional. For information about automatic restarts, Guide. 

UNKNOWN. If a server cannot be contacted, it is considered to be in the UNKNOWN state.