LifeKeeper for Windows is an HA cluster software which is developed and delivered by SIOS Technology, Inc.. DataKeeper is a data replication software which is developed and delivered by SIOS Technology, Inc. DataKeeper provides an integrated data mirroring capability for LifeKeeper environments. This feature enables LifeKeeper resources to operate in shared and non-shared storage environments. SIOS Protection Suite for Windows includes SIOS LifeKeeper and SIOS DataKeeper. It integrates high availability clustering with innovative data replication functionality in a single, enterprise-class solution.
LifeKeeper for Windows supports creating an HA cluster system in a Google Cloud environment. LifeKeeper Windows on Google Cloud configures a cluster environment on VM instances of Google Compute Engine (hereafter referred to as the GCE). A client on Google Cloud can communicate with a VM instance which is detected as healthy using a health check by connecting to a frontend IP address of Cloud Load Balancing. This guide walks you through creating the following configurations as examples of using a cluster environment.
- LifeKeeper cluster node (two nodes cluster)
- Shared data space (using data mirroring through DataKeeper replication)
- Shared disk resource, Oracle DB, Oracle Listener resource
The contents of this document are based on the specifications of LifeKeeper for Windows and Google Cloud as of June, 2021. SIOS does not warrant the compatibility of these settings on future iterations of LifeKeeper for Windows and Google Cloud. Refer to the corresponding documentation as necessary and update your settings accordingly.
The configuration described in this guide assumes that there is only one frontend IP address of the load balancer and Oracle has an active/standby configuration.
The terms used in this document are described as follows.
|Resource||A system asset that can be protected by LifeKeeper. Resources can be used to represent disk partitions, virtual IP addresses, applications, etc.|
|Switchover||The planned migration of a resource hierarchy from the Active Server to the Standby Server.|
|Failover||The unplanned migration of a resource hierarchy to the Standby Server because of a system or resource failure on the Active Server.|
|Communication path||A mechanism supporting communication between nodes in a LifeKeeper cluster.|
|Active/Standby configuration||One of the HA cluster configurations. Either one of the cluster nodes can start all services.|
Post your comment on this topic.