Linux Dependencies

Successful completion of the installation of LifeKeeper for Linux requires the installation of a number of prerequisite packages. To prevent script failures, these packages should be installed prior to attempting to run the installation setup script.

The prerequisite packages are broken down into the following three groups:

• General Package Dependencies

• Optional Recovery Kit Package Dependencies

Depending on the operating system version and the packages installed based on the operating system type selected (minimal, default, etc.), additional dependent packages may be required.

*Note: The dependencies are based on the versions of the OS supported by LifeKeeper. Refer to the Support Matrix for details.

!Before upgrading your Operating System, please be sure to document the list of dependencies and package(s) used via your package manager tool (yum or zypper) and note any impacts to LifeKeeper installed packages to prevent any expected removal based on dependencies. NOTE: The LifeKeeper dependent package listed below may not be complete, therefore, the actions of the package manager tool should be reviewed before performing an OS upgrade.

*Note: You may want to consider using a repository-based package manager such as yum or zypper that is designed to automatically resolve dependencies by searching in predefined software repositories thereby easing the installation of these required packages. To facilitate the installation of dependent packages, the LifeKeeper for Linux installer uses yum or zypper to install the LifeKeeper for Linux packages. Therefore, it is highly recommended that an OS package repository be setup and configured. This will negate the need to install the OS dependent packages listed below before attempting to install LifeKeeper for Linux.

rpm Install Example

rpm -ivh <package(s)>

yum Install Example

yum install <package(s)>

Zypper Install Example

zypper install <package(s)>

yum/Zypper Package Lists

The following list of rpm packages, for each distribution listed and installed with the corresponding package installer, is the minimum list of packages that will resolve all the required dependencies for LifeKeeper for Linux:

Red Hat Enterprise Linux, CentOS and Oracle Linux

yum install libXtst libstdc++ bzip2-libs pam zlib patch util-linux

SLES

zypper install libstdc++ bzip2 pam pam-modules zlib util-linux

General Package Dependencies

The following packages are always required to successfully install LifeKeeper for Linux. The package architecture version of the installed package should always match the operating system architecture (x86 or x86_64):

Red Hat Enterprise Linux, CentOS and Oracle Linux

• bzip2
• iproute
• iputils
• patch (version 2.5 or later)
• util-linux

Note: Some or all of these packages may already be installed depending on the selections made during the install of the operating system.

SLES

• bzip2
• iproute2
• iptables
• iputils
• insserv
• patch (version 2.5 or later)
• libXtst6 (SLES15 only)
• libXi6 (SLES15 only)
• util-linux
• module-legacy (SLES 15 only)

Note: Some or all of these packages may already be installed depending on the selections made during the install of the operating system.

Dependency with syslog daemon

LifeKeeper logs use the syslog daemon. LifeKeeper supports rsyslog. Before installing LifeKeeper the rsyslog daemon must be installed and activated.

Note: In the distributions using systemd such as RHEL7 or SLES12, journald administrates the log collectively. Because LifeKeeper does log output using the syslog daemon, the syslog daemon also must be operating in these environments. Therefore, set up syslog daemon to operate when using LifeKeeper.

Note: journald records the log output to a temporary file system (tmpfs) mount on /run/log/journal by default. Thus, the system log is not saved at the time of the OS shutdown. Change the setup to let the journald log perpetuate.

Note: To let the journald log perpetuate, set up “Storage=persistent” in /etc/systemd/journald.conf, or, create the /var/log/journal directory with the set up “Storage=auto” (default). After changing the set up, restart systemd-journald.service.

Optional Recovery Kit Package Dependencies

Additionally, some of the LifeKeeper for Linux optional Application Recovery Kits (ARKs) require supporting packages to be installed.

If NFS exports are to be protected via the LifeKeeper for Linux NFS Application Recovery Kit, then the following dependent packages are required:

• nfs-utils (Red Hat Enterprise Linux, CentOS, Oracle Linux)
• nfs-client (SLES)
• nfs-kernel-server (SLES)

If multipath devices are to be protected via Device Mapper Multipath (DMMP), Hitachi Dynamic Link Manager Software (HDLM), Power Path or NEC iStorage StoragePathSavior (NECSPS), then the following dependent packages are required:

• sg3_utils (All multipath kits)
• sg3_utils-libs (All multipath kits)
• HDLM (Hitachi Dynamic Link Manager Software Kit)
• EMCpower.LINUX (Power Path Kit)
• sps (NEC iStorage StoragePathSavior Kit 4.2.0 or prior)
• sps-utils and sps-driver (NEC iStorage StoragePathSavior Kit 4.2.1 or later)

If Websphere MQSeries queue managers are to be protected via the LifeKeeper for Linux Websphere MQ/MQSeries Application Recovery Kit, then the following dependent Websphere MQ packages are required:

• MQSeriesServer
• MQSeriesSamples
• MQSeriesClient
• MQSeriesRuntime
• MQSeriesSDK

If Software RAID devices are to be protected via the LifeKeeper for Linux Software RAID (md) Recovery Kit, then the following dependent package is required:

• mdadm