Specifications

LVM Recovery Kit
Description
When changes are made to res_state, monitoring is disabled
IfProtection Levelis set toBASICand SAP is taken down manually (i.e. for maintenance), it will
be marked as FAILED and monitoring will stop.
Solution: In order for monitoring to resume, LifeKeeper will need to start up the resource instead of
starting it up manually.
ERS in-service fails on remote host if ERS is not parent of Core/CI
Creating an ERS resource without any additional SAP resource dependents will cause initial in-
service to fail on switchover.
Solution:Create ERS as parent of CI/Core instance (SCS or ASCS), then retry in-service.
LVM Recovery Kit
Description
Use of lkID incompatible with LVM overeaten on entire disk
When lkID is used to generate unique disk IDs on disks that are configured as LVM physical
volumes, there is a conflict in the locations in which the lkID and LVM information is stored on the
disk. This causes either the lkID or LVM information to be overwritten depending on the order in
which lkID and pvcreate are used.
Workaround: When it is necessary to use lkID in conjunction with LVM, partition the disk and use
the disk partition(s) as the LVM physical volume(s) rather than the entire disk.
LVM actions slow on RHEL 6
When running certain LVM commands on RHEL 6, performance is sometimes slower than in
previous releases. This can be seen in slightly longer restore and remove times for hierarchies with
LVM resources.
The configuration of Raw and LVMRecovery Kits together is not supported in RHEL 6
environment
When creating a Raw resource, the Raw Recovery Kit is looking for a device file based on major #
and minor # of Raw device. As the result, /dev/dm-* will be the device; however, this type of
/dev/dm-* cannot be handled by the LVM Recovery Kit and a "raw device not found" error
will occur in the GUI.
240Troubleshooting