Date: August 29, 2026
Tags: High Availability
Where Should HA “Live”? Matching Placement to Your Availability Targets
At a recent trade show, one question came up repeatedly: Where does SIOS LifeKeeper actually run?
The answer is important. LifeKeeper is installed directly on the operating system of each protected server. This placement gives it visibility into the application, its supporting resources, and the dependencies required to keep the workload available.
This differs from relying solely on HA at the infrastructure or container layer.
Different Layers See Different Failures
Hypervisor-level HA can detect a failed physical host and restart its virtual machines elsewhere. Container orchestration platforms can replace failed containers or move workloads between nodes.
These capabilities provide valuable protection, but they operate from outside the application. A virtual machine can still be running while the database inside it has hung or the web service has crashed. Likewise, a container may be restarted without fully addressing problems involving data, storage, networking, or dependent services.
The layer providing HA determines what failures it can see and how precisely it can respond.
Why On-System HA Provides Deeper Protection
Because LifeKeeper runs within the operating system, it can monitor the health of the actual application environment, not simply the server, virtual machine, or container hosting it.
This enables LifeKeeper to:
● Monitor application processes and supporting resources
● Understand relationships between applications, storage, networking, and other dependencies
● Detect application-level failures that infrastructure monitoring may miss
● Coordinate recovery and failover in the correct sequence to ensure data integrity
● Move the complete application environment to a healthy system
This application-aware approach helps reduce the gap between “the server is running” and “the application is available.”
Placement Should Match the Availability Target
Where HA lives should be determined by what must remain available.
If the goal is primarily to recover from hardware or host failures, infrastructure-level HA may be sufficient. If the availability target applies to a business-critical application and its data, protection closer to the application provides greater visibility and more targeted recovery.
These approaches do not have to be mutually exclusive. Infrastructure, container, and application-level HA can work together as layers of protection. The key is understanding what each layer monitors and where responsibility for recovery begins and ends.
The closer an HA solution is to the application, the more context it has when something goes wrong. For organizations with demanding SLAs and strict RTO/RPO targets, that context can make the difference between restarting infrastructure and restoring the service users actually depend on.
Ready to close the availability gap in your environment? Contact our team to learn how SIOS LifeKeeper can help you meet your most critical uptime targets.
Author: Ben Roy, Marketing Programs Specialist at SIOS
Reproduced with permission from SIOS