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

Hierarchy

Hierarchy shown on the example database
Click to enlarge the image

To protect an application effeciently, it is necessary to learn more about the structure and the dependency between the single parts of the application.

SteelEye LifeKeeper uses the name resource for the smallest modules of the application structure. Between these resources are dependencies to build a hierachy. This hierarchy is a description of the internal structure of the application.

Examples of resources are IP addresses, names or volumes. At this point you can see that every application will have it's own environment. The IP address is a part of the application, and not associated with the server machine. Different applications will have different IP adresses.

The first step to stop an application is to stop the application itself. After that, all resources will be stopped. If LifeKeeper starts an application, the first step will be to start all resources in the right sequence, and with the last step bring the application in service.

The knowledge on how to start and stop an application, the resources and the hierarchy is a main part of the Application Recovery Kit (ARK).