Specifications

LifeKeeper Core
Description
lkscsid will halt system when it should issue a sendevent
When lkscsid detects a disk failure, it should, by default,issue a sendevent to LifeKeeper to
recover from the failure. Thesendevent will first try to recover the failure locally and if thatfails,
will try to recover the failure by switching the hierarchy withthe disk to another server.On some
versions of Linux (RHEL5 andSLES11), lkscsid will not be able to issue the sendevent but
instead willimmediately halt the system.This only affects hierarchies usingthe SCSI device
nodes such as /dev/sda.
Setup will fail for RHEL6 64-bit
There is a compatibility issue against Red Hat Enterprise Linux 6 64-bit.
Solution:Install the following packages, which are contained in the installation media of the OS,
prior to installing LifeKeeper. If these are not installedpriorto running LifeKeeper setup, the setup
will not finish correctly.
rpm -i compat-libstdc++-33-3.2.3-69.el6.i686 libgcc-4.4.4-13.el6.i686
rpm -i nss-softokn-freebl-3.12.7-1.1.el6.i686 glibc-2.12-1.7.el6.i686
Note: SeePackage Dependencies List for LifeKeeper 7.5 and Later for more information.
DataKeeper Create Resource fails
When using DataKeeper with fully virtualized VMs running on Citrix XenServer (or other hypervisor
that may provide IDE disk emulation), an error occurs on the create:
ERROR 104052: Cannot get the hardware ID of the device "dev/hda3"
This is due to the fact that the fully virtualized VMs have their local disk drives show up as IDE
drives andgetId is not able to query IDE disks on these VMs properly.
Workaround: Add /dev/hda* to the DEVNAME device_pattern file, e.g.:
# cat /opt/LifeKeeper/subsys/scsi/Resources/DEVNAME/device_
pattern
/dev/hda*
Specifying hostnames for API access
The key name used to store LifeKeeper server credentials must matchexactlythe hostname of the
other LifeKeeper server (as displayed by the hostname command on that server). If the hostname
is an FQDN, then the credential key must also be the FQDN. If the hostname is a short name, then
the key must also be the short name.
Workaround:Make sure that the hostname(s) stored by credstore match the hostname exactly.
SteelEye Protection Suite for Linux225