Specifications

Related Topics
The LifeKeeper Configuration Database (LCD) maintains the object-oriented resource hierarchy
information and stores recovery direction information for all resource types known to LifeKeeper. The
data is cached within system shared memory and stored in files so that configuration data is retained
over system restarts. The LCD also contains state information and specific details about resource
instances required for recovery.
See the following related topics for information on the LCD directory structure, types of data stored,
resource types available and use of application scripts.
Related Topics
LCDI Commands
LifeKeeper provides two mechanisms for defining an application resource hierarchy:
l LifeKeeper GUI
l LifeKeeper Configuration Database Interface (LCDI) commands
The LCDI is a set of interface commands provided by LifeKeeper that you can use to create and
customize resource hierarchy configurations to meet your application needs. You use the command
interface when an application depends upon multiple resources (such as two or more file systems).
For a description of the commands, see the LCDI manual pages. This topic provides a development
scenario that demonstrates the way you can use both the GUI and command functions to create a
resource hierarchy.
Scenario Situation
The example application, ProjectPlan, has data stored in SCSI file systems shared by Servers 1 and
2. Server 1 will be the primary hierarchy for the application. The application has two file systems:
/project-data and /schedule. The first step in the hierarchy definition is to determine the
dependencies.
The example application has these dependencies:
l Shared file systems. The application depends upon its file systems: /project-data and
/schedule.
l SCSI disk subsystem. The file systems in turn depend upon the SCSI disk subsystem,
which includes the device, diskand host adapter resources.
As a result, the task is to create a hierarchy that looks like the following diagram.
192User Guide