Viewing Resource and Server Status

*This documentation section describes the LifeKeeper Web Management Console (LKWMC). Refer to the LifeKeeper Web Management Console for an overview.

The status of each server and resource may be viewed from the Resource Tree.

The status of a protected resource on a particular server is reflected in the text, color, and icon shown in the corresponding cell. If a resource has not been extended to a particular server, the corresponding cell will appear blank.

Server States

The possible server states are shown below.

• Alive - LifeKeeper is functioning normally. All communication paths from this server to remote servers are ALIVE.

• Warning - Client has a valid connection to the server. One or more communication paths from this server to a given remote server are marked as DEAD, or no redundant communication paths exist from this server to a given remote server.

• Dead - Reported as DEAD by other servers in the cluster.

• Unknown - Network connection was lost. Last known LifeKeeper server state is ALIVE or the REST API server is not running on the server.

Resource States

The possible resource states are shown below. In addition to these generic resource states, some application recovery kits also provide resource-specific custom states (such as the “In-Sync” state for a DataKeeper resource indicating that replication is in-sync to a particular mirror target).

• Active - The resource is operational. LifeKeeper local recovery is operating normally. LifeKeeper inter-server recovery and failure recovery is operational.

• Warning - The resource is operational. However, no local recovery or failure recovery will occur because the LifeKeeper health check is not currently being performed for the resource.

• Failed - The resource has failed and has been taken out of service. Recovery has not been completed or has failed. LifeKeeper alarming is not operational for this resource.

• Passive - The resource is out of service but is available to take over an equivalent resource from another server.

• Unknown - The state of the resource could not be determined.

• Illegal - This state appears in situations where no state has been set for a resource instance. Under normal circumstances, this is a transient state which may appear while the resource is transitioning to another state. This state will be shown if switchover occurs before all LifeKeeper information tables have been updated (for example, when LifeKeeper is first started up).

Recovery Kit-Specific Resource States

• Recovery Kit for Volume
  • [Split Brain]
    DataKeeper mirror is in the split brain state. The mirrored volume is recognized as the Active on both servers and this can cause data loss.
  • [Maintenance]
    The DataKeeper mirror is in maintenance mode. In maintenance mode, the volume check script is not executed.
  • [Mirroring]
    DataKeeper mirror is resyncing and can take over resources from the primary server.
  • [Paused]
    DataKeeper mirror paused.
  • [Broken]
    DataKeeper mirror broken.
  • [Resyncing]
    DataKeeper mirror is running but DataKeeper resource is resyncing.
  • [Resync Pending]
    DataKeeper mirror resynchronization paused.
  • [ILLEGAL]
    DataKeeper mirror has no state.