Version 8.8.0

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 Windows (LKSSP) product. The document contains important information not detailed in the formal LifeKeeper Single Server Protection documentation set. 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. LifeKeeper Single Server Protection is built on the proven and stable architecture of SIOS LifeKeeper. LifeKeeper Single Server Protection for Windows provides superior application monitoring and can perform recovery of failed applications and system infrastructure items (e.g., IP address, File Share List). 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.

New Features of LifeKeeper Single Server Protection for Windows v8

Feature
Description
New in This Release
General maintenance Bug Fixes
New in Version 8.7.2
OpenJDK 15 LifeKeeper Single Server Protection for Windows now supports and includes OpenJDK 15
PostgreSQL 13 LifeKeeper Single Server Protection for Windows now supports PostgreSQL 13.
See the Support Matrix for supported configuration details.
PostgreSQL 12 LifeKeeper Single Server Protection for Windows now supports PostgreSQL 12.
See the Support Matrix for supported configuration details.
Oracle Pluggable Database Recovery Kit Support for Oracle Pluggable Databases
vSphere 7.0 Support for VMware vSphere 7.0.
See the Support Matrix for supported configuration details.
EnterpriseDB v13 LifeKeeper Single Server Protection for Windows now supports EnterpriseDB v13.
See the Support Matrix for supported configuration details.
General maintenance Bug Fixes

Bug Fixes

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

Description
PW-2284 emcmd . createjob should set shared volume configuration flags as appropriate
PW-2794 Handle volume dependencies when PDBS are added and removed
PW-2886 Warn users, and handle, missing and incorrectly initialized bitmap volumes
PW-2925 Additional Oracle support files gathered by lksupport script
PW-3241 EMTray doesn’t exit completely
PW-3702 LK-W GUI can pick up the wrong version of perl from system PATH

SSP for Windows Requirements

LifeKeeper Single Server Protection Software is bundled and runs on 64-bit systems (x86_64).

Product Operating Systems
LifeKeeper Single Server Protection for Windows

(Server Components)

See the SPS Support Matrix

64-bit versions (x64, no Itanium) of all of the listed OS platforms are supported.

Note: While installing LifeKeeper Single Server Protection for Windows 2008 R2, a dialog box will prompt whether the installer should make the system configuration changes described below. If the installer is not allowed to make these changes, they will need to be made manually after installation is complete.

  • Windows Firewall
  • The Distributed Link Tracking Client must be disabled

For systems running LifeKeeper Single Server Protection for Windows and Microsoft FTP Service 7.5 for IIS 7.0, Windows 2008 R2 or later is required.

In addition, if your Windows servers are not in a domain, the Local Security policy setting “Network Access: Let Everyone permissions apply to anonymous users” must be enabled. If the servers are in a domain, then this setting is not required.

LifeKeeper Single Server Protection for Windows

(User Interface)

See the SPS Support Matrix

MMC 3.0 – download from: https://download.cnet.com/Microsoft-Management-Console-3-0-for-Windows-XP-KB907265/3000-2206_4-10741230.html
Virtual Environments

The operating system versions listed above are supported for guests running on the following virtual platforms:

  • Amazon EC2 (AWS)
  • VMware vSphere 6.5, 6.7, 7.0 (Please see our Support Matrix for additional information on which versions are supported.)
  • Microsoft Hyper-V Server 2008 R2 or later
Memory The minimum memory requirement for a system supporting LifeKeeper Single Server Protection Suite for Windows is based on the memory requirements for the operating system being used. Additional memory is required to run user applications in addition to that required for LifeKeeper Single Server Protection Suite.
GUI Ports:

LifeKeeper Single Server Protection for Windows uses Port 82 for Remote Method Invocation (RMI) communication between the GUI server and client.

The LifeKeeper GUI uses Port 81 for its administration web server which should be different from any public web server. This is used by the GUI when run as a Java applet on a remote client.

In the event of conflict with an existing application, these ports can be changed by editing the RMI_PORT or WEB_PORT entries in the SIOS\LIFEKEEPER\JAVAGUI\SERVER registry key.

LifeKeeper Single Server Protection for Windows License One license is required for every server on which LifeKeeper Single Server Protection Suite runs. This applies to both physical and virtual servers.
LAN Manager Recovery Kit Requires the “File and Print Sharing for Microsoft Networks” component (lanmanserver) to be installed on the Windows server. NetBIOS must also be enabled. Otherwise, the LAN Manager resource will not come in service.

Optional Recovery Kits

All optional SIOS Protection Suite Recovery Kits require a software license key in order to function with LifeKeeper Single Server Protection for Windows.

Kit Name Versions/Requirement(s)
Microsoft SQL Server Recovery Kit See the SPS Support Matrix
Oracle Recovery Kit See the SPS Support Matrix

Client Platforms and Browsers

The currently supported configurations are Firefox (Firefox 51 or earler) and Internet Explorer on windows, 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 windows 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.

Technical Support

As a SIOS Technology Corp. customer with a valid Support contract, you are entitled to access the SIOS Technology Corp. Support Self-Service Portal.

The SIOS Technology Corp. Support Self-Service Portal offers you the following capabilities:

  • Search our Solution Knowledge Base to find solutions to problems and answers to questions
  • Always on 24/7 service with the SIOS Technology Corp. Support team to:
    • Log a Case to report new incidents.
    • View Cases to see all of your open and closed incidents.
    • Review Top Solutions providing information on the most popular problem resolutions being viewed by our customers.

Contact SIOS Technology Corp. Support at support@us.sios.com to set up and activate your Self-Service Portal account.

You can also contact SIOS Technology Corp. Support at:

1-877-457-5113 (Toll Free)

1-803-808-4270 (International)

Email: support@us.sios.com

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