Viewing Resource and Server Status

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.

• Standby - 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

• DataKeeper Resource States
  • Source - DataKeeper resource primary server, running successfully.
  • Target - DataKeeper resource replication target. Available to take over the resource from the primary server.
  • Out Of Sync - Mirror is stopped and data is not synchronized.
  • Wait for Previous Source - Mirror is stopped and data is not synchronized. DataKeeper resource is waiting to be synchronized with the previous source.
  • Wait to Resync - Data is not synchronized and the mirror is pending.
    To avoid replicating corrupt or inconsistent data to targets, LifeKeeper can wait for the parent resource to be in-service before replicating data.
    Refer to Verify Data Before Resync (Wait to Resync) for more information.
  • Resyncing - Mirror is running but DataKeeper resource is resyncing.
  • Paused - Mirror is paused.
  • Kernel Module Failure - Failed to load a required kernel module. The resource is not functioning properly.

• SAP Recovery Kit Resource States
  • Attention needed - The SAP resource has failed or is in a warning state. If it has failed and automatic recovery is enabled (Protection Level Full or Standard), then LifeKeeper will try to automatically recover the resource. Right-click on the SAP resource and choose Properties. This will show which SAP process is currently in a warning state. An SAP process state of Yellow may be normal (for example if the process is still initializing), but may signify that it is running slowly or encountering performance bottlenecks.

• SAP HANA Recovery Kit Resource States
  • Active - Sapstartsrv and the HDB instance are running properly.
  • Active - sapstartsrv Failure - Sapstartsrv is not running. The HDB instance status is unknown since sapstartsrv is used to check the status of HDB.
  • Active - HSR Disabled - Sapstartsrv and HDB instance are running properly. The replication mode is ‘none’, indicating that SAP HANA Replication is disabled.
  • Active - HDB Stopped - Sapstartsrv is running. The HDB instance is not running properly.
  • Active – Secondary - Sapstartsrv and the HDB instance are running properly but the active node is registered as a secondary replication site. In normal operation, the active node is expected to be the primary replication site.
  • Active – Unknown Repl Mode - Sapstartsrv and HDB instance are running properly. The replication mode cannot be determined using ‘hdbnsutil -sr_state’ or it returns an unsupported mode.
  • Active – Suspended - The database is suspended on the server where the SAP HANA resource is currently in-service. This is an unexpected state, and typically occurs when a user has performed a “takeover with handshake”
    outside of LifeKeeper.
  • Standby - This is the normal status for a resource that is out-of-service when an equivalent resource is not in-service on another node.
  • Standby - HDB Running – Sapstartsrv and the HDB instance are running on the standby (OSU) node. There is either no active (ISP) node, multiple active (ISP) nodes, or quickCheck has not determined the HSR status on the active node.
  • Standby - In Sync - Sapstartsrv and the HDB instance are running with HSR configured and reporting in-sync.
  • Standby - sapstartsrv Failure - Sapstartsrv is not running. There is an active (ISP) node. The HDB instance status is unknown since sapstartsrv is used to check the status of HDB.
  • Standby - Unknown Repl Mode - Sapstartsrv and the HDB instance are running. There is an active (ISP) node. The replication mode cannot be determined using ‘hdbnsutil -sr_state‘.
  • Standby - HSR Disabled - Sapstartsrv and the HDB instance are running. There is an active (ISP) node. Either the replication mode is ‘none’ according to ‘hdbnsutil -sr_state‘, or the HANA utility systemReplicationStatus.py returned ‘10’.
  • Standby - HSR Error - Sapstartsrv and the HDB instance are running. There is an active (ISP) node. The HANA utility systemReplicationStatus.py returned ‘11’.
  • Standby - Initializing - Sapstartsrv and the HDB instance are running. There is an active (ISP) node. HANA utility systemReplicationStatus.py returned ‘13’.
  • Standby - Syncing - Sapstartsrv and the HDB instance are running. There is an active (ISP) node. The HANA utility systemReplicationStatus.py returned ‘14’ .
  • Standby - HDB Stopped - Sapstartsrv is running. The HDB instance is not running. There is an active (ISP) node.
  • Standby - Primary - Sapstartsrv and the HDB instance are running properly, but the standby node is registered as a primary replication site. In normal operation, the standby node is expected to be a secondary replication site.
  • Standby - Unknown HSR Status - Sapstartsrv and the HDB instance are running. There is an active (ISP) node. The HANA utility systemReplicationStatus.py returned ‘12’.
  • Standby - Unexpected HSR State - Sapstartsrv and the HDB instance are running. There is an active (ISP) node. The HANA utility systemReplicationStatus.py returned a value that was not in the expected range of 10 to 15.
  • Standby - Suspended - The database is suspended on a server where the SAP HANA resource is currently out of service.