|
LifeKeeper for Linux FAQs
What system resources does LifeKeeper for Linux protect?
LifeKeeper for Linux provides switchover protection for a range of system resources. Automatic recovery is supported for the following resource types.
- Processes and Applications
- Shared Storage Devices
- Network Attached Storage Devices
- LVM Volume Groups and Logical Volumes
- File Systems (ext2, ext3, reiserfs, vxfs, xfs and nfs)
- Communication Resources (IP addresses)
- Database Applications (Oracle, Informix Dynamic Server, MySQL, DB2, SAP DB/MaxDB, PostgreSQL, Sybase)
- Web Server Resources (Apache, Apache SSL)
- Mail Server Resources (Sendmail, SAMS, SMMS, Mailcenter, Postfix)
- Samba Resources (file shares)
- Data Replication (SDR, DRBD)
- SAP Application Environment Resources
- ClearCase Configuration Management Resources
- Software RAID (md) Resources
- WebSphere MQ Resources
- VMware ESX Server and VMware Server Virtual Machines
LifeKeeper for Linux provides Disaster Recovery protection for the following resource type:
- Citrix XenServer Standard, Enterprise, and Platinum Editions Storage Repository
Back to top
What are the software requirements for installing LifeKeeper for Linux?
LifeKeeper for Linux is currently targeted for any platform that satisfies
the minimum requirements included in the table below.
| LifeKeeper Core |
|
| Description | | Requirement |
|
| Linux Operating System | | Red Hat Enterprise Linux 3.0 and 4.0 (AS and ES), Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 5 Advanced Platform
SUSE SLES 9 and SLES 10
Asianux 2.0
VMware ESX Server v3.0 Console OS
Citrix XenServer Standard, Enterprise, and Platinum Editions v4.1.0
Oracle Enterprise Linux 4 and 5
The Community ENTerprise Operating System
(CentOS) 4 and 5
|
|
|
| Korn Shell | | pdksh-5.2.14 (or later) |
|
| Memory | | The minimum memory requirement for a system supporting LifeKeeper is 128 MB. Additional memory (beyond that required for LifeKeeper) is required to run user applications. |
|
| Disk Space | | The LifeKeeper Core Package Cluster requires the following disk space:
/opt Approximately 17000 (1024-byte) disk blocks on 32-bit systems and approximately 60100 (1024-byte) disk blocks on 64-bit systems.
/ Approximately 89100 (1024-byte) disk blocks on 32-bit and 64-bit systems. |
| LifeKeeper Optional Recovery Software |
|
| Description |
|
Requirement(s) |
|
Disk Space Required |
|
| Apache Web Server |
|
Apache Web Server 1.3.14 or 2.x
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 215 (1024-byte) disk blocks in /opt |
|
| ClearCase |
|
ClearCase version 2003.06, version 7, or version 7.0.1.0
LifeKeeper v5.0.0 Core Package Cluster or later
LifeKeeper NFS Server Recovery Kit v5.0.0 or later (only required if ClearCase storage does not reside exclusively on network-attached storage devices) |
|
Approximately 150 (1024-byte) disk blocks in /opt. |
|
| DB2 |
|
IBM DB2 Universal Database v8.1 or later, Enterprise Server Edition (ESE), and Workgroup Server Edition (WSE)
IBM DB2 Express v8.1 or later
IBM DB2 Universal Database v9, Enterprise Server Edition (ESE), and Workgroup Server Edition (WSE)
LifeKeeper v5.0.0 Core Package Cluster or later
LifeKeeper NFS Server Recovery Kit v5.0.0 or later (for DB2 ESE with multiple partitions and DB2 EEE only) |
|
Approximately 215 (1024-byte) disk blocks in /opt. |
|
| Oracle |
|
Oracle 9i Standard Edition or Enterprise Edition
Oracle 10g Standard Edition, Standard Edition One or Enterprise Edition
Oracle 11g Standard Edition, Standard Edition One or Enterprise Edition
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 525 (1024-byte) disk blocks in /opt |
|
| Informix |
|
Informix Dynamic Server 9.2 or later and Informix Dynamic Server 10
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 200 (1024-byte) disk blocks in /opt |
|
| MySQL |
|
MySQL 3.23.x, 4.x, 5.x or MySQL Network
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 140 (1024-byte) disk blocks in /opt |
|
| PostgreSQL |
|
PostgreSQL v7.x or v8.x
LifeKeeper v5.0.0 Core Package Cluster or later |
| Approximately 144 (1024-byte) disk blocks in /opt |
|
| Sybase ASE |
|
Sybase ASE 12.5.x and 15.x
LifeKeeper v5.0.0 Core Package Cluster or later |
| Approximately 200 (1024-byte) disk blocks in /opt |
|
| Sendmail Mailcenter |
|
Sendmail Mailcenter 3.0
LifeKeeper v5.1.0 Core Package Cluster or later |
| Approximately 270 (1024-byte) disk blocks in /opt |
|
| Sendmail |
|
Sendmail 8.11, 8.12, or 8.13
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 200 (1024-byte) disk blocks in /opt |
|
| Sendmail Advanced Message Server |
|
Sendmail Advanced Message Server (SAMS) 1.2, 2.1, or 2.2
Sendmail Switch 2.2 or 3.1
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 196 (1024-byte) disk blocks in /opt |
|
| Postfix |
|
Postfix software provided with supported Linux distributions
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 150 (1024-byte) disk blocks in /opt |
|
| Samba |
|
Standard Samba file services provided with supported Linux distributions
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 265 (1024-byte) disk blocks in /opt |
|
| NFS Server |
|
Linux kernel version 2.4.21 or later
LifeKeeper v4.6.1 Core Package Cluster or later |
|
Approximately 160 (1024-byte) disk blocks in /opt |
|
| Network Attached Storage |
|
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 125 (1024-byte) disk blocks in /opt |
|
| Logical Volume Manager (LVM) |
|
Linux Logical Volume Manager (LVM) version 1 or 2
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 130 (1024-byte) disk blocks in /opt |
|
| SteelEye Data Replication (v6) |
|
LifeKeeper v6.2 Core Package Cluster or later
Linux kernel version 2.6 (2.6.16 or later for intent logging and asynchronous write support) |
|
Approximately 1800 (1024-byte) disk blocks in /opt |
|
| Data Replication (v4) |
|
raidtools-0.90-6 or later
LifeKeeper v4.6.0 Core Package Cluster or later
Linux kernel version 2.4 |
|
Approximately 350 (1024-byte) disk blocks in /opt |
|
| Software RAID (md) |
|
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 204 (1024-byte) disk blocks in /opt |
|
| PowerPath |
|
A 2.6 based Linux kernel and distribution
PowerPath for Linux v4.4.x or v4.5.x
LifeKeeper v6.0.0 Core Package Cluster or later |
|
Approximately 168 (1024-byte) disk blocks in /opt |
|
| IBM Subsystem Device Driver (SDD) |
|
A 2.6 based Linux kernel and distribution
IBM SDD driver v1.6.0.1-8 or later
LifeKeeper v6.0.0 Core Package Cluster or later |
|
Approximately 164 (1024-byte) disk blocks in /opt |
|
| Device Mapper Multipath (DMMP) |
|
A 2.6 based Linux kernel and distribution
multipath tools 0.4.5 or later
LifeKeeper v6.0.0 Core Package Cluster or later |
|
Approximately 176 (1024-byte) disk blocks in /opt |
|
| Hitachi Dynamic Link Manager (HDLM) |
|
RHEL 4 (AS/ES) Update 1, 2, 3, and 4 (x86 or EM64T/AMD64, where EM64T/AMD64 indicates an environment where an EM64T/AMD64 kernel is installed on a system that uses an Intel CPU or AMD Opteron CPU (Single Core and Dual Core)
Hitachi HDLM for Linux 5.8, 5.8.1, and 5.9
LifeKeeper v6.0.0 Core Package Cluster or later |
|
Approximately 168 (1024-byte) disk blocks in /opt |
|
| NEC iStorage StoragePathSavior(SPS) |
|
RHEL 4 SPS Driver package sps-E-3.0.9-2.6.9.42.EL
NEC iStorage StoragePathSavior Enterprise for Linux Version 3.3.001
LifeKeeper v6.2 Core Package Cluster or later |
|
Approximately 190 (1024-byte) disk blocks in /opt |
|
| DRBD |
|
DRBD version 0.7.5 or 0.8
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 70 (1024-byte) disk blocks in /opt |
|
| VMware Virtual Machine |
|
VMware ESX Server version 3.0.x
VMware Server version 1.0.x (on a LifeKeeper-supported Linux Host OS)
LifeKeeper v6.1.2 Core Package Cluster or later |
|
Approximately 120 (1024-byte) disk blocks in /opt |
|
| Citrix XenServer Support Package |
|
Citrix XenServer Standard, Enterprise, and Platinum Editions v4.1.0
LifeKeeper v6.3.0 Core Package Cluster or later |
|
Approximately 140 (1024-byte) disk blocks in /opt |
|
| WebSphere MQ |
|
WebSphere MQ versions 5.3, 5.3 Express Edition, and 6.0
LifeKeeper v5.2.0 Core Package Cluster or later |
|
Approximately 415 (1024-byte) disk blocks in /opt |
|
| Extender |
|
LifeKeeper v5.0.0 Core Package Cluster or later |
|
Approximately 185 (1024-byte) disk blocks in /opt |
|
| SAP |
|
SAP R/3 version 4.6C (Kernel 4.6D), SAP R/3 Enterprise 4.7 (Web AS 6.20), SAP NetWeaver 04 (Web AS 6.40), and SAP NetWeaver 2004s (Web AS 7.00)
Refer to the LifeKeeper for Linux Release Notes for detailed distribution, kernel, and database requirements.
LifeKeeper v5.1.3 Core Package Cluster or later
LifeKeeper NFS Server Recovery Kit v5.1.0 or later
LifeKeeper Network Attached Storage Recovery Kit v5.0.0 or later |
| Approximately 170 (1024-byte) disk blocks in /opt |
|
| SAP DB/MaxDB |
|
SAP DB 7.3.0 Build 21 or later for standalone use
SAP DB 7.3.0 Build 35 or later for use with SAP
MaxDB 7.5.x
LifeKeeper v5.0.0 Core Package Cluster or later |
| Approximately 205 (1024-byte) disk blocks in /opt |
|
Back to top
On what Linux distributions and kernel versions is LifeKeeper supported?
LifeKeeper for Linux has been certified for Red Hat Enterprise Linux 3.0 (AS and ES), Red Hat Enterprise Linux 4.0 (AS and ES), Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 5 Advanced Platform, SUSE SLES 9, and SLES 10, Asianux 2.0, VMware ESX Server v3.0, Citrix XenServer Standard, Enterprise, and Platinum Editions v4.1.0, Oracle Enterprise Linux 4 and 5, The Community ENTerprise Operating System (CentOS) 4 and 5.
The latest version of LifeKeeper is certified on the following Linux kernels:
- Red Hat
- 2.4.21-4.0.2.EL
- 2.4.21-9.EL
- 2.4.21-9.0.1.EL
- 2.4.21-15.EL
- 2.4.21-20.EL
- 2.4.21-27.EL
- 2.4.21-32.EL
- 2.4.21-32.0.1.EL
- 2.4.21-37.EL
- 2.4.21-40.EL
- 2.4.21-47.EL
- 2.4.21-50.EL
- 2.6.9-5.EL
- 2.6.9-5.0.3.EL
- 2.6.9-11.EL
- 2.6.9-22.EL
- 2.6.9-34.EL
- 2.6.9-42.EL
- 2.6.9-55.EL
- 2.6.9-67.EL
- 2.6.18-8.EL5
- 2.6.18-8.1.1.EL5
- 2.6.18-53.EL5
- SUSE
- 2.6.5-7.97
- 2.6.5-7.139
- 2.6.5-7.151
- 2.6.5-7.191
- 2.6.5-7.244
- 2.6.5-7.308
- 2.6.16.21-0.8
- 2.6.16.46-0.12
- Asianux
- 2.6.9-11.19AX
- VMware ESX Server
- 2.4.21-37.0.2.ELvmnix
- Citrix XenServer Standard, Enterprise, or Platinum Edition v4.1.0
- 2.6.18-53.1.13.el5.xs4.1.0.254.273
- Oracle Enterprise Linux
- 2.6.9-55.0.0.0.2.EL
- 2.6.18-8.el5
- The Community ENTerprise Operating System (CentOS)
- 2.6.9-55.EL
- 2.6.18-8.el5
LifeKeeper-specific changes have been incorporated into these kernels by their vendors. If you have replaced the kernel delivered by the Operating System vendor with one from the Linux kernel site, then you will need to download our kernel patches and apply them.
Reference the SteelEye
open source site
for more information on LifeKeeper modifications to the Linux kernel.
Back to top
Does LifeKeeper for Linux replace any of the standard Linux kernel components?
LifeKeeper resides in non-kernel space, and communicates with the
standard kernel via published APIs. However, in developing and
testing the LifeKeeper product, SteelEye has identified core
kernel, module, and driver changes that are essential to meeting
the high availability requirements of the LifeKeeper product.
These core kernel changes have all been picked up by the
Operating System vendors whom we support, and are already
included in the supported kernels listed above. If you have
replaced the kernel delivered by the Operating System vendor with
an unmodified one from the Linux kernel site, then you will need
to download our core kernel patches and apply them.
For some specific high availability configurations and kernels,
LifeKeeper may also require changes that affect the loadable modules
within the kernel (e.g. nfs, raid1). The majority of these changes
have also been picked up by the Operating System vendors and are already
included with the supported kernels listed above. In the few cases
where this is not true, these modules are provided on the LifeKeeper
installation media and are installed only when your configuration
requires them. Again if you have replaced the kernel delivered by the
Operating System vendor with one from the Linux kernel site, you may
need to download our kernel module patches and apply them.
Reference the SteelEye
open source site
for more information on LifeKeeper modifications to the Linux kernel.
Back to top
What application recovery kits are available for LifeKeeper for Linux?
| Package |
|
Protected Applications |
|
| LifeKeeper DB2 Recovery Kit |
|
IBM DB2 Universal Database v8.1 or later, Enterprise Server Edition (ESE), Workgroup Server Edition (WSE), and Express
IBM DB2 Universal Database v9, Enterprise Server Edition (ESE), and Workgroup Server Edition (WSE) |
|
| LifeKeeper Oracle Recovery Kit |
|
Oracle 9i Standard Edition or Enterprise Edition; Oracle 10g Standard Edition, Standard Edition One or Enterprise Edition; and Oracle 11g Standard Edition, Standard Edition One or Enterprise Edition |
|
| LifeKeeper Informix Database Recovery Kit |
|
Informix Dynamic Server 9.2 or later and Informix Dynamic Server 10 |
|
| LifeKeeper MySQL Recovery Kit |
|
MySQL 3.23.x, 4.x, 5.x and MySQL Network |
|
| LifeKeeper PostgreSQL Recovery Kit |
|
PostgreSQL v7.x and v8.x |
|
| LifeKeeper Sybase ASE Recovery Kit |
|
Sybase ASE 12.5.x and 15.x |
|
| LifeKeeper Apache Web Server Recovery Kit |
|
Apache Web Server 1.3 or 2.x |
|
| LifeKeeper Sendmail Mailcenter Recovery Kit |
|
Sendmail Mailcenter 3.0 |
|
| LifeKeeper Sendmail Recovery Kit |
|
Sendmail 8.11, 8.12, or 8.13 |
|
| LifeKeeper SAMS Recovery Kit |
|
Sendmail Advanced Message Server (SAMS) 1.2, 2.1, or 2.2 and Sendmail Switch 2.2 or 3.1 |
|
| LifeKeeper Postfix Recovery Kit |
|
Postfix provided with supported Linux distributions |
|
| LifeKeeper Samba Recovery Kit |
|
Samba file shares |
|
| LifeKeeper NFS Server Recovery Kit |
|
NFS exported file systems on Linux distributions with a kernel version of 2.4.21 or later |
|
| LifeKeeper Network Attached Storage Recovery Kit |
|
Mounted NFS filesystems from an NFS server or Network Attached Storage (NAS) device |
|
| LifeKeeper Logical Volume Manager (LVM) Recovery Kit |
|
LVM volume groups and logical volumes |
|
| LifeKeeper ClearCase Recovery Kit |
|
ClearCase VOB and View Storage locations, ClearCase Registry files, and the ClearCase Release Area |
|
| LifeKeeper DRBD Recovery Kit |
|
DRBD (Distributed Remote Block Device) data replication software |
|
| LifeKeeper Software RAID (md) Recovery Kit |
|
Software RAID devices based on md |
|
| LifeKeeper PowerPath Recovery Kit |
|
EMC PowerPath multipath I/O devices |
|
| LifeKeeper IBM Subsystem Device Driver (SDD) Recovery Kit |
|
IBM SDD multipath I/O devices |
|
| LifeKeeper Device Mapper Multipath (DMMP) Recovery Kit |
|
Linux dm-multipath I/O devices |
|
| LifeKeeper Hitachi Dynamic Link Manager (HDLM) Recovery Kit |
|
Hitachi Dynamic Link Manager devices |
|
| LifeKeeper NEC iStorage StoragePathSavior (SPS) Recovery Kit |
|
NEC iStorage StoragePathSavior multipath I/O devices |
|
| SteelEye Data Replication (v6) |
|
Network RAID devices (synchronous or asynchronous mirrors, with intent logging) |
|
| LifeKeeper Data Replication (v4) |
|
Network RAID devices (synchronous mirrors only) |
|
| LifeKeeper VMware Virtual Machine Recovery Kit |
|
VMware ESX Server and VMware Server virtual machines |
|
| LifeKeeper WebSphere MQ Recovery Kit |
|
WebSphere MQ queue managers including the command server, the listener and the persistent queue manager data |
|
| LifeKeeper Extender |
|
Provides sample code and tool for creating a basic application Recovery Kit. Documentation includes an overview of the Recovery Kit architecture, and a detailed description of Recovery Kit components and APIs. |
|
| LifeKeeper SAP Recovery Kit |
|
SAP R/3 version 4.6C (Kernel 4.6D), SAP R/3 Enterprise 4.7 (Web AS 6.20), SAP NetWeaver 04 (Web AS 6.40), and SAP NetWeaver 2004s (Web AS 7.00) |
|
| LifeKeeper SAP DB / MaxDB Recovery Kit |
|
SAP DB 7.3.0 Build 21 and higher (requires Build 35 and higher for use with SAP)
MaxDB 7.5.x |
Back to top
What optional support software packages are available for LifeKeeper for Linux?
| Package |
|
Protected Applications |
|
|
| Citrix XenServer Support Package |
|
Citrix XenServer Standard, Enterprise, and Platinum Editions storage repositories to provide Disaster Recovery protection |
|
Back to top
Does LifeKeeper require special hardware to provide its fault resilience?
LifeKeeper does not require any customized fault-tolerant hardware. The basis for the fault resilience provided by LifeKeeper is the clustering of computer nodes with shared data and communication paths. The bullets below talk about these in more detail:
- Clustered Nodes: Nodes can be any LifeKeeper compatible server systems. LifeKeeper gives
you the flexibility to configure nodes in multiple overlapping groups. For any given recoverable resource, however, the critical factor is the linking of a group of designated nodes
with defined roles or priorities for that resource. The priority of a node for a given resource is used to determine which node will recover that resource in the event of a failure on the node where it is currently running. The node with the highest priority value for a given resource is typically referred to as the primary node for that resource, the node with
the second highest priority is referred to as the secondary node, etc.
- Communication Paths: The LifeKeeper heartbeat, a periodic message between paired nodes, is a key fault detection facility. SteelEye recommends configuration of redundant heartbeat communications paths using different protocols and communications media (LAN and TTY) to
avoid system panics due to a simple communications failure. A LAN-based communications path can also be used for other system communications.
- Shared Data: Storage devices connected to multiple nodes in the LifeKeeper cluster provide mechanisms that allow grouped nodes to share access to the same set of disks. In the case of a failure of the primary node, LifeKeeper automatically manages the unlocking of the disks from the failed system and the locking of the disks to the next available backup system
- Shared Communication: LifeKeeper can automatically manage switching of TCP/IP communication resources. This allows users to connect to an application regardless of which of the grouped nodes is currently active.
Back to top
How do I know if my specific servers and storage devices
will work with LifeKeeper?
Here are some useful guidelines:
- LifeKeeper runs on Intel x86, Intel Itanium 2, Intel Xeon EM64T, and AMD Opteron based platforms. SteelEye has certified LifeKeeper with servers from Compaq, IBM, HP, Dell, Unisys, and NCR. However, most servers based on these processor architectures should be compatible.
- If you are using a disk array with shared SCSI, then the disk array must have a smart controller within it and the array must support SCSI 2 reservations. We have certified Compaq, Consan, Baydel, Winchester, and Jetstor disk arrays that meet this requirement.
- LifeKeeper is supported on Fibre Channel (FC) hardware. This can be used as an alternative to shared SCSI. SteelEye has certified Compaq, Dell, and IBM
fibre channel disk arrays using QLogic and Compaq host adapters. Note: The SCSI requirements mentioned in the previous bullet apply here as well.
- SteelEye Data Replication (SDR) replicates and protects data from one internal drive of a system to another internal drive on the backup system. This eliminates the need
for a shared storage device.
- The Network Attached Storage Recovery Kit provides support for NAS devices.
- Please see the Release Notes in the latest
LifeKeeper for Linux documentation for the list of
supported storage and adapter models.
Back to top
I can't run the LifeKeeper GUI from my client. What do I need to do?
The LifeKeeper Planning and Installation Guide documents all of the steps to run the GUI as an application or an applet. The important things to remember when running the GUI as an applet are:
- You need a .java.policy file in your home directory. LifeKeeper provides a template policy file that meets all of the permissions requirements for LifeKeeper.
- You must set your browser security permissions to low.
- If the Java plug-in is not already installed on your client, you will automatically be
taken to a web site to download the necessary plug-in.
- You open the GUI web page by accessing the URL http://servername:81 where servername is the name of the LifeKeeper server.
- It is important that all of the networking configuration is correct and complete. All
DNS and/or /etc/hosts entries must also be correct.
Back to top
How can I use LifeKeeper to protect my own application?
LifeKeeper Extender provides documentation and sample scripts for you to create your own recovery kit for your application. LifeKeeper Extender is a separately orderable product.
Back to top
|
|
 |
