Version 10.1
Released July 29, 2026
Read the following topics before attempting to install or use this product!
The documents contain 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.
Quick Links
| IMPORTANT NOTICES What’s New in this Release? Bug Fixes Security Updates 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 v10.1
v10.1.0 New Features
| LifeKeeper Core | Updated Perl version to 5.42.0. More information related to the Perl upgrade can be found here. |
| Add Powershell templates for generic application scripts | |
| Upgraded Java from v24.0.1 to v26.0.1 | |
| Upgraded Curl from v8.15.0 to v8.20.0 | |
| Recovery Kit for HULFT | “Recovery Kit for HULFT” has been released. It provides the same functionality as “Generic ARK for HULFT”, but reduces the effort required during setup. |
| Recovery Kit for Oracle Cloud Infrastructure | lksupport gathers information about RK for OCI. |
| Recovery Kit for Oracle Database | Support multiple SIDs for a single Oracle Home on Windows |
| Added support for protecting the OracleVssWriter service | |
| Support Oracle listener resource on Windows | |
| LifeKeeper Web Management Console (LKWMC) | Supports the operation of LifeKeeper Single Server Protection on LKWMC. |
Bug Fixes
The following is a list of the latest bug fixes and enhancements.
v10.1.0 Bug Fixes
| LifeKeeper Core |
PW-12839 | Fixed an issue that SOCKCA crashes |
| PW-18272 | Prevent random script failures. | |
| PW-18722 | Prevented certain Perl-related environment variables from affecting the system. | |
| PW-14981 | Fixed an issue where no debug was being collected and output for failed recovery kit action scripts, despite having an event viewer message for it. Now debug is collected for many scripts, and where it is not, the message is more clear. | |
| Recovery Kit for Oracle Cloud Infrastructure |
PW-17838 | Fixed an issue where OCIVIP resources could not be created on Windows Server 2025. |
| PW-16518 | Improve logging of RK for OCI. | |
| PW-15532 | Fixed an issue where non-existent network adapters were incorrectly identified as enabled. | |
| PL-16887 | Fixed an issue where warning messages on stderr from the OCICLI could cause OCIVIP resource creation and quickCheck to fail. | |
| Recovery Kit for Oracle Database | PW-17593 | Fixed the issue where resource creation failed if the database to be protected is not on a volume protected by LifeKeeper. |
| Recovery Kit for Microsoft SQL Server | PW-17593 | Fixed the issue where resource creation failed if the database to be protected is not on a volume protected by LifeKeeper. |
| Recovery Kit for Quick Service Protection | PW-18205 | “Use of uninitialized value in subroutine entry” warning no longer appears during successful QSP operations. |
Security Updates
v10.1.0 Security Updates
None.
Discontinued Features
v10.1.0 Discontinued Features
| Feature | Description |
|---|---|
| Recovery Kit for Microsoft SQL Server | Microsoft SQL Server 2016 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 Certification Information for supported Operating Systems. LifeKeeper Single Server Protection for Windows only supports 64-bit platforms (excluding x64 and Itanium). If you are using LifeKeeper for Windows on a system running Microsoft FTP Service 7.5 for IIS 7.0, Windows Server 2016 or later is required.
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 Certification Information 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 | See Certification Information |
| 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. For software requirements supported by Application Recovery Kits, refer to 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 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
Trademarks:
|
Post your comment on this topic.