Release Notes

Version 8.10.1

Released July 10, 2024

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.

To maintain the quality of our publications, we welcome your comments on their accuracy, clarity, organization and value.

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.

Quick Links

What’s New in this Release?
Bug Fixes
Discontinued Features
Single Server Requirements
System Requirements
Optional Recovery Kits
Technical Support

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 Supported Versions of LifeKeeper Single Server Protection for Windows v8

Feature
Description
New in This Release
LifeKeeper Core LifeKeeper for Windows now supports VMware vSphere 8.0 Update3 (Certified in Aug 2024).
Bundled Perl upgraded to v5.32.1.
Bundled OpenJDK upgraded to v21.0.2.
Bundled OpenSSL upgraded to v3.0.13.
Bundled Curl upgraded to v8.7.1.
Stop using Java RMISecurityManager.
LifeKeeper will now perform checks on child resources even when the parent resource is OSU.
Updated and enhanced the code signing for LifeKeeper binaries to provide additional security when deploying SIOS software.
PostgreSQL Server Recovery Kit LifeKeeper for Windows now supports PostgreSQL 17 (Certified in Nov 2024).
Recovery Kit for EC2™ Instance MetaData Service (IMDS) version 2 is now available for Amazon EC2 instances.
Oracle Recovery Kit Allow Oracle RK to use Windows Authentication.
Bug Fixes
New in Version 8.10.0
LifeKeeper Core LifeKeeper Single Server Protection for Windows now supports VMware vSphere 8.0 Update1 and Update2 (Certified in May 2024).
Load Balancer Health (LBHC) Check Recovery Kit Load Balancer Health Check (LBHC) is now available as an Application Recovery Kit, and is included when you install LifeKeeper for Windows v8.10.0.
Quick Service Protection Recovery Kit (QSP) The Quick Service Protection Recovery Kit is now available and is included when you install LifeKeeper for Windows v8.10.0.
  • If you are using LifeKeeper for Windows 8.10.0 or later you must use the new (built-in) Quick Service Protection Recovery Kit.
  • The existing QSP gen/app based Recovery Kit is not supported with v8.10.0.
  • SIOS will continue to support the QSP gen/app based Recovery Kit with v8.9.2 until June 30, 2026.
PostgreSQL Server Recovery Kit LifeKeeper for Windows now supports PostgreSQL 16. See the Support Matrix for supported configuration details.
LifeKeeper for Windows now supports EnterpriseDB PostgreSQL Advanced Server v16. See the Support Matrix for supported configuration details.
Bug Fixes
New in Version 8.9.2
LifeKeeper Core LifeKeeper Single Server Protection for Windows now supports Oracle Cloud
Support for VMware vSphere 8.0.
See the Support Matrix for supported configuration details.
PostgreSQL Server Recovery Kit LifeKeeper Single Server Protection for Windows now supports PostgreSQL 15. See the Support Matrix for supported configuration details.
LifeKeeper Single Server Protection for Windows now supports EnterpriseDB v15. See the Support Matrix for supported configuration details.
Bug Fixes
New in Version 8.9.1
LifeKeeper Core Stop supporting Windows operating systems older than Server 2012 and Client 10
Microsoft SQL Server 2022 Support (Certified in May 2023)
Bug Fixes
New in Version 8.9.0
LifeKeeper Single Server Protection for Windows Version 8.9.0 is the last version that will support Microsoft Windows Server 2008 R2 Enterprise and DataCenter Editions. It is currently only supported in Azure. Any subsequent releases will not support an install or upgrade for Microsoft Windows Server 2008 R2.
Bug Fixes
New in Version 8.8.2
LifeKeeper Core LifeKeeper Single Server Protection for Windows now supports Windows Server 2022
LifeKeeper Single Server Protection for Windows now supports Windows 11 OS
PostgreSQL Server Recovery Kit LifeKeeper Single Server Protection for Windows now supports PostgreSQL 14. See the Support Matrix for supported configuration details.
LifeKeeper Single Server Protection for Windows now supports EnterpriseDB v14. See the Support Matrix for supported configuration details.
Oracle Recovery Kit LifeKeeper Single Server Protection for Windows now supports Oracle 21c
New in Version 8.8.1
Bug Fixes
New in Version 8.8.0
Bug Fixes
New in Version 8.7.2
LifeKeeper Core LifeKeeper Single Server Protection for Windows now supports and includes OpenJDK 15
Support for VMware vSphere 7.0.
See the Support Matrix for supported configuration details.
PostgreSQL Recovery Kit LifeKeeper Single Server Protection for Windows now supports PostgreSQL 13.
See the Support Matrix for supported configuration details.
LifeKeeper Single Server Protection for Windows now supports PostgreSQL 12.
See the Support Matrix for supported configuration details.
LifeKeeper Single Server Protection for Windows now supports EnterpriseDB v13.
See the Support Matrix for supported configuration details.
Oracle Recovery Kit Support for Oracle Pluggable Databases
Bug Fixes

Bug Fixes

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

Description
PW-4551 Cache share settings are now saved and restored upon switchover/switchback.
PW-7297 IIS Recovery Kit now verifies site connectivity before resource recovery action completes.
PW-9289 Reduced the frequency of Route53 RK quickcheck logs.
PW-9391 Fixed an issue where lack of unnecessary IAM permissions could prevent ECC resource creation.
PW-9520 Allow protecting services with more special characters in the service name.

Discontinued Features of LifeKeeper Single Server Protection for Windows v8

Feature Description
Discontinued in This Release
Microsoft Windows Server 2012/2012 R2 are no longer supported on any version of LifeKeeper as of October 10, 2024.
Discontinued in v8.10.0
LifeKeeper Core Hyper-V 2012 R2 is no longer supported.
Windows Server 2012 and 2012 R2 Standard and DataCenter Editions are no longer supported with this version of LifeKeeper.
PostgreSQL Recovery Kit PostgreSQL 11 is no longer supported.
Discontinued in v8.9.2
None
Discontinued in v8.9.1
Windows Server 2008 R2 Enterprise and DataCenter Editions are no longer supported.
LifeKeeper Core Hyper-V Server 2008 R2 is no longer supported.
Microsoft SQL Server Recovery Kit Microsoft SQL Server 2008 R1 is no longer supported.
Microsoft SQL Server 2008 R2 is no longer supported.
Microsoft SQL Server 2012 is no longer supported.
PostgreSQL Recovery Kit PostgreSQL 10 is no longer supported.
Oracle Recovery Kit Oracle 12c is no longer supported.
Oracle 12c Release 2 is no longer supported.
Oracle 18c is no longer supported.
Discontinued in v8.9.0
PostgreSQL Recovery Kit PostgreSQL 9.6 is no longer supported
Oracle Recovery Kit Oracle 11g Release 2 is no longer supported
LifeKeeper Core Windows 7 is no longer supported
Windows 8 is no longer supported

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 LifeKeeper for Windows 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 LifeKeeper for Windows 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.

LifeKeeper System Requirements

Minimum Requirements
Memory 1 GB RAM
Processor Refer to Windows Server Processor Requirements
Disk size 750 MB required for install

Optional Recovery Kits

All optional LifeKeeper for Windows 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 LifeKeeper for Windows Support Matrix
Oracle Recovery Kit See the LifeKeeper for Windows Support Matrix

Client Platforms and Browsers

The currently supported configurations are Firefox (Firefox 51 or earlier) 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 LifeKeeper 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