Version 9.3.2

Important!!

Read This Document Before Attempting To Install Or Use This Product!
This document contains last minute information that must be considered before, during and after installation.

Introduction

This release notes document is written for the person who installs, configures and/or administers the LifeKeeper Single Server Protection for Linux product. The document contains important information not detailed in the formal LifeKeeper Single Server Protection documentation set such as system requirements, new features and links to product restrictions and troubleshooting hints and tips. It is important that you review this document before installing and configuring LifeKeeper Single Server Protection software.

LifeKeeper Single Server Protection Product Description

LifeKeeper Single Server Protection allows for application monitoring in a single node configuration (i.e., no cluster requirements or restraints). Single node environments may be physical or virtual (vSphere, KVM, Amazon EC2). LifeKeeper Single Server Protection is built on the proven and stable architecture of SIOS LifeKeeper. LifeKeeper Single Server Protection provides superior application monitoring and can perform recovery of failed applications and system infrastructure items (e.g., NFS share, IP address, File System). If an application cannot be recovered for some reason, LifeKeeper Single Server Protection will initiate a restart of the node via a system reboot or via a VMware HA restart for VMware virtual machines configured for VM and Application Monitoring.

Components

LifeKeeper Single Server Protection Software is bundled and runs on 64-bit systems (x86_64, AMD64) and is comprised of the following components:

  • LifeKeeper Single Server Protection Software
  • SteelEye Management Console with LifeKeeper Single Server Protection vSphere Client Plug-in (optional software for VMware environments only)

LifeKeeper Single Server Protection Optional Recovery Software

The following optional software provides resource definition and recovery software for the application versions listed:

Package
Package Name
Protected Applications
LifeKeeper Apache Web Server Recovery Kit steeleye-lkAPA-9.3.2-6863.noarch.rpm Apache Web Server v2.4
LifeKeeper SAP Recovery Kit steeleye-lkSAP-9.3.2-6863.noarch.rpm

SAP

NetWeaver 7.0 including Enhancement Package 1,2 and 3

SAP NetWeaver 7.3 including Enhancement Package 1

SAP NetWeaver 7.4

SAP NetWeaver 7.5

SAP NetWeaver AS for ABAP 7.51 innovation package

LifeKeeper SAP DB / MaxDB Recovery Kit steeleye-lkSAPDB-9.3.2-6863.noarch.rpm SAP MaxDB v7.6, v7.7, v7.8 and v7.9
LifeKeeper DB2 Recovery Kit steeleye-lkDB2-9.3.2-6863.noarch.rpm

IBM DB2 Universal Database v10.5 and v11.1

IBM DB2 Enterprise Server Edition (ESE) v10.5 and v11.1

IBM DB2 Workgroup Server Edition (WSE) v10.5 and v11.1

IBM DB2 Express Edition v10.5 and v11.1

LifeKeeper Oracle Recovery Kit steeleye-lkORA-9.3.2-6863.noarch.rpm

Oracle Database Standard Edition v11g R2 and v12c R2 (excluding ASM and pluggable database)

Oracle Database Enterprise Edition v11g R2, v12c and v12c R2 (excluding ASM and pluggable database)

Oracle Database Standard Edition One (SE1) v11g R2, v12c and v12c R2 (excluding ASM and pluggable database)

Oracle Database Standard Edition 2 (SE2) v12c and v12c R2 (except AWS EC2 system. See Known Issues and Restrictions > Oracle Recovery Kit. Also, excluding ASM and pluggable database)

LifeKeeper MySQL Recovery Kit steeleye-lkSQL-9.3.2-6863.noarch.rpm

MySQL and MySQL Enterprise v5.5, v5.6, v5.7 and v8.0

MariaDB v5.5 and v10.0

LifeKeeper PostgreSQL Recovery Kit

steeleye-lkPGSQL-9.3.2-6863.noarch.rpm

PostgreSQL v9.3, v9.4, v9.5,v9.6 and v10

EnterpriseDB Postgres Plus Advanced Server v9.3, v9.4 and v10.0

EDB Postgres Advanced Server v9.5、v9.6 and v10.0

LifeKeeper Sybase ASE Recovery Kit steeleye-lkSYBASE-9.3.2-6863.noarch.rpm Sybase ASE 15.7 and 16.0
LifeKeeper Postfix Recovery Kit steeleye-lkPOSTFIX-9.3.2-6863.noarch.rpm Postfix software provided with the supported Linux distributions installed and configured on each server. The same version of Postfix should be installed on each server.
LifeKeeper Samba Recovery Kit steeleye-lkSMB-9.3.2-6863.noarch.rpm Standard Samba file services provided with the supported Linux distributions
LifeKeeper NFS Server Recovery Kit steeleye-lkNFS-9.3.2-6863.noarch.rpm

Linux kernel version 2.6 or later

The NFS Server and client packages must be installed on SLES systems.

LifeKeeper Network Attached Storage Recovery Kit steeleye-lkNAS-9.3.2-6863.noarch.rpm NFS version of Mounted NFS file systems from an NFS server or Network Attached Storage (NAS) device v2, v3 and v4
LifeKeeper WebSphere MQ Recovery Kit steeleye-lkMQS-9.3.2-6863.noarch.rpm

WebSphere MQ v7.5

IBM MQ v8.0 and v9.0

See Known Issues and Restrictions > Installation.

Quick Service Protection steeleye-lkQSP-9.3.2-6863.noarch.rpm Quick Service Protection supplies functionality to easily protect OS services.

Features of LifeKeeper Single Server Protection

Product
Description
Temporal Recovery Logic Local recovery attempt limits can be set providing improved application availability.
Multi-Level Policies Recovery options can be specified at the server and resource levels allowing clients to define the most appropriate recovery strategy for each application.
Notification Only/Maintenance Mode Allows users to temporarily disable monitoring of one or more resources preventing LifeKeeper Single Server Protection from attempting to recover a resource that is undergoing maintenance.
VMware vSphere Integration Integrates with VMware’s vSphere platform to improve application availability while allowing organizations to realize the full benefits of server virtualization and automation. (VMware environments only)
vSphere Client Plug-in Centralized management and monitoring through the vSphere Client. (VMware environments only)
Product
Feature
New in Version 9.3.2
MQ SIOS Protection Suite for Linux now supports IBM MQ 9.1
LifeKeeper Core

Red Hat Enterprise Linux 7.6 is supported.

CentOS 7.6 is supported.

Oracle Linux Version 7.6 is supported.

SUSE Linux Enterprise Server 12 SP4 is supported.
SUSE Linux Enterprise Server 15 is supported.
Install The -s option for saving the current setup configuration has been added to the setup command.
PostgreSQL PostgreSQL 11 is supported.
EDB Postgres Advanced Server v11 is supported.
General Maintenance Bug fixes
New in Version 9.3.1
LifeKeeper Core

Upgated the OpenSSL package to 1.0.2p

Support Red Hat Enterprise Linux 6.10

Support CentOS 6.10

Support Oracle Linux 6 Update 10

MySQL Support MySQL 8.0
Oracle Support Oracle 18c (Certified in March 2019)
Install Bug fixes
New in Version 9.3
LifeKeeper Core

Red Hat Enterprise Linux Version 7.5 is supported.

CentOS7.5 is supported.

Oracle Linux Version 7.5 is supported.

Support VMware vSphere 6.7. (Certified in October 2018)

Bug fixes

Install The installation script has been renewed. For details, please click here.
Oracle, Samba, MQ, Sybase, Filesystem, Generic Application, QSP Bug fixes
New in Version 9.2.2
PostgreSQL

Support PostgreSQL 10

EDB Postgres Advanced Server v10.0 is now supported. (Certified in April 2018)

SAP,NAS Bug fixes
New in Version 9.2.1
LifeKeeper Core

Support Oracle Linux 7.4

Support CentOS 7.4

Support SUSE Linux Enterprise Server 12 SP3

  • The kernel should be updated to 4.4.82-6.9.1 for SUSE Linux Enterprise Server 12 SP3

    Bug fixes

PostgreSQL Support EDB Postgres Advanced Server 9.6
MQ Support IBM MQ 9.0
New in Version 9.2
LifeKeeper Core

Support Red Hat Enterprise Linux 7.4

SNMP trap can be sent to multiple targets

Virtualization environment Nutanix Acropolis Hypervisor is supported. (SPS is not supported)

Bug fixes

IP IP resources using real IP (primary IP address configured for NIC) can be created
PostgreSQL Support PostgreSQL 9.6
MQ Support IBM MQ 9.0 (Certified in December 2017)
SAP, SAP MaxDB, Route53, Install Bug fixes
New in Version 9.1.1
LifeKeeper Core

SUSE Linux Enterprise Server 12 SP1 support.

* SLES12.0 is not supported.

* Btrfs is not supported.

Red Hat Enterprise Linux Version 7.3 support.

Oracle Linux Version 7.3 support.

* UEK is not supported.

vSphere 6.5 support (SMC feature is no longer supported with vSphere 6.5).

Bug fixes

PostgreSQL PostgreSQL 9.5 support

EDB Postgres Advanced Server v9.5 support
For the details, refer to the SPS Optional Recovery Software Requirements, PostgreSQL Recovery Kit Administration Guide > Administration.

Sybase ASE Sybase ASE 16.0 support.
MySQL MySQL 5.7 support on RHEL 7.x/CentOS 7.x/OEL 7.x.

* MySQL 5.7 on other OS is already supported.

SAP SAP 7.5 support.
New in Version 9.1.0
LifeKeeper Core

Red Hat Enterprise Linux 6.8 support (Certified in September 2016).

CentOS 6.8, Oracle Linux 6.8 support (Certified in September 2016).

*MD RecoveryKit is not supported on these OS.

LifeKeeper API for Monitoring

Added API to supply LifeKeeper status and log information.

Quick Service Protection support

Added functionality to easily protect OS services.

Bug Fixes.

New in Version 9.0.2
LifeKeeper Core

Support of Red Hat Enterprise Linux Version 7.2.

※MySQL RK is not supporting RHEL 7.x/CentOS 7.x/OEL 7.x.

※Support of RHEL 7.2 by each application must be confirmed by user.

Update OpenSSL package to 1.0.1q

Bug Fixes.

MQ

WebSphere MQ – Added support for Multi-version WebSphere MQ. With this support queue managers for 7.1, 7.5, and 8.x can all be protected on the same cluster node.

Added the function that mqm group user can execute MQ command alternatively

Bug Fixes.

IP, Filesystem, DMMP, EC2, PostgreSQL, Power Path, SAP, SAP DB/MaxDB, Oracle Bug Fixes.
Licensing Update the package of FlexNet
New in Version 9.0.1
LikeKeeper Core Bug Fixes
DataKeeper Bug Fixes
New in Version 9.0
LifeKeeper Core

Combined documents of Parameters List, and added the lkchkconf command.

vSphere 6 support (SMC feature is no longer supported with vSphere 6.)

reiserfs filesystem is no longer supported.

Arks supported with Red Hat Enterprise Linux Version 7.0/7.1, Community ENTerprise Operating System (CentOS) Version 7.0/7.1, and Oracle Linux Version 7.0/7.1 are the same as LifeKeeper for Linux v8.4.1. (Arks to be applied: PostgreSQL, MySQL, Oracle, DB2, Apache, Postfix, NFS, NAS, Samba)

Bug Fixes.

GUI

JRE 8u51 support. (JRE 7 is no longer supported.)

Chrome Browser is no longer supported

Bug Fixes.

FileSystem, PostgreSQL Bug Fixes.

Bug Fixes

The following is a list of the latest bug fixes and enhancements.

Bug
Description
7367 A lib/ directory is added under /opt/LifeKeeper/lkadm/subsys/gen/app/ for Generic ARK
7368 Script with an extension can be found when creating generic resources
7384 xz-compressed kernel module is supported
7470 SYSLOG facility conflict is checked at the installation
7492 Unnecessary failover will not occur when SAPDB/MaxDB monitoring takes time
7493 A problem that the export information is deleted when NFS resource is started when a file system is full has been fixed
7495 The owner of files and directories of LifeKeeper products has been standardized to root user and root group
7502 Forced unmount in file system resources is ensured
7507 lksupport command obtains full /etc/hosts
7508 Output of /var/log/messages and journalctl is saved separately when obtaining lksupport
7517 A log when the PostgreSQL startup process hangs up is output to lifekeeper.log
7518 A problem that irrelevant processes in PostgreSQL resources may be killed (very rare) has been addressed
7526 sys user and sys group can no longer become an rpm package owner
7531 Reviewed the judgment process for a firewall startup at the time of installation
7537 A problem that LifeKeeper is launched incorrectly in systemd environment when upgrading using the setup script was fixed
7541 Anti-aliasing is used for LifeKeeper GUI fonts
7551 A conf.d directory of Apache is read
7556 An old syslog is no longer supported
7564 A description regarding OpenJDK support has been added to the setup script
7565 An incorrect branch of PostgreSQL instance startup determination has been fixed
7571 The logic to start and stop LifeKeeper in the setup command has been modified
7585 Communication path creation may fail when real IP’s are used
7593 The library libncurses5 required for the setup command will be installed automatically when it is not installed
7594 A link for libncurses5 has been changed from a static link to a dynamic link
7608 Fixed a problem that the lklogconfig fails to identify and configure logging
7637 Fixed a problem that LifeKeeper failed to start up when rebooting OS (very rare)
7668 Corrected a warning message when trying to install LifeKeeper with SELinux in Permissive Mode

System Requirements

LifeKeeper Single Server Protection Product Requirements

LifeKeeper Single Server Protection is supported on any Linux platform that satisfies the minimum requirements included in the table below.

Description
Requirement
Linux Operating System See the Linux Configuration Table for specific operating system information.
Virtual Environments

The guest operating system running on the virtual machine must be one of the supported versions listed in the Linux Configuration Table. The following virtual environment is an example where SIOS Protection Suite for Linux is deployed. Please refer to the Support Matrix for detailed versions of supported virtualization environments.

  • KVM

  • Oracle VM Server for x86

  • VMware vSphere v5, v5.1, v5.5, v6.0, v6.5 and v6.7

  • Amazon EC2

  • Nutanix Acropolis Hypervisor

    vSAN configuration is supported for vSphere 6.5 or later except RDM which is not supported by VMWare.

    Fibre channel SAN and shared SCSI cluster configurations are not supported with SPS for Linux running in a KVM and Oracle VM Server for x86 virtual machine.

Memory The minimum memory requirement for a system running LifeKeeper Single Server Protection is 512 MB. This is the minimum amount required by LifeKeeper Single Server Protection supported Linux distributions. System memory should be sized for the applications that will be running on the LifeKeeper Single Server Protection protected system as well.
Disk Space

The LifeKeeper Single Server Protection requires the following disk space:

/opt – approx 100000-105000 (1024-byte) disk blocks (depending on kits installed)

/ – approx 110000 (1024-byte) disk blocks

LifeKeeper Single Server Protection Support Software Requirements

The following table of Supporting Software is only required in VMware VMs configured for VM and Application Monitoring.

Product
Requirement(s)
Disk Space Required
VMware

VMware vSphere Client (for LifeKeeper Single Server Protection vSphere Client Plug-in functionality)

VMware Tools installed and running on all protected virtual machines

VMware Application HA monitoring must be enabled and set to VM and Application Monitoring for all protected virtual machines

Approximately 175 KB in /opt (for VMware Tools

Client Platforms and Browsers

The LifeKeeper Single Server Protection web client can run on any platform that provides support for Java Runtime Environment JRE8 update 51. The currently supported configurations are Firefox (Firefox 51 or earler) and Internet Explorer on Linux, Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016, Windows 7, Windows 8 or Windows 10 with JRE8 update 51. Other recent platforms and browsers will likely work with the SPS web client, but they have not been tested by SIOS Technology Corp. In addition, particular features of each browser also have not been tested.

IP addresses for LifeKeeper Single Server Protection components (e.g. the SteelEye Management Console and vCenter when installed in a VMware configuration) and protected Linux guests must be resolvable via DNS or the local hosts file (usually/etc/hosts or C:\windows\system32\drivers\etc\hosts). Using the local hosts file minimizes the client connection time and allows the client to connect even in the event of a Domain Name Server (DNS) failure.

Known Issues

See the Troubleshooting section in LifeKeeper Single Server Protection for Linux Technical Documentation for known issues, workarounds and other troubleshooting information.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment