Specifications
Software Requirements
Software Requirements
l Operating System – SteelEye DataKeeper can be used with any major Linux distribution
based on the 2.6 Linux kernel. See the SPS for Linux Release Notes for a list of supported
distributions. Asynchronous mirroring and intent logs are supported only on distributions that
use a 2.6.16 or later Linux kernel. Multiple target support (i.e., support for more than 1 mirror
target) requires a 2.6.7 or later Linux kernel.
l LifeKeeper Installation Script - In most cases, you will need to install the following package
(see the “Product Requirements” section in the SPS for Linux Release Notes for specific
SteelEye DataKeeper requirements):
HADR-generic-2.6
This package must be installed on each server in your LifeKeeper cluster prior to the
installation of SteelEye DataKeeper. The HADR package is located on the SPS
Installation Image File, and the appropriate package is automatically installed by the
Installation setup script.
l LifeKeeper Software - You must install the same version of the LifeKeeper Core on each of
your servers. You must also install the same version of each recovery kit that you plan to use
on each server. See the SPS for Linux Release Notes for specific SPS requirements.
l SteelEye DataKeeper software - Each server in your SPS cluster requires SteelEye
DataKeeper software. Please see the SPSfor Linux Installation Guide for specific instructions
on the installation and removal of SteelEye DataKeeper.
General Configuration
l The size of the target disks or partitions (on the backup servers) must be equal to or greater
than the size of the source disk or partition (on the primary server).
l Once the DataKeeper resource is created and extended, the synchronization process will
delete existing data on the target disks or partitions and replace it with data from the source
partition.
Network Configuration
l The network path that is chosen for data replication between each pair of servers must also
already be configured as a LifeKeeper communication path between those servers. To change
the network path, seeChanging the Data Replication Path.
l When configuring DataKeeper resources, avoid using an interface/address already in use by a
LifeKeeper IP resource that has local recovery enabled. For example, if a LifeKeeper IP
resource is configured on interface eth1 having local recovery enabled with interface eth2,
DataKeeper resources should avoid using either eth1 or eth2. Enabling local recovery will
disable the interface during switchover to the backup interface which can cause SteelEye
DataKeeper failure.
266Installation and Configuration