Open topic with navigation
Before you begin constructing an interface between your application and LifeKeeper, you need to be sure that you have the appropriate hardware and software (including your application and LifeKeeper) installed and working properly.
After you are assured that your components are configured and working properly, you should perform the following steps to create the interface with LifeKeeper:
Establish application operation within the configuration. The first step is to set up the application appropriately for operation with the shared disk environment. You must configure the application and its associated environment on each of the LifeKeeper servers so that any one of the servers can access and run the application at different times. For example, this might mean installing the application on all servers, mounting and populating the shared file systems and creating the same user and group IDs on all servers.
It is always necessary to verify that the application is functional on all servers before configuring the application to be under LifeKeeper protection. Before defining the resource hierarchy in LifeKeeper, the application should be running on the server that you want to be the primary.
Create application scripts (or programs). LifeKeeper uses a set of scripts (or programs) to start or stop an application. The two scripts generally required for any application under LifeKeeper are restore and remove. You can also provide other action scripts to determine how the application or the system reacts to specific operational conditions.
Define the LifeKeeper resource hierarchy. In order for LifeKeeper to control an application in the event of system failures or administrative actions, you must define a resource hierarchy. This definition implies creating resource instances and relationships for the application and other system resources such as shared file systems and disks, communication facilities and other applications.
There are three ways to define the LifeKeeper resource hierarchy:
Using the LifeKeeper GUI.
Using the LifeKeeper configuration database interface (LCDI) commands, (for applications dependent upon multiple disk partitions and/or file systems or any arbitrary application type).
Using a combination of GUI and command functions. The LCDI Command Interface topic provides a creation example using both the GUI and the LCDI commands.
Establishing any optional application fault detection. The ability to provide detection and alarming for problems within an application is valuable for building the best fault resilient solution. Because every specific application varies on the mechanism and format of failures, no one set of generic mechanisms meets all needs. LifeKeeper does, however, provide a complete environment for defining errors, alarms and events that can trigger recovery procedures. For further information, see the LifeKeeper Alarming and Recovery topic.
© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.
Open topic with navigation