Search
Related topics are listed below.
AWS Direct Connect Quick Start Guide
Quick Start Guides » AWS Direct Connect Quick Start Guide
Objective Starting in v9.2, LifeKeeper supports a connection from an on-premises environment using AWS Direct Connect to HA cluster nodes in Amazon VPC. Connection from other VPC through VPC peer connection is also supported. This allows you to use services protected…
AWS Direct Connect Requirements
Quick Start Guides » AWS Direct Connect Quick Start Guide » AWS Direct Connect Requirements
The following is a summary of requirements that should be met for an AWS environment and instances created on it. Requirements for AWS Environment Create a base environment on AWS to provide services. The requirements for using this configuration are as…
AWS Direct Connect Preparations
Quick Start Guides » AWS Direct Connect Quick Start Guide » AWS Direct Connect Setup Procedure » AWS Direct Connect Preparations
Create an environment that satisfies Requirements. Install LifeKeeper on each instance and create a communication path between Node1 and Node2. Confirm that you can access from your on-premises environment or other VPC environment to ENI’s private address…
AWS Direct Connect Setup Procedure
Quick Start Guides » AWS Direct Connect Quick Start Guide » AWS Direct Connect Setup Procedure
This section describes the general procedure to setup the environment shown below.
AWS VPC Peering Connections Quick Start Guide
Quick Start Guides » AWS VPC Peering Connections Quick Start Guide
Objective This document descries the requirements and basic operations for building connections among VPCs with LifeKeeper for Linux v9.3.1. You can also build HA clusters in the AWS environment using the existing Recovery Kit for EC 2; however, you cannot connect…
Creating Direct Connect Resources
Quick Start Guides » AWS Direct Connect Quick Start Guide » AWS Direct Connect Setup Procedure » Creating Direct Connect Resources
Creating an IP Resource Create an IP resource: not a virtual IP resource but a real IP resource (Note: resource for a primary IP address configured for NIC). Specify an ENI private IP address when creating a resource. Also, specify an ENI private IP address for…
Quick Start Guides
Quick Start Guides
AWS Direct Connect Quick Start Guide Protection Suite for Linux in the AWS Cloud (SAP) SAP HANA 1.0 Recovery Kit SAP HANA 2.0 Recovery Kit Chef Support Documentation AWS VPC Peering Connections Quick Start Guide DataKeeper for Linux Evaluation Guide MySQL…
Considerations for Settings and Operations in AWS Direct Connect
Quick Start Guides » AWS Direct Connect Quick Start Guide » Considerations for Settings and Operations in AWS Direct Connect
Considering the Use of LifeKeeper I-O Fencing Since the shared disk environment cannot be used in an AWS environment, you cannot use SCSI reservations to prevent a split-brain. IP resources may cause a split-brain as it uses the real IP resource with different IP…
Cluster Connect Dialog
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Using LifeKeeper for Linux » Common Tasks » Cluster Connect Dialog
Server Name. The name of the server to which you want to connect. Login. The login name of a user with LifeKeeper authorization on the server to which you want to connect. Password. The password that authorizes the specified login on the server to which you want…
AWS VCP Peering Requirements for AWS Environment
Quick Start Guides » AWS VPC Peering Connections Quick Start Guide » AWS VCP Peering Connections Requirements » AWS VCP Peering Requirements for AWS Environment
You need to install the same version of LifeKeeper software and patches on each server. The Application Recovery Kit (ARK) required for this configuration is shown below. For the specific LifeKeeper requirements, please refer to: SPS for Linux Technical Documentation…
Before You Start
SIOS Protection Suite for Linux Technical Documentation » DataKeeper » SIOS Protection Suite for Linux Multi-Site Cluster » Migrating to a Multi-Site Cluster Environment » Before You Start
The following image depicts a file system resource hierarchy prior to performing a migrate.
Other AWS VCP Requirements
Quick Start Guides » AWS VPC Peering Connections Quick Start Guide » AWS VCP Peering Connections Requirements » Other AWS VCP Requirements
Requirements for using this service from other VPCs are as follows: Clients using the service should be able to resolve names of the hosts that are protected by Route53 resources. Clients using the service should access with the host name protected by Route53…
Configuration 2 – Direct Mounts
Application Recovery Kits » WebSphere MQ Recovery Kit Administration Guide » WebSphere MQ Configuration Considerations » MQ Configuration Requirements » MQ Supported File System Layouts » Configuration 2 – Direct Mounts
In this configuration, the QMDIR and the QMLOGDIR directories are located on shared storage. This requires two dedicated LUNS or partitions or the use of LVM for each queue manager. If LVM is used, two logical volumes from the same LUN can be created and separately…
AWS VCP Peering Connections Requirements
Quick Start Guides » AWS VPC Peering Connections Quick Start Guide » AWS VCP Peering Connections Requirements
Some requirements should be met when using this configuration. Below is a summary of requirements for the AWS environment and instances created on it. Requirements for AWS environment Create a base environment on AWS to provide services. The requirements for using…
AWS VCP Peering Setup Procedure
Quick Start Guides » AWS VPC Peering Connections Quick Start Guide » AWS VCP Peering Setup Procedure
In this section, a general procedure to setup the environment shown as the figure below Preparations Create an environment that satisfies Requirements. Please install LifeKeeper on each instance and create a communication path between Node1 and Node2 (or Node2’).…
Install, Configure, and Start MySQL
Quick Start Guides » MySQL Cluster with Data Replication (“Shared Nothing” Cluster) » Install, Configure, and Start MySQL
Primary Server On your Primary server, perform the following actions: Install both the “mysql” and “mysql-server” rpm packages if they do not exist on your system. Apply any required dependencies as well # yum install mysql mysql-server Verify…
Install, Configure, and Start PostgreSQL
Quick Start Guides » PostgreSQL Cluster with Shared Storage (ISCSI) » Install, Configure, and Start PostgreSQL
Primary Server On your Primary server, perform the following actions: Install both the “postgresql-server” and “postgresql” rpm packages if they do not exist on your system. Apply any required dependencies as well # yum install postgresql…
Quick Service Protection Kit Message Catalog
Search for an Error Code » Combined Message Catalog » Quick Service Protection Kit Message Catalog
Use Control F to search for a specific error code in each catalog. To search for any error code, select the Search button at the top right of the screen. …
Quick Service Protection (QSP) Recovery Kit
LifeKeeper Single Server Protection Technical Documentation » Administration » Quick Service Protection (QSP) Recovery Kit
The QSP Recovery Kit provides a simplified method to protect the OS service. With the QSP Recovery Kit users can easily create a LifeKeeper resource instance to protect an OS service provided that service can be started and stopped by the OS service command. The…
Quick Service Protection (QSP) Recovery Kit
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » LifeKeeper Administration Overview » Administrator Tasks » Creating Resource Hierarchies » Quick Service Protection (QSP) Recovery Kit
The QSP Recovery Kit provides a simplified method to protect the OS service. With the QSP Recovery Kit users can easily create a LifeKeeper resource instance to protect an OS service provided that service can be started and stopped by the OS service command. The…
Related LifeKeeper Resources for AWS VCP Peering
Quick Start Guides » AWS VPC Peering Connections Quick Start Guide » Related LifeKeeper Resources for AWS VCP Peering
Route53 Resource Summary When switchover occurs, it is necessary to update Amazon Route 53 DNS information in order to continue to secure the connection to the service. This feature is provided in Route53 resources. When the status of Route53 resource becomes “In…
AWS VCP Peering Known Issues and Troubleshooting
Quick Start Guides » AWS VPC Peering Connections Quick Start Guide » Considerations for Settings and Operations in AWS VCP Peering » AWS VCP Peering Known Issues and Troubleshooting
There is no information at the time of the release of LifeKeeper for Linux v9.3.1
Install, Configure, and Start MySQL – Apache
Quick Start Guides » Apache/MySQL Cluster Using Both Shared and Replicated Storage » Install, Configure, and Start MySQL – Apache
Primary Server On your Primary server, perform the following actions: Install both the “mysql” and “mysql-server” rpm packages if they do not exist on your system. Apply any required dependencies as well # yum install mysql mysql-server Verify…
Considerations for Settings and Operations in AWS VCP Peering
Quick Start Guides » AWS VPC Peering Connections Quick Start Guide » Considerations for Settings and Operations in AWS VCP Peering
Considering the Use of LifeKeeper I-O Fencing – AWS VCP Peering AWS VCP Peering Known Issues and Troubleshooting
SIOS Protection Suite for Linux in the AWS Cloud (SAP)
Quick Start Guides » SIOS Protection Suite for Linux in the AWS Cloud (SAP)
Overview This document will guide the user during SIOS Protection Suite for Linux installation (SPS). Follow the quick decision matrix to understand how to install SPS for SAP environment. Note: The link above is provided here so it can be…
Considering the Use of LifeKeeper I-O Fencing – AWS VCP Peering
Quick Start Guides » AWS VPC Peering Connections Quick Start Guide » Considerations for Settings and Operations in AWS VCP Peering » Considering the Use of LifeKeeper I-O Fencing – AWS VCP Peering
Since the shared disk environment cannot be used in AWS environment, you cannot use SCSI reservations to prevent a split-brain. Also, IP resource may cause the split-brain as it uses the real IP resource with different IP addresses for each node. For this reason,…
Additional Resources
Quick Start Guides » SIOS Protection Suite for Linux in the AWS Cloud (SAP) » Switchover and Failover Testing » Additional Resources
AWS services Amazon EC2 https://aws.amazon.com/documentation/ec2/ AWS CloudFormation https://aws.amazon.com/documentation/cloudformation/ Amazon VPC https://aws.amazon.com/documentation/vpc/ SIOS Protection Suite for Linux Step-By-Step: How to configure…
Additional Steps to Configure SAP on SPS
Quick Start Guides » SIOS Protection Suite for Linux in the AWS Cloud (SAP) » Additional Steps to Configure SAP on SPS
Follow the steps below to configure SAP on SPS. Step 1. Test the Deployment To connect to the SPS-L nodes, you need to connect to Windows jumpbox. To connect to a Windows machine, you need to connect to remote desktop terminal. In AWS console, select the windows…
Creating the SAP Resource Hierarchy – Separate Instances
Quick Start Guides » SIOS Protection Suite for Linux in the AWS Cloud (SAP) » ASCS + ERS with NFS on Separate Instances » Creating the SAP Resource Hierarchy – Separate Instances
From the LifeKeeper GUI menu, select Edit, then Server. From the drop-down menu, select Create Resource Hierarchy. A dialog box will appear with a drop-down list box with all recognized recovery kits installed within the cluster. Select SAP from the drop-down…
Creating the SAP Resource Hierarchy – Same Instances
Quick Start Guides » SIOS Protection Suite for Linux in the AWS Cloud (SAP) » ASCS + ERS with NFS on the Same Instance as ASCS » Creating the SAP Resource Hierarchy – Same Instances
From the LifeKeeper GUI menu, select Edit, then Server. From the drop-down menu, select Create Resource Hierarchy. A dialog box will appear with a drop-down list box with all recognized recovery kits installed within the cluster. Select SAP from the drop-down…
Route53 Parameters List
Parameters List » Route53 Parameters List
The table below lists and explains the tunable values that are available for modifying the behavior of the Route53 Recovery Kit. These values are set by adding the /etc/default/LifeKeeper configuration file. Because none of the components of the Route53 Recovery Kit…
EC2 Parameters List
Parameters List » EC2 Parameters List
The table below lists the EC2 parameters. These values are set by adding them to the /etc/default/LifeKeeper configuration file. Because none of the components of the Recovery Kit for EC2 are memory resident, changes to these particular values become effective…
How to Make Existing Resources Support an IAM Role
Application Recovery Kits » Recovery Kit for EC2 Administration Guide » How to Make Existing Resources Support an IAM Role
Stating with v9.2.2 LifeKeeper supports the use of an IAM role Prior to v9.2.2, it was necessary to enter the AWS access key (access key ID and secret access key) when creating EC2 and Route53 resources, but if you create these resources after granting access privilege…
Connecting Servers to a Cluster
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Using LifeKeeper for Linux » Common Tasks » Connecting Servers to a Cluster
There are two possible ways to begin. On the Global Toolbar, click the Connect button. On the File Menu, click Connect. In the Server Name field of the Cluster Connect dialog, enter the name of a server within the cluster to which you want to…
Creating an NFS Resource Hierarchy – Separate Instances
Quick Start Guides » SIOS Protection Suite for Linux in the AWS Cloud (SAP) » ASCS + ERS with NFS on Separate Instances » Creating an NFS Resource Hierarchy – Separate Instances
You will need to repeat these steps to create multiple resource hierarchies for multiple NFS shares. To create a resource instance from the primary server, you should complete the following steps: From the LifeKeeper GUI menu, select Edit, then Server. From the…
Creating an NFS Resource Hierarchy – Same Instances
Quick Start Guides » SIOS Protection Suite for Linux in the AWS Cloud (SAP) » ASCS + ERS with NFS on the Same Instance as ASCS » Creating an NFS Resource Hierarchy – Same Instances
You will need to repeat these steps to create multiple resource hierarchies for multiple NFS shares. To create a resource instance from the primary server, you should complete the following steps: From the LifeKeeper GUI menu, select Edit, then Server. From the…
Using External Snapshot Functions for Disks and Devices Protected by DataKeeper
SIOS Protection Suite for Linux Technical Documentation » DataKeeper » Using External Snapshot Functions for Disks and Devices Protected by DataKeeper
Full synchronization is required when using a snapshot process to restore data to a disk or device that is actively protected by DataKeeper. Snapshot capability referred to in this document includes: Snapshots provided by cloud environment services such as…
Changing LifeKeeper WebSphere MQ Recovery Kit Defaults
Application Recovery Kits » WebSphere MQ Recovery Kit Administration Guide » LifeKeeper Configuration Tasks for MQ » Editing MQ Configuration Resource Properties » Changing LifeKeeper WebSphere MQ Recovery Kit Defaults
The IBM WebSphere MQ Recovery Kit uses a number of default values which can be tuned and modified if you have problems with the default settings. The default settings should be sufficient for most environments. If you have problems with timeouts you can use the…
Running the GUI on a LifeKeeper Server
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Using LifeKeeper for Linux » GUI » Preparing to Run the GUI » Running the GUI on a LifeKeeper Server
The simplest way to run the LifeKeeper GUI is as an application on a LifeKeeper server. By doing so you are, in effect, running the GUI client and server on the same system. After configuring the LifeKeeper server for GUI Administration, you can run the GUI as an…
Route53 Recovery Kit Requirements
Application Recovery Kits » Route53 Recovery Kit Administration Guide » Route53 Recovery Kit Requirements
Prior to installing and configuring the Route53 Recovery Kit, be sure your configuration meets the following requirements. AWS Command Line Interface (AWS CLI) must be installed on all EC 2 instances. Refer to Installing AWS Command Line Interface” for…
MQ Parameters List
Parameters List » MQ Parameters List
The table below lists and explains names and meanings of the MQ parameters. These values are tuned by editing the /etc/default/LifeKeeper configuration file. Parameter Name Meaning Setting Value Default Value When to Apply Notes…
Recovery Kit for EC2 Requirements
Application Recovery Kits » Recovery Kit for EC2 Administration Guide » Recovery Kit for EC2 Requirements
Before attempting to install or remove the Recovery Kit for EC2 you must understand Amazon Web Service software requirements, as well as the installation and removal procedures for the Recovery Kit for EC2 package. Amazon Web Service and Software Requirements Before…
Application Configuration
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » Installation and Configuration » Application Configuration
Item Description Database Initialization Files The initialization files for databases need to be either on a shared device and symbolically linked to specified locations in the local file system or kept on separate systems and manually…
Browser Security Parameters for GUI Applet
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Using LifeKeeper for Linux » GUI » Preparing to Run the GUI » Browser Security Parameters for GUI Applet
!WARNING: Be careful of other sites you visit with security set to low values. Firefox From the Edit menu, select Preferences. In the Preferences dialog box, select Content. Select the Enable Java and Enable Java Script options. Click Close. Internet…
EC2 Resource Monitoring and Configuration
Application Recovery Kits » Recovery Kit for EC2 Administration Guide » Recovery Kit for EC2 Configuration » EC2 Resource Monitoring and Configuration
Route Table scenario (Backend Cluster): The recovery kit uses AWS CLI to perform the monitoring of the Route Table settings to enable an access from clients within the VPC to the protected IP resources. The recovery kit ensures that the target of the IP resources for…
Create the ERS Resource – Separate Instances
Quick Start Guides » SIOS Protection Suite for Linux in the AWS Cloud (SAP) » ASCS + ERS with NFS on Separate Instances » Create the ERS Resource – Separate Instances
The ERS resource provides additional protection against a single point of failure of a Core Instance (Central Services Instance) or enqueue server process. When a Core Instance (Central Services Instance) fails and is restarted, it will retrieve the current status of…
Create the ERS Resource – Same Instances
Quick Start Guides » SIOS Protection Suite for Linux in the AWS Cloud (SAP) » ASCS + ERS with NFS on the Same Instance as ASCS » Create the ERS Resource – Same Instances
The ERS resource provides additional protection against a single point of failure of a Core Instance (Central Services Instance) or enqueue server process. When a Core Instance (Central Services Instance) fails and is restarted, it will retrieve the current status of…
Configure the Cluster – DK for Linux
Quick Start Guides » DataKeeper for Linux Evaluation Guide » Configure the Cluster – DK for Linux
Primary Server Complete the following steps on the primary server to configure the cluster: Create TCP Communication (Comm) Path(s) Verify the Communication (Comm) Path(s) Before you begin, SIOS recommends at least two TCP communications paths between each…
Specific Configuration Considerations for Oracle
Application Recovery Kits » Oracle Recovery Kit Administration Guide » Configuring Oracle with LifeKeeper » Specific Configuration Considerations for Oracle
*If you plan to use Oracle with Raw I/O, the Raw I/O devices must be properly set up prior to use. See the Appendix for instructions. (Raw I/O is not an option for LifeKeeper Single Server Protection.) Before configuring the Oracle Recovery Kit, complete the following…
SPS Configuration Steps
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » Installation and Configuration » SPS Configuration Steps
If you have installed your SPS environment as described in the SPS Installation Guide, you should be ready to start and configure the SPS software on each server in your cluster. Follow the steps below which contain links to topics with additional details. Perform…
Switchover and Failover Testing
Quick Start Guides » SIOS Protection Suite for Linux in the AWS Cloud (SAP) » Switchover and Failover Testing
The steps below are for testing the switchover and failover of a SIOS cluster for SAP. Open “SAP Logon” or “SAP GUI for Windows”, which is an SAP supplied Windows client. The program can be downloaded from the SAP download site. The virtual IP…
Configuration Considerations for All DB2 Configurations
Application Recovery Kits » DB2 Recovery Kit Administration Guide » Configuring the LifeKeeper for Linux DB2 Recovery Kit » Configuration Considerations for All DB2 Configurations
DB2 instance names should contain alphanumeric characters only. DB2 clients should be configured to connect to the database via a LifeKeeper protected IP address. Users can define: DB2SYSTEM=” in $instancehome/sqllib/profile.env and catalog the floating IP…
Software RAID Notes and Restrictions
Application Recovery Kits » MD Recovery Kit Administration Guide » Software RAID (md) Recovery Kit Overview » Software RAID Notes and Restrictions
The following notes and restrictions apply to this version of the Software RAID Recovery Kit. Activating Virtual Devices During Boot Up Virtual devices on shared storage should not be activated during system boot-up. Persistent Superblock All virtual devices must…
Configure the Cluster
Quick Start Guides » MySQL Cluster with Data Replication (“Shared Nothing” Cluster) » Configure the Cluster
Primary Server Complete the following steps on the primary server to configure the cluster: Create TCP Communication (Comm) Path(s) Verify the Communication (Comm) Path(s) Before you begin, SIOS recommends at least two TCP communications paths between each server…
inqfail error in the LifeKeeper Log
Application Recovery Kits » Oracle Recovery Kit Administration Guide » Oracle Troubleshooting » Oracle Known Issues and Restrictions » inqfail error in the LifeKeeper Log
If an inqfail error appears in your LifeKeeper error log following a failover, you will need to change the filesystemio setting. Note: The disk id and server name will be different for each configuration. To resolve this problem, you will need to change the setting…
Configure the Cluster – PostgreSQL
Quick Start Guides » PostgreSQL Cluster with Shared Storage (ISCSI) » Configure the Cluster – PostgreSQL
Primary Server Complete the following steps on the primary server to configure the cluster: Create TCP Communication (Comm) Path(s) Verify the Communication (Comm) Path(s) Before you begin, SIOS recommends at least two TCP communications paths between each server…
PostgreSQL General Tips
Application Recovery Kits » PostgreSQL Recovery Kit Administration Guide » PostgreSQL Troubleshooting » PostgreSQL General Tips
The following error messages and conditions may be encountered while using the recovery kit. Error Solution Unable to protect PostgreSQL database using the same port as another LK protected PostgreSQL database. Verify the version of…
Creating an EC2 Resource Hierarchy
Application Recovery Kits » Recovery Kit for EC2 Administration Guide » Recovery Kit for EC2 Configuration » Creating an EC2 Resource Hierarchy
To create a resource instance from the primary server, complete the following steps: From the LifeKeeper GUI menu, select Edit, then Server. From the drop down menu, select Create Resource Hierarchy. A dialog box will appear with a drop down list showing all of…
Standby Node Health Check
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » Installation and Configuration » Standby Node Health Check
Overview The Standby Node Health Check feature allows you to monitor CPU and memory utilization on the standby node and monitor the health of out-of-service resources to detect errors on the standby node. This allows for issues to be resolved in advance, reducing the…
Postfix Resource In-Service / Out-of-Service / Health Monitoring Error Messages
Application Recovery Kits » Postfix Recovery Kit Administration Guide » Postfix Troubleshooting » Postfix Resource In-Service / Out-of-Service / Health Monitoring Error Messages
Error Error Message Master process of postfix is not running The master process of Postfix is not running. Please check the Postfix error log. Failed in a check by postfix command Postfix command check option has failed.…
Set Up TTY Connections
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » Installation and Configuration » SPS Configuration Steps » Set Up TTY Connections
If you plan to use a TTY communications (comm) path for a LifeKeeper heartbeat, you need to set up the physical connection for that heartbeat. Remember that multiple communication paths are required to avoid false failover due to a simple communications failure. Two or…
Running the GUI on a Remote System
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Using LifeKeeper for Linux » GUI » Preparing to Run the GUI » Running the GUI on a Remote System
You may administer LifeKeeper from a Linux, Unix or Windows system outside the LifeKeeper cluster by running the LifeKeeper GUI as a Java applet. Configuring and running the GUI in this environment is described below. Configuring the GUI on a Remote System In order…
GUI – Known Issues / Restrictions
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » Troubleshooting » Known Issues and Restrictions » GUI – Known Issues / Restrictions
Description GUI login prompt may not re-appear when reconnecting via a web browser after exiting the GUI When you exit or disconnect from the GUI applet and then try to reconnect from the same web browser session, the login prompt may not…
Client Configuration Considerations for MySQL
Application Recovery Kits » MySQL Recovery Kit Administration Guide » MySQL Recovery Kit Configuration » Client Configuration Considerations for MySQL
Following are some configuration considerations for MySQL database clients: If clients will connect from remote hosts, create an IP address under LifeKeeper to be used for client connections. Clients must be configured to connect to the database server through a…
Creating a File System Resource Hierarchy
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » LifeKeeper Administration Overview » Administrator Tasks » Creating Resource Hierarchies » Creating a File System Resource Hierarchy
Use this option to protect a file system only (for example, if you have shared files that need protection). There are four ways to begin creating a file system resource hierarchy. º Right-click on a server icon to bring up the server context menu, then click…
Configure the Cluster – Apache
Quick Start Guides » Apache/MySQL Cluster Using Both Shared and Replicated Storage » Configure the Cluster – Apache
Primary Server Complete the following steps on the primary server to configure the cluster: Create TCP Communication (Comm) Path(s) Verify the Communication (Comm) Path(s) Before you begin, SIOS recommends at least two TCP communications paths between each server…
Network Related Troubleshooting (GUI)
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » Troubleshooting » GUI Troubleshooting » Network Related Troubleshooting (GUI)
LifeKeeper uses Java RMI (Remote Method Invocation) for communications between GUI clients and servers. Some potential problems may be related to RMI, and others are general network configuration problems. Long Connection Delays on Windows Platforms From Sun…
File Menu
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Using LifeKeeper for Linux » GUI » Menus » File Menu
Connect. Connect to a LifeKeeper cluster. Connection to each server in the LifeKeeper cluster requires login authentication on that server. Exit. Disconnect from all servers and close the GUI window.
IP Recovery Kit Configuration Examples
Application Recovery Kits » IP Recovery Kit Administration Guide » IP Recovery Kit Configuration » IP Recovery Kit Configuration Examples
This topic identifies example network configurations and then describes two sample IP configuration exercises. The first example illustrates a typical case of a database application dependent upon a single IP resource and configured on a pre-existing subnet. The second…
Starting and Stopping the GUI Server
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Using LifeKeeper for Linux » GUI » Preparing to Run the GUI » Starting and Stopping the GUI Server
To Start the LifeKeeper GUI Server If the LifeKeeper GUI Server is not running, type the following command as root: /opt/LifeKeeper/bin/lkGUIserver start This command starts all LifeKeeper GUI Server daemon processes on the server being administered if they are not…
Common Hardware Components
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » SIOS LifeKeeper for Linux Introduction » Configuration Concepts » Common Hardware Components
All LifeKeeper configurations share these common components: Server groups. The basis for the fault resilience provided by LifeKeeper is the grouping of two or more servers into a cluster. The servers can be any supported platform running a supported distribution of…
IP Recovery Kit Principles of Operation
Application Recovery Kits » IP Recovery Kit Administration Guide » IP Recovery Kit Principles of Operation
LifeKeeper brings an IP resource into service by creating an IP alias address on one of the physical network interfaces on the primary server. Users connect to the node using this alias address. The IP Recovery Kit software performs checks to help ensure that the…
Password Dialog
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Dialogs » Password Dialog
This dialog is displayed if the initial login name or password entered in the Cluster Connect dialog is invalid. Login. The login name of a user with LifeKeeper authorization on the specified server. Password. The password that authorizes the specified login on…
Testing MQ Client Connectivity
Application Recovery Kits » WebSphere MQ Recovery Kit Administration Guide » LifeKeeper Configuration Tasks for MQ » Testing a WebSphere MQ Resource Hierarchy » Testing MQ Client Connectivity
Testing Client Connectivity To test client connectivity, perform the following steps: On the primary server, use the amqsbcgc command to connect to the queue manager: export MQSERVER=‘SYSTEM.DEF.SVRCONN/TCP/192.168.1.90(1414)’ Note: Replace the IP…
SMC Troubleshooting
LifeKeeper Single Server Protection Technical Documentation » Troubleshooting » SMC Troubleshooting
See below for troubleshooting hints and tips. LifeKeeper Single Server Protection monitored guest virtual machines must have VMware Tools installed. LifeKeeper Single Server Protection is unable to completely connect to virtual machines that do not…
EC2 Principles of Operation
Application Recovery Kits » Recovery Kit for EC2 Administration Guide » EC2 Principles of Operation
Recovery Kit for EC2 provides two functions. The Route Table scenario (Backend Cluster) manages Route Table for LifeKeeper-protected IP resources to be reached from clients within the Amazon VPC™. The Elastic IP scenario (Frontend Cluster) manages Elastic IP…
MQ Configuration Requirements
Application Recovery Kits » WebSphere MQ Recovery Kit Administration Guide » WebSphere MQ Configuration Considerations » MQ Configuration Requirements
The section Configuring WebSphere MQ for Use with LifeKeeper contains a process for protecting a queue manager with LifeKeeper. In general, the following requirements must be met to successfully configure a WebSphere MQ queue manager with LifeKeeper: Configure…
MQ Recovery Kit Features
Application Recovery Kits » WebSphere MQ Recovery Kit Administration Guide » WebSphere MQ Recovery Kit Overview » MQ Recovery Kit Features
The WebSphere MQ Recovery Kit provides the following features: Supports mult-instance Queue Managers (queue managers created with multiple versions of MQ software) Supports Active/Active configurations Supports LINEAR and CIRCULAR logging (detected…
OSU Resource Monitoring
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » Installation and Configuration » Standby Node Health Check » OSU Resource Monitoring
For each out-of-service (OSU) resource, lkcheck periodically calls the OSUquickCheck script for the resource. The OSUquickCheck script performs a quick health check for the resource. If it determines that the resource cannot start successfully, it changes the state of…
Resource Error Recovery Scenario
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » SIOS LifeKeeper for Linux Introduction » Fault Detection and Recovery Scenarios » Resource Error Recovery Scenario
LifeKeeper provides a real-time daemon monitor, lkcheck, to check the status and health of LifeKeeper-protected resources. For each in-service resource, lkcheck periodically calls the quickCheck script for that resource type. The quickCheck script performs a quick…
Install the PostgreSQL Software
Application Recovery Kits » PostgreSQL Recovery Kit Administration Guide » PostgreSQL Installation » Install the PostgreSQL Software
Install the PostgreSQL software on all servers in the cluster using identical parameters/settings. Refer to the PostgreSQL Administration Guide for details. The following are additional recommendations and reminders to ensure that LifeKeeper will work with…
tcp_remote Mode
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » Installation and Configuration » LifeKeeper I/O Fencing Introduction » Quorum/Witness » tcp_remote Mode
In this setting Quorum is determined by checking the ability to connect to TCP/IP services on remote hosts. Connections are done via TCP/IP to a specific port on a host and are done independent of any of the defined communication paths. Being able to connect to the…
LifeKeeper GUI – Overview
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Using LifeKeeper for Linux » GUI » Preparing to Run the GUI » LifeKeeper GUI – Overview
The LifeKeeper GUI uses Java technology to provide a graphical status interface to LifeKeeper and its configuration data. Since the LifeKeeper GUI is a client/server application, a user will run the graphical user interface on a client system in order to monitor or…
Running Multiple Instances of Samba
Application Recovery Kits » Samba Recovery Kit Administration Guide » Configuring Samba with LifeKeeper » Running Multiple Instances of Samba
Running multiple instances of Samba in a LifeKeeper cluster introduces additional configuration requirements and restrictions. The following Samba configuration scenarios may involve multiple instances of Samba: Active/Standby configuration with multiple LifeKeeper…
Storage Mode
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » Installation and Configuration » LifeKeeper I/O Fencing Introduction » Quorum/Witness » Storage Mode
With this mode each node writes information about itself to a shared storage device on a regular basis and periodically reads the information written by the other nodes. A cluster is considered to have quorum consensus when each node is able to access the shared…
Route53 Recovery Kit Administration Guide
Application Recovery Kits » Route53 Recovery Kit Administration Guide
Route53 Recovery Kit provides a mechanism for updating Amazon Route 53 DNS information corresponding to a virtual IP address and an actual IP address information of IP resources that are in dependency relation when switching to a failed primary server to a backup…
Active/Active Configuration with Shared Storage
Application Recovery Kits » WebSphere MQ Recovery Kit Administration Guide » WebSphere MQ Configuration Considerations » MQ Configuration Requirements » WebSphere MQ Configuration Examples » Active/Active Configuration with Shared Storage
In the Active/Active configuration below, both Node1 and Node2 are primary LifeKeeper servers for WebSphere MQ resources. Each server is also the backup server for the other. In this example, Node1 protects the shared storage array for queue manager QMGR1. Node2…
LifeKeeper Core – Known Issues / Restrictions
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » Troubleshooting » Known Issues and Restrictions » LifeKeeper Core – Known Issues / Restrictions
Description File system labels should not be used in large configurations The use of file system labels can cause performance problems during boot-up with large clusters. The problems are generally the result of the requirement that to use labels…
LifeKeeper Core
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » SIOS LifeKeeper for Linux Introduction » LifeKeeper Core
LifeKeeper Core is composed of four major components: LifeKeeper Core Software File System, Generic Application, Raw I/O and IP Recovery Kit Software LifeKeeper GUI Software LifeKeeper Man Pages LifeKeeper Core Software The LifeKeeper Core Software…
Recovery Kit for EC2 Administration Guide
Application Recovery Kits » Recovery Kit for EC2 Administration Guide
The Recovery Kit for EC2 provides a mechanism to recover an Elastic IP from a failed primary server to a backup server. It also provides a mechanism to enable the IP Recovery Kit to work in multiple availability zones. Please see the Principles of Operation for a…
Oracle Known Issues and Restrictions
Application Recovery Kits » Oracle Recovery Kit Administration Guide » Oracle Troubleshooting » Oracle Known Issues and Restrictions
Control File Switchover Failure If the $ORACLE_HOME directory does not recover, the database control files may not be set up properly. For automatic switchover, the control files need to be configured on a shared device during the database creation. If you keep the…
Active/Active Configuration with NAS Storage
Application Recovery Kits » WebSphere MQ Recovery Kit Administration Guide » WebSphere MQ Configuration Considerations » MQ Configuration Requirements » WebSphere MQ Configuration Examples » Active/Active Configuration with NAS Storage
In the Active/Active configuration below, both Node1 and Node2 are primary LifeKeeper servers for WebSphere MQ resources. Each server is also the backup server for the other. In this example, Node1 protects the NFS mount for queue manager QMGR1. Node2 protects the NFS…
Message Bar
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Using LifeKeeper for Linux » Message Bar
The message bar appears beneath the status window. It is used for displaying messages in a single text line. Message such as “Connecting to Server X” or “Failure to connect to Server X” might be displayed. To hide the message bar, clear the…
Configuring Transparent Application Failover with LifeKeeper
Application Recovery Kits » Oracle Recovery Kit Administration Guide » Configuring Oracle with LifeKeeper » Configuring Transparent Application Failover with LifeKeeper
When a server failover or an Oracle database failure occurs, users can be severely disrupted. Typically the user’s connections to the database will be lost along with most work in progress. Upon the completion of the failover (or recovery of the Oracle database),…
Sybase ASE Recovery Kit Overview
Application Recovery Kits » Sybase ASE Recovery Kit Administration Guide » Sybase ASE Recovery Kit Overview
The SIOS Protection Suite (SPS) for Linux Sybase ASE Recovery Kit provides a mechanism for protecting Sybase ASE Server instances within SPS. The Sybase ASE software, LifeKeeper Core and Sybase ASE Recovery Kit are installed on two or more servers in a cluster. Once…
Active/Standby Configuration with /var/mqm on Shared Storage
Application Recovery Kits » WebSphere MQ Recovery Kit Administration Guide » WebSphere MQ Configuration Considerations » MQ Configuration Requirements » WebSphere MQ Configuration Examples » Active/Standby Configuration with /var/mqm on Shared Storage
In the Active/Standby configuration, Node1 is the primary LifeKeeper server. It protects the WebSphere MQ queue managers. All storage resides on a shared array between the cluster servers. While Node2 may be handling other applications/services, it acts only as a…
GUI Toolbar
SIOS Protection Suite for Linux Technical Documentation » LifeKeeper » User Guide » Using LifeKeeper for Linux » GUI » Toolbars » GUI Toolbar
This toolbar is a combination of the default server and resource context toolbars which are displayed on the properties panel except that you must select a server and possibly a resource when you invoke actions from this toolbar. Connect. Connect…
Configuration 4 – Multi-Instance Queue Managers
Application Recovery Kits » WebSphere MQ Recovery Kit Administration Guide » WebSphere MQ Configuration Considerations » MQ Configuration Requirements » MQ Supported File System Layouts » Configuration 4 – Multi-Instance Queue Managers
Recommended for Active/Standby or Active/Active configurations that specify the data file directory location during queue manager creation (crtmqm -md DataPath) to be something other than the default of /var/mqm/qmgrs. This feature is available in WebSphere MQ Version…
SAP MaxDB Recovery Kit Overview
Application Recovery Kits » SAP MaxDB Recovery Kit Administration Guide » SAP MaxDB Recovery Kit Overview
The SPS for Linux SAP DB / Max DB Recovery Kit provides a mechanism for protecting SAP DB instances within SPS. The SAP DB software, SPS Core and SAP DB / Max DB Recovery Kit are installed on two or more servers in a cluster. Once the SAP DB database instance is under…
Verifying Installation
LifeKeeper Single Server Protection Technical Documentation » Intergration with VMware HA » SteelEye Management Console » Verifying Installation
The SteelEye Management Console installation can be verified by connecting, via a web browser, to https:/// which should show a page indicating that the SMC services are available. *Note: It is normal to receive a security warning since the SMC uses a self-signed SSL…