CC Search Sitemap
High Availability  / Components  / Application Availability  / Cluster  / High Availability Cluster  / SteelEye LifeKeeper  / Structure & Function  /  Failover Scenarios

Failover Scenarios

LifeKeeper uses a comprehensive set of management priorities to enable it to cater for a wide range of failover scenarios. This will work only with more than two nodes.

N+1 Failover

The cluster includes a dedicated backup node for two or more primary nodes or applications. Typically, this node works as a file server with a minimum of used resources. One or more applications could failover to this node.

N+1 Failover
Click to enlarge image

N-Way Failover

Several proteced applications on a primary node could switch to different backup nodes after a failure. The background of this configuration is to have a tolerable performance after a failover or to bypass conflicts between applications after the failover.

N-Way Failover
Click to enlarge image

Cascading Failover

This option is useful for a high level of availability. Cascading Failover may be configured to have a second failover to a second backup node if the primary and the first backup node crashed. Another option to use this feature is to have a failover to a disaster recovery data center after a local failover.

Cascading Failover
Click to enlarge image