Specifications

Logging With syslog
l LifeKeeper never performs an automatic switchback from a higher priority server to a lower
priority server.
Logging With syslog
Beginning with LifeKeeper 8.0, logging is done through the standard syslog facility. LifeKeeper
supports three syslog implementations: standard syslog, rsyslog, and syslog-ng. During
package installation, syslog will be configured to use the "local6" facility for all LifeKeeper log
messages. The syslog configuration file (for example, /etc/syslog-ng/syslog-ng.conf) will be
modified to include LifeKeeper-specific routing sending all LifeKeeper log messages to
/var/log/lifekeeper.log. (The original configuration file will be backed up with the same name ending in
"~".)
The facility can be changed after installation by using the lklogconfig tool located in
/opt/LifeKeeper/bin. See the lklogconfig(8) manpage on a system with LifeKeeper installed for more
details on this tool.
Note: When LifeKeeper is removed from a server, the LifeKeeper-specific syslog configuration will
be removed.
Resource Hierarchies
The LifeKeeper GUI enables you to create a resource hierarchy on one server, then extend that
hierarchy to one or more backup servers. LifeKeeper then automatically builds the designated
hierarchies on all servers specified. LifeKeeper maintains hierarchy information in a database on
each server. If you use the command line interface, you must explicitly define the hierarchy on each
server.
After you create the resource hierarchy, LifeKeeper manages the stopping and starting of the
resources within the hierarchy. The related topics below provide background for hierarchy definition
tasks.
Resource Types
A resource can be either a hardware or software entity, categorized by resource type. LifeKeeper
supplies file system and SCSI resource types, and the recovery kits provide communications,
RDBMS and other application resource types.
For example, a hierarchy for a protected file system includes instances for resources of the following
types:
l filesys. Linux file system resource objects identified by their mount point.
l device. SCSI disk partitions and virtual disks, identified by their device file names, for
example sdc1.
l disk. SCSI disks or RAID system logical units, identified by SCSI device name, for example
sd.
SteelEye Protection Suite for Linux45