Release Notes
Version 8.9.0
(Version 8 Update 9)
Released July 13, 2022
Important!!
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.
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
| |
|
| 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 | |
| |
|
| 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 |
| Bug Fixes | |
| Bug Fixes | |
| 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-3377 | When a new PDB resource hierarchy is about to be created using an Oracle SID which is already in use by the other PDB resource, LifeKeeper displays a warning message because it is not a recommended configuration. |
| PW-3647 | Virtual IP resource in AWS causes resource status update failures in lkGUIapp |
| PW-4482 | Updated FlexNet to 11.18 |
Discontinued Features of LifeKeeper Single Server Protection for Windows v8
| Feature | Description |
|---|---|
| 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 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.
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:
|
| 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
Post your comment on this topic.