SteelEye Protection Suite for Windows
v7.7
Technical Documentation

October 2013

This document and the information herein is the property of SIOS Technology Corp. (previously known as
SteelEye® Technology, Inc.) and all unauthorized use and reproduction is prohibited. SIOS Technology
Corp. makes no warranties with respect to the contents of this document and reserves the right to revise thispublication and make changes to the products described herein without prior notification. It is the policy of
SIOS Technology Corp. to improve products as new technology, components and software become
available. SIOS Technology Corp., therefore, reserves the right to change specifications without prior notice.
LifeKeeper, SteelEye and SteelEye DataKeeper are registered trademarks of SIOS Technology Corp.
Other brand and product names used herein are for identification purposes only and may be trademarks of
their respective companies.
To maintain the quality of our publications, we welcome your comments on the accuracy, clarity,organization, and value of this document.
Address correspondence to:
ip@us.sios.com
Copyright © 2013
By SIOS Technology Corp.
San Mateo, CA U.S.A.
All rights reserved

Table of Contents
Chapter 1: About SteelEye Protection Suite for Windows

1

SteelEye Protection Suite for Windows Integrated Components

1

Protected Resources

1

SteelEye Protection Suite Core Software
SteelEye Protection Suite Core Recovery Kits

2
3

SteelEye Protection Suite Microsoft SQL Server Recovery Kit

4Communication Path Overview

4

Communication Path Types

5

More About the Shared Disk Comm Path

5

SteelEye Protection Suite Heartbeat

6

Heartbeat Interval

6

Safety Check

6

Resource Hierarchies

7

Hierarchy Relationships

7

Resource Hierarchy Information

8

Resource States

8

Shared Equivalencies

9

Chapter 2: Installation Guide

11

Chapter 3: Configuration

13

SteelEye Protection Suite Configuration Steps

13

Active-Active Grouping

13

Active-Standby Grouping

14

Intelligent Versus Automatic Switchback

15

SteelEye Protection Suite Configurations

16

Common Hardware Components

16

Table of ContentsiSystem Grouping Arrangements

17

Chapter 4: SteelEye Protection Suite Administration Overview

20

Administrator GUI Tasks

20

Editing Server Properties

20

Set Server Shutdown Strategy

21

Server Properties

21

Disabling Automatic Failover

26

Creating a Communication Path

27

Configuration Notes

27

Creating a Comm Path

28

Verifying the Comm Path

29

Deleting a Communication Path

29

Working With Resource Hierarchies

29

Creating Resource Hierarchies

30

SteelEye Protection Suite Application Resource Hierarchies

30

Microsoft SQL Server Recovery Kit

30

Creating a DNS Resource Hierarchy

30

Creating a File Share Resource Hierarchy

33

Criteria for File Share Resources

33

File Share Resource Creation

33

Creating a Generic Application Resource Hierarchy

34

Before Creating a Resource Hierarchy

34

Creating Your Resource Hierarchy

35

Creating a LAN Manager Resource Hierarchy

36

Creating a Volume Resource Hierarchy

37

After the Volume Resource is Created38

Creating an IP Address Resource Hierarchy

38

Requirements for IP Local Recovery

38

IP Local Recovery Scenario

40

Editing Resource Priorities

41

Table of Contentsii

Using the Up and Down Buttons

42

Editing the Priority Values

43

Applying Your Changes

43

Incomplete Resource Priority Modification
Restoring Your Hierarchy to a Consistent State

43
44

Editing Resource Properties

44

Extending Resource Hierarchies

44

Extending a DNS Resource Hierarchy

45

Extending a File Share Resource Hierarchy

45

Extending a Generic Application Resource Hierarchy

46

Extending a LAN Manager Resource Hierarchy

46

Extending a Volume Resource Hierarchy

46

Extending an IP Address Resource Hierarchy46

Unextending a Hierarchy

47

Adding a Resource Dependency

48

Removing a Resource Dependency

48

Deleting a Hierarchy from All Servers

49

Man Pages

49

LCD - Miscellaneous LCD Programs

49

Synopsis49

Description

50

Exit Codes

50

lcdrcp50

lcdrecover50

lcdremexec

52

lcdsync52

lkstart52

lkstop53

LCDI Applications

53

Synopsis

53

Table of Contentsiii

Description

53

Exit Codes

54

app_create54

app_list54

app_remove

54

LCDI Instances

55

Synopsis

55

Description

55

Exit Codes56

ins_list

56

Initialization Strategy

57

Initial State58

ins_create58

ins_gettag

58

ins_remove59

ins_setas60

ins_setchkint

60

ins_setin60

ins_setit60

ins_setlocalrecover61

ins_setst

61

LCDI-relationship

61

Synopsis61

Description

62

Exit Codes

62

dep_create62

dep_list63

dep_remove63

eqv_create64

eqv_list

64

Table of Contentsiv

eqv_remove

65

LCDI-resource_type

65

Synopsis65

Description

65

Exit Codes65

typ_create66

typ_list66

typ_remove

66

LCDI-systems

68

Synopsis

68

Description

68

Exit Codes

68

sys_create69

sys_getds69

sys_getst

69

sys_list69

sys_remove

69

LifeKeeper Flags

69

flg_create70

flg_list70

flg_remove70

flg_test

70

LCDI Flags

71

Synopsis71

Description

71

lk_chg_value

72

NAME

72

SYNOPSIS

72

DESCRIPTION

73

EXAMPLES73

Table of Contentsv

EXIT CODES

74

NOTES

74

FILES

74

lk_err74

Synopsis74

Description

75

perform_action

75

Synopsis75

Description

75

Example78

Exit Codes

78

sendevent78

Synopsis

78

Description

78

Output80

Exit Codes

81

volume81

Synopsis81

Description

81

Example82

Exit Codes

82

LKSUPPORT

83

Setting Browser Security Parameters

83

Internet Explorer

83

IP Local Recovery

83

Overview of SteelEye Protection Suite Event Forwarding via SNMP

84

SteelEye Protection Suite Events Table

84

Steps to Upgrade Java Runtime Environment (JRE) Version for SteelEye Protection Suite forWindows
87
Notes

88

Table of ContentsviChapter 5: User Guide

90

LifeKeeper GUI

91

LifeKeeper Graphical User Interface

91

GUI Overview

91

GUI Server

91

GUI Client

91

Starting GUI Clients

92

Starting the Web Client

92

Starting the Application Client

92

Exiting GUI Clients92

Status Table

92

Properties Panel

93

Output Panel

93

Message Bar

93

Toolbars

94

SteelEye Protection Suite for Windows Toolbars

94

Global Toolbar

94

Resource Context Toolbar

95

Server Context Toolbar

96

Menus

98

SteelEye Protection Suite for Windows Menus

98

Resource Context Menu

98

Server Context Menu

99

File Menu

100

Edit Menu - Resource

100

Edit Menu - Server

101

View Menu

102

Help Menu

103

LifeKeeper GUI Server and Client Components

104

Running the SteelEye Protection Suite Web Client

105

Table of Contentsvii

Configuring the Browser Security Level

106

Internet Explorer

107

Mozilla Firefox

107

Running the GUI Application on a SteelEye Protection Suite Server

107

LifeKeeper GUI User Accounts

108

Logging In

108

Configuring GUI Users

108

Common Tasks

109

Connecting To A Cluster

109

Disconnecting From a Cluster

110

Viewing Connected Servers

110

Viewing The Status Of A Server

111

Viewing Server Log Files

111

Viewing Server Properties

111

Viewing Resource Tags and IDs

112

Viewing the Status of Resources

112

Server Resource Status

112

Global Resource Status

113

Viewing Resource Properties

113

Viewing Message History

114

Reading the Message History

114

Expanding and Collapsing A Resource Hierarchy Tree114

Operator Tasks

115

Bringing A Resource In Service

115

Taking a Resource Out Of Service

116

Taking Volume Resources In and Out Of Service

116

Volume Remove Stop/Restart Programs and Services

117

Volume Restore Stop/Restart Programs and Services

118

Volume Shadow Copy (VSS)

119

Using Volume Shadow Copy (VSS) with DataKeeper/SteelEye Protection Suite Volumes

Table of Contents
viii

119

Volume Locking for Shared SCSI Volumes

119

Advanced Topics

120

LifeKeeper Configuration Database (LCD)120

LCD Directory Structure

120

Diagram of LCD Directory

121

LCD Configuration Data

122

Dependency Information

122

Resource Status Information

122

Inter-Server Equivalency Information

122

LCD Resource Types

122

Resources Subdirectories

123

Resource Actions

124

LCDI Commands

124

LifeKeeper Communications Manager (LCM)

124

Communication Status Information

125

Maintenance Tasks

125

Starting and Stopping LifeKeeper

125

Starting LifeKeeper

125

Stopping LifeKeeper

125Managing IP Resources

125Managing DNS Resources

126

Displaying List of Protected File Shares

128

EditFileShareResource Utility

128

Transferring Resource Hierarchies

129

Performing Offline Maintenance On A Shared Disk

129

Maintaining a SteelEye Protection Suite Protected System

129

Configuring Generic Application Scripts

130

Maintaining a Resource Hierarchy

133

Recovering After a Failover

133

Chapter 5: Uninstalling SteelEye Protection Suite for Windows

Table of Contentsix

134

Before Removing LifeKeeper

134

Before Removing DataKeeper

134

Uninstall SteelEye Protection Suite

134

Notes

135

Data Replication

135

Monitoring Replicated Volume Resources

135

Replication Settings

138

Performing Actions on Replicated Volumes

139

What is Split-Brain

140

Split-Brain Recovery

142

Data Rewind Overview

145

Rewind Settings

146

Performing Rewind on Replicated Volume Resources

147

Chapter 6: DataKeeper

150

Chapter 7: Troubleshooting

151

Applet Troubleshooting

151

Description151

CYGWIN Crash on Win2008 May Occur When LifeKeeper Stopping

152

Symptom

152

Solution

152

Error When Attempting to Run SteelEye Protection Suite Command From Command
Prompt152

Symptom

152

Solution

152

Firewall153

Symptom

153

Solution

153

GUI Error Messages

153

Description

153

GUI Network Related - Initial Connection to Server Failed (Error 117)

Table of Contentsx155

Symptom155

Solution

155

GUI Network Related - Long Connection Delays on Windows Platforms

155

Symptom

155

Solution

155

From Sun FAQ:155

GUI Network Related - NoRouteToHostException Message Generated During Connection
Attempt

156

Symptom

156

Solution

156

GUI Network Related - Unknown Host Exception Message Generated During Connection
Attempt

156

Symptom

156

Solution

157

From Windows

157

From Linux158

GUI Server Troubleshooting

158

Symptom

158

Solution

159

Health Check Timeouts

159

Incomplete Resource Creation

160

Description

160

Installation - Access is Denied

160

Symptom

160

Solution

160

IP Resource Create Issue

161

Symptom

161

Workaround161

Java Mixed Signed and Unsigned Code Warning

161

Symptom

161

Solution

162

Table of Contentsxi

LANMAN Name May Be Seen Twice in Browse List

162

Symptom

162

Solution

162

Licensing - Licensed Recovery Kit Resource Fails to Come In Service

163

Symptom

163

Solution

163

Licensing - License Key Not Found

163

Symptom

163

Solution

163

SteelEye Protection Suite Web Client May Lock Up

163

Symptom

163

Solution

163

SteelEye Protection Suite Web Client May Lock Up - Multiple Changes Made to Existing
Hierarchy

164

Symptom

164

Solution

164

New Evaluation License Key Error

164

Symptom

164

Solution

164

Recovering From a SteelEye Protection Suite Server Failure in a 1 x 1 Configuration
Suggested Action:

164
165

Recovering Out-of-Service Hierarchies
Description

172
172

Remove Hangs During Recovery Kit Uninstall

172

Symptom

172

Solution

172

Replicated Volume Switchover Failure
Description

173
173

Restore and Health Check Account Failures
Symptom173
173

Table of Contentsxii

Solution

174

SQL 2005 and SQL 2008174

Symptom

174

Solution

174

SQL Server Reporting Services (MSSQLSERVER)

175

Symptom

175

Solution

175

Two-Server Cluster Issue

175

Symptom

175

Solution

175

Unknown User Name or Bad Password

175

Access Denied: Unknown User Name or Bad Password

175

Symptom

176

Solution

176

Web Client Troubleshooting

176

Background

176

Answer176

Win2008 - IIS Resource Hierarchy Creation Error

177

Symptom

177

Solution

177

Index

178

Table of ContentsxiiiChapter 1: About SteelEye Protection Suite forWindows
SteelEye Protection Suite (SPS) for Windows integrates high availability clustering and data replication
functionality to protect mission-critical data and applications. SteelEye Protection Suite also integrates with
SIOS' Application Recovery Kits, which provide application-aware agents for SQL Server and Oracle andmore enabling you to make more informed recovery decisions.

SteelEye Protection Suite for Windows Integrated Components
LifeKeeper for Windows provides a fault resilient software solution to provide high availability for data,applications, and communications resources. LifeKeeper does not require any customized, fault-tolerant
hardware. You simply group two or more systems and enter site-specific configuration data. Then, LifeKeeper
automatically provides fault detection and recovery.
In case of a failure, LifeKeeper migrates protected resources from the failed system to the backup system.
Users experience a brief interruption during the actual switchover, but LifeKeeper automatically restoresoperations on the backup system when it completes the failover recovery.
SteelEye DataKeeper is a highly optimized host-based replication solution which ensures your data is
replicated as quickly and as efficiently as possible from your source server across the network to one or moretarget servers.
Optional Microsoft SQL Server Recovery Kit provides granular visibility into SQL Server so you canensure your systems are properly responding – not just running.

Protected Resources
The SteelEye Protection Suite family of products includes software that allows you to provide failoverprotection for a range of system resources. The figure below demonstrates SteelEye Protection Suite's
flexibility and identifies the resource types you can specify for automatic recovery:lVolume. With LifeKeeper’s volume resource type, you can protect data and applications on shared
SCSI peripherals or replicated volumes by creating a resource in the SteelEye Protection Suitehierarchy for the disk volume containing those resources.

lFile share. SteelEye Protection Suite's LAN Manager Recovery Kit lets you protect a specific folder ordirectory on a shared drive.

lComputer alias name. SteelEye Protection Suite's LAN Manager Recovery Kit enables automatic
failover of the computer alias name for applications that communicate to the server via NetBEUI.

lCommunications resources.

SteelEye Protection Suite for Windows Technical Documentation
Page 1

SteelEye Protection Suite Core SoftwarelSteelEye Protection Suite’s IP Recovery Kit allows you to create resources that enableswitchover of IP addresses.

lSteelEye Protection Suite's DNS Recovery Kit provides a mechanism to update DNS A andPTR records.

l

Database application. SteelEye Protection Suite provides an optional Recovery Kit for Microsoft SQL
Server.

l

Generic applications. SteelEye Protection Suite's Generic Application Recovery Kit allows thecreation of resources for an application that has no predefined recovery kit.

SteelEye Protection Suite supports N-Way recovery for a range of resource types. N-way recovery allows
different resources to fail over to different backup servers in a cluster.

See SteelEye Protection Suite Core Software for the core components available with SteelEye Protection
Suite.

SteelEye Protection Suite Core Software
SteelEye Protection Suite for Windows Core includes LifeKeeper and the basic LifeKeeper software
packages, DataKeeper and the Core Recovery Kits.
l

LifeKeeper - The LifeKeeper for Windows core includes the basic LifeKeeper software packages plus
the Core Recovery Kits.
l

LifeKeeper Configuration Database (LCD) - The LCD stores information about the
LifeKeeper-protected resources. This includes information on resource instances,
dependencies, shared equivalencies, recovery direction, and LifeKeeper operational

SteelEye Protection Suite for Windows Technical Documentation
Page 2

SteelEye Protection Suite Core Recovery Kits

flags. The data is cached in shared memory and stored in files so that the data can beremembered over system boots.

ll

LCD Interface (LCDI) - The LCDI queries the configuration database (LCD) to satisfy
requests for data or modifications to data stored in the LCD. The LCDI may also be usedby the Application Recovery Kit to obtain resource state or description information.

l

LifeKeeper Communications Manager (LCM) - The LCM is used to determine thestatus of servers in the cluster and for LifeKeeper inter-process communication (local
and remote). Loss of LCM communication across all communication paths on a serverin the cluster indicates the server has failed.

l

LifeKeeper Alarm Interface - The LifeKeeper Alarm Interface provides theinfrastructure for triggering an event. The sendevent program is called by application
daemons when a failure is detected in a LifeKeeper-protected resource. The sendevent
program communicates with the LCD to determine if recovery scripts are available.

l

LifeKeeper Recovery Action and Control Interface (LRACI) - The LRACI
determines the appropriate recovery script to execute for a resource and invokes theappropriate restore / remove scripts for the resource.

l

LifeKeeper GUI - The LifeKeeper GUI is a client/server application that provides agraphical administration interface to LifeKeeper and its configuration data The
LifeKeeper GUI client is implemented as both a stand-alone application and as a Java
applet invoked from a web browser.

DataKeeper - The DataKeeper package provides real-time data replication that allows you to keep Windows Server data in sync across multiple servers and data centers.

SteelEye Protection Suite Core Recovery Kits
The Core Recovery Kits provide all fault detection and recovery mechanisms and the definitions necessary toprovide SteelEye Protection Suite protection for volumes (drive letters), file shares, communications
resources and Microsoft Internet Information Server.
lVolume Recovery Kit - Allows you to create a resource to protect an entire shared or mirrored drive(for instance, the K: drive).

l

LAN Manager Recovery Kit - Enables automatic recovery of the computer alias name and Windows
file share lists. The LAN Manager resource lets you create a"switchable" computer name forapplications that communicate with the server via NetBEUI, or system name. It includes the File
Share recovery component.

l

IP Recovery Kit - Provides a mechanism to recover a "switchable" IP address from a failed primaryserver to one or more backup servers in a SteelEye Protection Suite environment. A switchable IP
address is a virtual IP address that can switch between servers and is separate from the IP address
associated with the network interface card of each server. Applications under SteelEye Protection
Suite protection are associated with the switchable IP address, so if there is a failure on the primaryserver, the switchable IP address becomes associated with the backup server This kit also provides
local recovery of the IP resource.

SteelEye Protection Suite for Windows Technical Documentation
Page 3

SteelEye Protection Suite Microsoft SQL Server Recovery Kitl

DNS Recovery Kit - Provides a mechanism to update DNS A and PTR records of the primary server
or an alias name. After a failover or switchover to the backup server, the A record and the associated
PTR record (if exists) of the primary server or alias name will be updated with the IP address of the
backup server.

lMicrosoft IIS Recovery Kit - Protects Web, FTP and SMTP services of the Microsoft Internet
Information Services (IIS). It continuously monitors the health of your Internet servers, and if a problem
arises, provides automatic failover of the affected web server to a backup server.

lGeneric Application Recovery Kit - Allows the creation of resources for an application that has nopredefined recovery kit.

SteelEye Protection Suite Microsoft SQL Server Recovery Kit
SteelEye Protection Suite Microsoft SQL Server Application Recovery Kit includes tools and utilities thatallow SteelEye Protection Suite to manage and control the Microsoft SQL-based database application. Wheninstalled, SteelEye Protection Suite is able to monitor the health of the application and automatically recover
the application if it fails. The SteelEye Protection Suite Recovery Kit is non-intrusive and requires no changes
within the application in order for SteelEye Protection Suite to protect it.
This recovery kit provides menu-driven definition of resources for automatic switchover of a Microsoft SQL
Server instance. The kit provides options that allow you to easily create a complete resource hierarchy so thatthe recovery operation can include all disk resources used by the SQL Server as well as the Named Pipe or IP
socket resources used to access the database.
For further information, refer to the Microsoft SQL Server Recovery Kit Technical Documentation.
Note: Product Requirements and FAQ information is delivered in the OS specific Release Notes.

Communication Path Overview
SteelEye Protection Suite monitors resource operations and provides failover using shared communication
paths (comm paths) between servers. It is critical to SteelEye Protection Suite fault detection and resource
recovery that communication between the servers remains active. As a result, you need to define multiplecomm paths using different protocols to guard against a system failover simply because a communication line
fails.
Before you can define resources or resource hierarchies in SteelEye Protection Suite, you must define yourcomm paths on each of the servers. SteelEye Protection Suite uses the comm paths to coordinate resource
definitions and states between the nodes and for fault detection and recovery.
The Communication Path Types section describes these comm path topics:lComm path types. SteelEye Protection Suite supports two types of comm paths for two-server
configurations: TCP/IP and Shared Disk. Configurations with greater than two servers support only
TCP/IP comm paths.

lSteelEye Protection Suite heartbeat. A key function of the comm path between the servers is the
SteelEye Protection Suite heartbeat. This periodic signal between the servers assures each serverthat the other is still alive and processing.

SteelEye Protection Suite for Windows Technical Documentation
Page 4

Communication Path Typesl

Safety check. If all comm paths die, SteelEye Protection Suite performs a safety check to verify
system failure before switching over resources.

Communication Path Types
SteelEye Protection Suite provides three different types of comm paths so that you can define redundantcomm paths using different protocols. Although there is less value in defining multiple paths of the same typeover the same media, redundant paths using different protocols or different media provide good protection
against failover due to a comm path failure.
When you define your comm paths, you establish a priority for each path. SteelEye Protection Suite uses thepaths in priority order for inter-node communication. However, SteelEye Protection Suite sends heartbeat
signals over all active comm paths. These are the comm paths supported by SteelEye Protection Suite andthe default priority range assigned to each:l

TCP/IP (socket). The LAN comm path is given the highest priority. The default priority range for thesocket path is 1 to 30. You can define multiple LAN comm paths between a pair of servers by defining
each one over a different adapter to prevent false failovers.
Note: The LifeKeeper GUI uses TCP/IP for communicating status information about protectedresources; if there are two TCP/IP comm paths configured, SteelEye Protection Suite uses the commpath with the highest priority for communicating resource status.

l

Shared disk. SteelEye Protection Suite allows you to define a raw disk partition on a shared disk as acommunication location for a pair of servers in the cluster. The shared disk path must be identified withthe same drive letter on both servers and the drive letter must identify the same disk partition. The disk
partition is usually small, typically one megabyte. The default priority range for the shared disk commpath is 61 to 99 (not supported in greater than two-server configurations).
Note: Shared Disk comm paths are used by SteelEye Protection Suite only for detecting whether otherservers in the cluster are alive. Therefore if the TCP/IP comm path used by the LifeKeeper GUI isdown, the GUI will show hierarchies on other servers in an UNKNOWN state, even if the shared disk
or secondary TCP/IP comm path is operational.

More About the Shared Disk Comm Path
The shared disk comm path can be used as a channel of last resort in the case where all other communication
has been severed. If the shared disk comm path were to be lost as well, it is very likely that at least one of theservers would not be able to access the storage subsystem, thereby preventing a "split-brain" situation where
both servers may access the same disk resource simultaneously.
CAUTIONS:l

A SteelEye Protection Suite configuration should include no more than one shared disk comm path
between any two servers in the cluster.

l

Before using shared disk comm paths on JBOD or Host-based RAID, be sure to test the comm pathfor reliability when a member of the cluster is shut down or out of service. Sometimes, in configurations
using JBOD or Host-based RAID, the comm path will fail to go down when a cluster member goes
down, and therefore a failover is not initiated.

SteelEye Protection Suite for Windows Technical Documentation
Page 5SteelEye Protection Suite Heartbeat

SteelEye Protection Suite Heartbeat
The heartbeat is a key SteelEye Protection Suite fault detection mechanism. The heartbeat is a periodic
signal sent over the comm path between a pair of servers. The regular signals tell each server that the other isstill active. When you define your comm path, the definition sets the heartbeat signal interval in seconds andspecifies the number of consecutive heartbeats a server can miss before marking the comm path as dead.
When the SteelEye Protection Suite servers mark a comm path as dead, inter-node communications
immediately commence over the comm path with the next highest priority. Only when the server fails toreceive the heartbeat signal on all comm paths does SteelEye Protection Suite initiate the safety check todetermine the need for failover recovery.

Heartbeat Interval
The SteelEye Protection Suite heartbeat interval is the number of seconds between heartbeat signals thatverify the servers are alive. The default (and recommended) interval is six seconds.
l

If you wish to set the interval at the minimum allowed value of four seconds, then you should ensurethat the communication path is configured on a private network and tested thoroughly since values
lower than five seconds create a risk of false failovers due to network interruptions.

l

The heartbeat interval works in conjunction with the maximum heartbeat misses, which has a default
value of five (recommended). Setting the maximum heartbeat misses to a lower number (3 or 4) cancreate a risk of false failovers. Be sure to test thoroughly in your environment.

lSetting these values too high can effectively disable SteelEye Protection Suite's ability to detect a
failure.

Safety Check
When all the communications paths on a server are DEAD, SteelEye Protection Suite assumes that thepaired system is DEAD (or down) and attempts to fail over. However, SteelEye Protection Suite performs asafety check to ensure that the failure occurred in the server rather than just the comm paths.
The safety check queries on the network (through LAN Manager) to see if the machine still exists. One of two
events can occur:l

System is alive. If the check receives a response that the system does exist on the network, it aborts
the failover and reports the following message to the LifeKeeper event log:
SAFETY CHECK FAILED: COMM_DOWN ABORTEDl

System is dead. If the check does not receive a response within a specified time-out period (default 8
seconds), the machine is assumed to be down and the failover proceeds.

SteelEye Protection Suite performs this check only once, after all comm paths go down. If the safety checkdetects that the system is alive, failover is aborted. SteelEye Protection Suite does not re-initiate failover until
all of the following events happen in sequence:

SteelEye Protection Suite for Windows Technical Documentation
Page 6

Resource Hierarchies

1. At least one of the comm paths comes back ALIVE.
2. All comm paths again go DEAD.
3. The safety check activates and does not detect that the paired system is alive.

Resource Hierarchies
The LifeKeeper GUI enables you to create a resource hierarchy on one server and extend that hierarchy to one
or more backup servers. SteelEye Protection Suite then automatically builds the designated hierarchies on allservers specified. SteelEye Protection Suite maintains hierarchy information in a database on each server. If
you use the command line interface, you must explicitly define the hierarchy on each server.
After you create the resource hierarchy, SteelEye Protection Suite manages the stopping and starting of theresources within the hierarchy. The following topics provide background for hierarchy definition tasks:lResource Statesl

Hierarchy RelationshipslShared EquivalencieslResource Hierarchy Information

Hierarchy Relationships
SteelEye Protection Suite allows you to create relationships between resource instances.The primary
relationship is a dependency. For example, one resource instance depends on another resource instance forits operation. The combination of resource instances and dependencies is the resource hierarchy.

In the example above, MSExch.0 is an Exchange resource, which has three dependencies - a DNS resource(DNS.0) and two volume resources (Vol.L and Vol.X).
The dependency relationships specified by the resource hierarchy tell SteelEye Protection Suite theappropriate order for bringing resource instances in service and out-of-service. In the example resource
hierarchy, SteelEye Protection Suite cannot bring the MSExch.0 resource into service until it successfully
brings into service the DNS and volume instances.

SteelEye Protection Suite for Windows Technical Documentation
Page 7

Resource Hierarchy Information

Resource Hierarchy Information
A snapshot of information about all the resources defined for a server can be displayed in the Server
Properties dialog box.

Other resource information can be viewed in the Status Table (main GUI window) or in the Viewing Resource
Properties topics.

Resource States
The LifeKeeper GUI status display shows the resources that are defined across all servers to which it isconnected. The left pane of the status window displays the Resource Hierarchy Tree which reflects theglobal resource status (that is, the status of the resource across all servers).
The right pane of the status window contains columns showing the status of each individual resource on eachserver.

The sample above shows a hierarchy MSExch.0 with a status of In Service, Protected (ISP). The resource
Vol.M exists only on CARDINAL. Thus it is In Service, but it has no failover protection, which is indicated by
the yellow triangle.

SteelEye Protection Suite for Windows Technical Documentation
Page 8

Shared Equivalencies

For more details on resource states, see Viewing the Status of Resources.

Shared Equivalencies
When you create a SteelEye Protection Suite resource hierarchy, you create the hierarchy initially on the
primary server and extend the hierarchy to a backup server. Most resource instances can be active on only
one server at a time. For such resources, SteelEye Protection Suite defines a second kind of relationshipcalled a shared equivalency that ensures that when the resource is in-service on one server, it is out-ofservice on the other servers on which it is defined.
In the example below, a shared equivalency exists between each hierarchy level on a pair of servers. For
example, the MSExch.0 resource exists on both servers, and there is a shared equivalency between the two
instances of MSExch.0 (just as there is between the one DNS instance and the two volume instances).

SteelEye Protection Suite for Windows Technical Documentation
Page 9Chapter 2: Installation Guide
For complete information on installing SteelEye Protection Suite for Windows, see the SteelEye Protection
Suite for Windows Installation Guide located on the SIOS Technical Documentation site:l

http://docs.us.sios.com/#SPS4W

SteelEye Protection Suite for Windows Technical Documentation
Page 11

SteelEye Protection Suite for Windows Technical Documentation
Page 12

Chapter 3: Configuration

Chapter 3: Configuration
If the SteelEye Protection Suite environment has been installed, the SteelEye Protection Suite software canbe configured on each server in the cluster. The topics in this section will help with this configuration.

SteelEye Protection Suite Configuration Steps
Follow the steps below which contain links to topics with additional details. Perform these tasks on eachserver in the cluster.
1. Ensure that the LifeKeeper services are running by checking the Services in the Administrative
Tools on the Control Panel. You should see both LifeKeeper and LifeKeeper External Interfaces
services. If they are not both running, start them now.
For additional information, see Starting and Stopping LifeKeeper.
2. Users with administrator privileges on a SteelEye Protection Suite server can run the application clientfrom that server. Click Start, then point to All Programs, then SteelEye->LifeKeeper->LifeKeeper(Admin Only).
After the application is loaded, the LifeKeeper GUI appears and the Cluster Connect dialog isdisplayed. Enter the Server Name you wish to connect to, followed by the login and password.
3. Create Communication Paths. Before you can activate SteelEye Protection Suite protection, youmust create the communication path (heartbeat) definitions within LifeKeeper.
4. Set your Server Shutdown Strategy. This tells LifeKeeper whether to switch over resources when you
initiate an orderly shutdown.
5. SteelEye Protection Suite is now ready to protect your applications. The next step depends on which
SteelEye Protection Suite Recovery Kit(s) you will be using:l

If you are using a Core Recovery Kit, then refer to the topics for creating Volume, DNS, IP , File Share,
LAN Manager, or Generic Application hierarchies.

l

If you are using the optional Microsoft SQL Server Recovery Kit, refer to the Microsoft SQL Server
Recovery Kit Administration Guide for instructions on creating and extending your resource
hierarchies.

Active-Active Grouping
In an active/active group, all servers are active processors; they also serve as the backup server for resource
hierarchies on other servers.
For example, the configuration example below shows two active/active pairs of servers. Server 1 isprocessing AppA, but also serves as the backup server for AppX running on Server 2. The reverse is also true.
Server 2 is processing AppX, but also serves as the backup server for AppA running on Server 1. Servers 3
and 4 have the same type of active/active relationships.

SteelEye Protection Suite for Windows Technical Documentation
Page 13

Active-Standby Grouping

Although the configurations on Servers 1 and 2 and the configurations on Servers 3 and 4 are similar, there is a
critical difference. For the AppA and AppX applications, Servers 1 and 2 are the only servers available forgrouping. They are the only servers that have access to the shared resources.
AppB and AppC, however, have several grouping options because all four servers have access to the AppB
and AppC shared resources. AppB and AppC could also be configured to failover to Server1 and/or Server2
as a third or even fourth backup system.

Note: Because SteelEye Protection Suite applies locks at the volume level, only one of the four systems
connected to the AppB and AppC disk resources can have access to them at any time. Therefore, when
Server 3 is actively processing AppB, those disk resources are no longer available to Servers 1, 2, and 4,
even though they have physical connections.

Active-Standby Grouping
In an active/standby group, the primary server is processing, and the back-up servers are standing by in caseof a failure on the primary server. The standby systems can be smaller, lower-performance systems, but theymust have the processing capability to assure resource availability should the primary server fail.

SteelEye Protection Suite for Windows Technical Documentation
Page 14

Intelligent Versus Automatic Switchback

A standby server can provide backup for more than one active server. For example in the figure above,
Server2 is the standby server in three active/standby resource pairs. The SteelEye Protection Suite resource
definitions specify the following active/standby paired relationships:l

AppA on Server1 fails over to Server2.

l

AppB on Server3 fails over to Server2.

l

AppC on Server4 fails over to Server2.

Be aware of these three critical configuration concepts when you are considering configurations with multiple
active/standby groups:lDisk ownership. Different active applications cannot use disk slices on the same volume. SteelEye
Protection Suite applies locks at the volume level. When the SCSI locks are applied, only one systemon the shared SCSI bus can access volumes on the disk device. In the example, Server3 hasownership of the AppB disk resources and Server4 owns the AppC resources.

l

Processing capacity. Although it is unlikely that Servers 1, 3, and 4 would fail at the same time, youmust take care when designating a standby server to support multiple resource relationships so thatthe standby server can handle all critical processing should multiple faults occur.

l

SteelEye Protection Suite administration. In the example, Server2 provides backup for three otherservers. In general, it is not desirable to administer the SteelEye Protection Suite database on the
different logical groups simultaneously. You should first create the resources between the spare andone active system, then between the spare and another active system and so on.

Intelligent Versus Automatic Switchback
By default, the switchback setting of a resource is intelligent. This means that once the failover occurs forthat resource from Server A to Server B, the resource remains on Server B until another failure or until anadministrator intelligently switches the resource to another server. Thus the resource continues to run onServer B even after Server A returns to service. Server A now serves as a backup for the resource.
In some situations, it may be desirable for a resource to switch back automatically to the original failed serverwhen that server recovers. SteelEye Protection Suite offers an automatic switchback option as analternative to the normal intelligent switchback behavior described above. This option can be selected for

SteelEye Protection Suite for Windows Technical Documentation
Page 15

SteelEye Protection Suite Configurationsindividual resource hierarchies on individual servers. If automatic switchback is selected for a resource
hierarchy in the In-Service-Protected (ISP) state running on a given server and that server fails, the resource
hierarchy is failed over to a backup system; when the failed server recovers, the hierarchy is automaticallyswitched back to the original server.
Notes:
l

If using data replication (DataKeeper), you must choose intelligent switchback. Automatic
switchback is not supported.

l

Checks for switchback are only made either when LifeKeeper starts or when a new server is added tothe cluster; they are not performed during normal cluster operation.

l

SteelEye Protection Suite never performs an automatic switchback from a higher priority server to alower priority server.

l

If there is a dependency between two resources with different switchback strategies, the switchback
strategy of the parent resource takes precedence.

SteelEye Protection Suite Configurations
SteelEye Protection Suite works on the basis of resource hierarchies you define for groups of two or moreservers. The following three topics introduce the SteelEye Protection Suite failover configuration concepts.
lCommon Hardware ComponentslSystem Grouping ArrangementslResource Hierarchies

Common Hardware Components
All SteelEye Protection Suite configurations share these common components as illustrated in the diagram
below:
1. Server Groups. The basis for the fault resilience provided by SteelEye Protection Suite is clustered
Windows 2003 servers. The servers, also referred to as SteelEye Protection Suite nodes, do not haveto be the same hardware platform.
2. Communication paths for heartbeat. It is strongly recommended that each pair of servers in thegroup share at least two communication paths (comm paths), although only one is required. To avoid
unnecessary failover due to communication failure, you should configure your redundant comm paths
using different protocols and communication media, for example TCP/IP (or socket). SteelEye
Protection Suite uses the comm paths to coordinate resource availability for the fault-detection
heartbeat, a periodic message between nodes and for switchover of resources. (See Overview ofCommunication Paths.)
3. Shared data resources. SteelEye Protection Suite can recover and restore shared or mirrored data,applications and communication resources. SteelEye Protection Suite controls access at the volume(drive letter) level. In case of a server failure, SteelEye Protection Suite automatically switches
availability of protected resources to an active server. Peripheral devices that are to be shared between

SteelEye Protection Suite for Windows Technical Documentation
Page 16

System Grouping Arrangements

systems must be packaged in external peripheral cabinets. See the Configuring Your Storage topic for
information to help you configure your shared storage.
4. Shared communication for user connections. SteelEye Protection Suite can also automaticallymanage the switchover of user communication resources, such as IP addresses, computer alias
names and file share lists. Switchover of communication resources allows users to connect using theirnormal paths.

System Grouping Arrangements
A resource hierarchy is defined on a cluster of SteelEye Protection Suite servers. For a given hierarchy, eachserver is assigned a priority, with one (1) being the highest possible priority. The primary, or highest priority,
server is the computer you want to use for the normal operation of those resources. The server having thesecond highest priority is the backup server to which you want SteelEye Protection Suite to switch thoseresources should the primary server fail.
In an active/active group, all servers are active processors, but they also serve as the backup server forresource hierarchies on other servers. In an active/standby group, the primary server is processing and any
one of the backup servers can be configured to stand by in case of a failure on the primary server. The standby
systems can be smaller, lower-performance systems, but they must have the processing capability to assure
resource availability should the primary server fail.
Your physical connections and access to the shared resources determine your grouping options. To begrouped, servers must have communications and heartbeat paths installed and operational, and all servers
must have access to the disk resources through a shared SCSI or Fibre Channel interface. For example in thefollowing diagram, there is only one grouping option for the resource AppA on Server 1. Server 2 is the only
other server in the configuration that has shared access to the AppA database.

SteelEye Protection Suite for Windows Technical Documentation
Page 17System Grouping Arrangements

The resource AppB on Server 3, however, could be configured for a group including any one of the other threeservers, because the shared SCSI bus in this example provides all four servers in the configuration access to
the AppB database.

SteelEye Protection Suite for Windows Technical Documentation
Page 18

Chapter 4: SteelEye Protection Suite Administration
Overview
SteelEye Protection Suite provides two administration interface options:l

LifeKeeper GUIl

LifeKeeper command line interface

The LifeKeeper GUI is used for the following tasks which are listed in the typical sequence for configuring
SteelEye Protection Suite.
lCommunication path definition. You must define the communication paths you want to use before
you define any other resource instances or hierarchies in LifeKeeper. This can be done using the Editmenu or the Create Comm Path icon on the GUI toolbar.

lResource definition. As you install recovery kits, the resource types supported by those kits appear
in the Create Resource Hierarchy dialog box.For most recovery kits, the necessary dependencies
will be created automatically.

l

Monitoring. The LifeKeeper GUI's status display provides a visual status of resources protected by
SteelEye Protection Suite on the connected servers. In addition, SteelEye Protection Suite maintains
log files which you can view through the GUI.

l

Manual intervention. You may need to stop servers or specific resources for maintenance or otheradministrative actions. The LifeKeeper GUI provides menu functions that allow you to bring specificresources in and out of service. Once applications have been placed under SteelEye Protection Suite
protection, they should be started and stopped only through SteelEye Protection Suite.

For initial step-by-step configuration instructions, see SteelEye Protection Suite Configuration Steps.
See the GUI Tasks and Maintenance Tasks topics for detailed instructions on performing SteelEye Protection
Suite administration, configuration and maintenance operations using the GUI.
Note: SteelEye Protection Suite is set up so that the SteelEye Protection Suite services are run by the local
system account on each server. SteelEye Protection Suite should not be changed to run as any other user
account.

Administrator GUI Tasks
Editing Server Properties
1. To edit the properties of a server, begin just as you would for viewing server properties.

SteelEye Protection Suite for Windows Technical Documentation
Page 20

Set Server Shutdown Strategy

2. If you are logged in to that server with the appropriate permissions, the following items will be editable.
lShutdown StrategylAutomatic Failover ConfigurationlServer Configuration (only for servers with specialized configuration settings)

3. Once you have made changes, the Apply button will be enabled. Clicking this button will apply yourchanges without closing the window.
4. When you are finished, click OK to save any changes and close the window, or Cancel to close thewindow without applying changes.

Set Server Shutdown Strategy
The Shutdown Strategy is a configuration option that governs whether or not resources are switched over to a
backup server when a server is shut down. The options are:
Do Not Switch Over
Resources (default)

SteelEye Protection Suite will not switch over resource hierarchies during
an orderly shutdown.

Switch Over Resources

SteelEye Protection Suite will switch over all resource hierarchies during
an orderly shutdown.

Restriction: The Switch Over on Shutdown setting is not supported with SteelEye DataKeeper resources.
The Shutdown Strategy is set by default to ”Do Not Switch Over Resources.” You should decide which
strategy you want to use on each server, and if you wish, change the Shutdown Strategy to "Switch Over
Resources".
For each server in the cluster:
1. Bring up the Server Properties dialog just as you would for viewing server properties.
2. On the General Tab of the Server Properties dialog, select the Shutdown Strategy.
Note: The LifeKeeper process must be running during an orderly shutdown for the Shutdown Strategy to havean effect. If LifeKeeper is not running or the resources are not currently in service, the resources will notswitch over.

Server Properties
The Server Properties dialog is available from the Edit Menu or from a server popup menu. This dialog
displays the properties for a particular server. When accessed from the Edit menu, you can select the server.
The Server Properties dialog updates itself when the selected server changes.
The OK button applies any changes that have been made and then closes the window. The Apply button
applies any changes that have been made. The Cancel button closes the window without saving any changes
made since Apply was last clicked.

SteelEye Protection Suite for Windows Technical Documentation
Page 21

Server PropertieslName. Name of the selected server.

lPermission.The permission level of the user currently logged into that server. These are the possible
permission values:

l

l

l

Administrator - the user can perform any SteelEye Protection Suite task.

lOperator- the user can monitor SteelEye Protection Suite resource and server status, and canbring resources in service and take them out of service.

lGuest- the user can monitor SteelEye Protection Suite resource and server status.

State. Current state of the server. These are the possible server state values:l

ALIVE- server is available.

lDEAD- server is unavailable.

l

UNKNOWN - state could not be determined. The GUI server may not be available.

ShutdownStrategy (editable). The setting that governs whether or not resources which are in service

SteelEye Protection Suite for Windows Technical Documentation
Page 22

Server Properties

are switched over to a backup server in the cluster when a server is shut down. The setting "Switch
Over Resources" indicates that resources will be brought in service on a backup server in the cluster.
The setting "Do not Switch Over Resources" indicates that resources will not be brought in service
on another server in the cluster.
lServer Name. Automatic failover capabilities from the local server to other servers in the cluster may
be configured here. All servers in the cluster should be operational (i.e. at least one SteelEye
Protection Suite comm path must be active) as inactive servers are not listed. The name of each active
server in the cluster is listed, excluding the local server. For each server, two types of failover
capabilities are configurable. By default, all failover capabilities are enabled.
lDisable Resource Failover- Select the remote server(s) to be disqualified as a backup server
for any failed resource hierarchy on the local server. When disabled, the designated server isdisqualified as a failover site if a local resource fails. Unselect to re-enable automatic failover
capabilities.

lDisable System Failover- Select the remote server(s) to be disqualified as a backup server for
a complete failure of the local server. When disabled, the designated server is disqualified as a
failover site if the local server completely fails. Unselect to re-enable automatic failover
capabilities.

Note: If all remote servers are disabled for resource failovers, then the failed resource will be marked as"Failed" and no additional quick check or deep check monitoring will be performed for the failed
resource. However, the failed resource as well as other dependent resources in the hierarchy will not be
removed from service and no failover will be attempted.

SteelEye Protection Suite for Windows Technical Documentation
Page 23

Server PropertieslServer. The server name of the other server to which the communication path is connected in the
SteelEye Protection Suite cluster.

lType. The type of comm path between the server in the list and the server specified in the Server field(TCP/IP or Shared Disk).

lState. State of the comm path in the LifeKeeper Configuration Database (LCD). These are the possiblecomm path state values:l

ALIVE - functioning normallyl

DEAD - no longer functioning normallyl

UNKNOWN - state could not be determined. The GUI server may not be available.

lAddress/Device. The IP address or device name that this comm path uses.

lComm Path Status. Summary comm path status determined by the GUI based on the state of thecomm paths in the LifeKeeper Configuration Database (LCD). These are the possible comm pathstatus values displayed below the detailed text in the lower panel:

SteelEye Protection Suite for Windows Technical Documentation
Page 24

Server Propertiesl

NORMAL - all comm paths functioning normallyl

FAILED- all comm paths to a given server are deadl

UNKNOWN- comm path status could not be determined. The GUI server may not be available.

l

WARNING- one or more comm paths to a given server are dead, or only one comm path exists.

l

DEGRADED- one or more redundant comm paths to a given server are deadl

NONE DEFINED - no comm paths definedlName.The tag name of a resource instance on the selected server.

lApplication. The application name of a resource type (gen, scsi, ...)

l

Resource Type.The resource type, a class of hardware, software, or system entities providing aservice (for example, volume, TCP/IP, SQL...)lState. The current state of a resource instance.

SteelEye Protection Suite for Windows Technical Documentation
Page 25

Disabling Automatic Failoverl

ISP - In-service locally and protected.

l

ISU - In-service locally, but local recovery will not be attempted.

l

OSF - Out-of-service, failed.

l

OSU - Out-of-service, unimpaired.

l

ILLSTATE - Resource state has not been initialized properly by the resource initialization
process which is run as part of the SteelEye Protection Suite startup sequence. Resources inthis state are not under SteelEye Protection Suite protection.

l

UNKNOWN - Resource state could not be determined. The GUI server may not be available.

Disabling Automatic Failover
In the event that the primary server has attempted and failed local recovery or failed completely, most server
administrators will want SteelEye Protection Suite to automatically restore the protected resource(s) to a
backup server. This is the default SteelEye Protection Suite behavior. However, some administrators may notwant the protected resource(s) to automatically go in service at a recovery site; for example, if SteelEye
Protection Suite is installed in a WAN environment where the network connection between the servers may
not be reliable in a disaster recovery situation.
Automatic failover is enabled by default for all protected resources. To disable automatic failover for protectedresources or to prevent automatic failover to a backup server, use the Failover section located on the
General tab of Server Properties to configure as follows:
For each server in the cluster:
1. Bring up the Server Properties dialog just as you would for viewing server properties.
2. Select the General tab. In the Failover section of the Server Properties dialog, check the server todisable system and resource failover capabilities. By default, all failover capabilities of SteelEye
Protection Suite are enabled.
In the Disable System Failover column, select the server to be disqualified as a backup server for acomplete failure of the local server.
In the Disable Resource Failover column, select the server to be disqualified as a backup server for any
failed resource hierarchy on this local server. Resource failovers cannot be disabled without first disabling
system failover capabilities.
To commit your selections, press the Apply button.

SteelEye Protection Suite for Windows Technical Documentation
Page 26

Creating a Communication Path

Creating a Communication Path
Before configuring a SteelEye Protection Suite communication path between servers, verify the hardware andsoftware setup. See the Configuration section for requirements.

Configuration Notesl

You should configure no more than one shared disk comm path between servers.

lShared Disk comm paths are supported for two-server clusters only.

l

For greater than two-server clusters, use multiple TCP/IP comm paths for heartbeat redundancy. A
priority value is used to tell SteelEye Protection Suite the order in which TCP/IP paths to a given
remote server should be used.

l

IMPORTANT: Supported configurations require that you define redundant comm paths so that the
failure of a single communication line will not cause an unnecessary failover. If a single comm path isused and the comm path fails, SteelEye Protection Suite hierarchies may come in service on multiple
servers simultaneously. This is known as "split-brain". Additionally, heavy network traffic on a TCP/IP

SteelEye Protection Suite for Windows Technical Documentation
Page 27

Creating a Comm Pathcomm path can result in unexpected behavior, including false failovers and SteelEye Protection Suite
initialization problems.

Creating a Comm Path
1. Select one of the servers, and then select Create Comm Path from the server context menu or server
context toolbar.
2. Select one or more Remote Servers in the list box. If a remote server is not listed in the list box (i.e. it
is not yet connected to the cluster), you may enter it using Add Server. You must make sure that the
network addresses for both the local and remote servers are resolvable (for example, with DNS or
added to the /etc/hosts file). Click Next.
3. Select either TCP or DISK for Device Type and click Next.
4. Provide all required information for the Device Type that you selected and click Next after each step.
Refer to the table below for additional information on each configuration field.

Field

Tips

For TCP/IP Comm Path...
HeartbeatIntervalEnter a value between 4 and 15 for the heartbeat interval, which is the number of
seconds between heartbeat signals that verifies the servers are alive). The default = 6.

Maximum
Heartbeat
MissesEnter a value between 3 and 99. This is the number of consecutive heartbeat signals thatcan be missed before the comm path is marked as dead. The default = 5.

Local IP
Address

Enter the IP address to be used by the local server for this comm path.

PriorityEnter the priority for the comm path on the local server. The priority will be used todetermine the order that the comm paths between the two servers will be used. Priority 1
is the highest, 99 is the lowest.

Remote IP
Address

Enter the IP address to be used by the remote server for this comm path.

Port
NumberEnter a unique port number to be used by the TCP/IP service. This number must be
between 1500 and 10000. SteelEye Protection Suite offers a default which you canchange.

For Shared Disk Comm Path...
HeartbeatIntervalEnter a value between 4 and 15 for the heartbeat interval, which is the number of
seconds between heartbeat signals that verifies the servers are alive). The default = 6.

Maximum
Heartbeat
MissesEnter a value between 3 and 99. This is the number of consecutive heartbeat signals thatcan be missed before the comm path is marked as dead. The default= 5.

SteelEye Protection Suite for Windows Technical Documentation
Page 28

Verifying the Comm Path

Field

Tips

PriorityEnter the priority for the comm path on the local server. The priority will be used todetermine the order that the comm paths between the two servers will be used. Priority 1
is the highest, 99 is the lowest.

Drive Letter

The drive letter associated with the shared volume to be used for the shared disk commpath. This must be the same letter on both servers.

5. Click Create. The dialog should display a message indicating the network connection is successfully
created. If the output panel is enabled, the message will be displayed there as well. Click Next.
6. If you selected multiple Local IP Addresses or multiple Remote Servers and the Device Type was set
to TCP, then you will be taken back to Step 4 to continue with the next Comm Path. If you selected
multiple Remote Servers and the Device Type was set to DISK, then you will be taken back to Step 3
to continue with the next Comm Path.
7. Click Done when presented with the concluding message.

Verifying the Comm Path
You can verify the comm path by viewing the Server Properties dialog. You should see an Alive status.
In addition, check the server icon in the right pane of the GUI. If this is the first comm path thathas been created, the server icon shows a yellow heartbeat indicating that one comm path is
ALIVE but there is no redundant comm path.
The server icon will display a green heartbeat when there are at least two comm paths ALIVE.
If the comm path does not activate after a few minutes, verify that the paired server's computer name iscorrect.

Deleting a Communication Path
1. Select one of the servers, and then select Delete Comm Path from the server context menu or server
context toolbar.
2. Select the communications path(s) that you want to delete and click Delete Comm Path(s).
3. If the output panel is enabled, the dialog closes, and the results of the commands to delete thecommunications path(s) are shown in the output panel. If not, the dialog remains up to show theseresults, and you click Done to finish when all results have been displayed.

Working With Resource Hierarchies
The topics in this section describe the tasks that are common across any type of resource hierarchy. Thesetasks function very much the same regardless of whether you are working with a core Recovery Kit or an
optional Recovery Kit.

SteelEye Protection Suite for Windows Technical Documentation
Page 29Creating Resource Hierarchies

The documentation for the optional SteelEye Protection Suite Recovery Kits is available in the SteelEye
Protection Suite for Windows Technical Documentation.

Creating Resource Hierarchies
1. Select the server, and then select Create Resource Hierarchy from the server context menu or server
context toolbar.
2. A dialog entitled Create Protected Application will appear with a list of all recognized recovery kits
installed within the cluster. Select the Recovery Kit that builds resource hierarchies to protect yourapplication and click Next.
3. Continue through the succeeding dialogs, entering whatever data is needed for the type of resource
hierarchy that you are creating.
4. After receiving the message that the resource hierarchy has been created successfully, click Next tocontinue. If SteelEye Protection Suite has detected a problem, an ERROR will appear in theinformation box, the partially created resource hierarchy will be removed and the Next button will bedisabled. In that case, click Cancel to exit the Wizard.

SteelEye Protection Suite Application Resource Hierarchies
If you install SteelEye Protection Suite without any optional recovery kits, the Application to Protect list
includes options DNS, File Share List, Generic Application, IIS, IP Address, LAN Manager and Volume
by default. The Generic Application option may be used for applications that have no associated recovery
kits.
See the following topics describing these available options:lCreating a DNS Resource HierarchylCreating a File Share Resource HierarchylCreating a Generic Application Resource HierarchylCreating an IP Address Resource HierarchylCreating a LAN Manager Resource HierarchylCreating a Volume Resource Hierarchy

Microsoft SQL Server Recovery Kit
Installing Microsoft SQL Server Recovery Kit adds entries to the Application to Protect list. Refer to theMicrosoft SQL Server Recovery Kit Administration Guide for instructions on creating the required resource
hierarchies.

Creating a DNS Resource Hierarchy
The DNS Recovery Kit provides a mechanism to update the DNS A record and associated PTR record (ifSteelEye Protection Suite for Windows Technical Documentation
Page 30

Creating a DNS Resource Hierarchy

exists) of the primary server or a LifeKeeper alias name on all DNS servers in your configuration. The kit
allows selection of the name for the primary server or a LifeKeeper alias name in DNS which will be modified
with the IP address of a backup server when failover or switchover occurs.
Note A "LifeKeeper alias" is a DNS 'A' record that is created using the name specified during
the LifeKeeper DNS resource create process.
The example below shows the changes that occur on the DNS Server for a protected DNS resource after
failover or switchover.
Primary Server: ExchSrvr1 (172.17.10.24/255.255.255.0)
Backup Server: ExchSrvr2 (172.16.10.25/255.255.255.0)
DNS Server:
Zone: mydomain.com
Before failover:
A Record

ExchSrvr1

172.17.10.24

ExchSrvr2

172.16.10.25

PTR Record 24.10.17.172.in-addr.arpa ExchSrvr1.mydomain.com
25.10.16.172.in-addr.arpa ExchSrvr2.mydomain.com
After Failover:
A Record

ExchSrvr1

172.16.10.25

ExchSrvr2

172.16.10.25

PTR Record 25.10.16.172.in-addr.arpa ExchSrvr1.mydomain.com
25.10.16.172.in-addr.arpa ExchSrvr2.mydomain.com
DNS resource configuration requires that all cluster nodes are members of a domain and that domain includes
a DNS server for each SteelEye Protection Suite node. During DNS resource creation and extension, those
DNS server names for each cluster node are requested by the SteelEye Protection Suite Resource
Configuration Wizard as shown below.
SteelEye Protection Suite cluster nodes may also be members of different domains; however this is notrecommended. When cluster nodes are members of different domains, the domain administrator ID andpassword for all domains must be identical and the local server administrator ID and password for all cluster
nodes should be the same. This facilitates LifeKeeper GUI login using local server accounts when cluster
nodes are members of different domains.
During creation of a DNS resource, enter the primary server name or a LifeKeeper alias name which will be
modified on the primary DNS server upon failover or switchover. If the server is multi-homed, select the IP
address of the A record to be updated. The A and PTR records, based on the selection made during creation,
will be created if they do not exist on the DNS server. The records are created on the primary DNS server
specified during create and on all of the NS (Name server) servers who are the primary zone servers for the A
record.

SteelEye Protection Suite for Windows Technical Documentation
Page 31

Creating a DNS Resource Hierarchy

The deep check script, which monitors the DNS resource, will check for the existence of the A record of theprotected server (either primary server name or LifeKeeper alias name) on all of the DNS servers. If the A
record mapping to the correct IP address is not found on at least one of the DNS servers, the deep check
script will fail which will trigger local recovery (if enabled) and the A and PTR records will be recreated on all of
the primary DNS servers.
To create a DNS resource hierarchy from the primary server, you should complete the following steps:
1. Select the server, and then select Create Resource Hierarchy from the server context menu or server
context toolbar.
2. The Create Protected Application window appears displaying the Primary and Backup Servers inyour cluster. Select the correct systems for this configuration.
3. A dialog appears with a list of all recognized recovery kits installed within the cluster. Select DNS andclick Next.
4. The Create Protected Application will prompt you to enter the following information. When the Backbutton is active in any of the dialog boxes, you can go back to the previous dialog box. This isespecially helpful should you encounter an error that might require you to correct previously enteredinformation. If you click Cancel at any time during the sequence of creating your hierarchy, SteelEye
Protection Suite will cancel the entire creation process.

Field

Tips

Resource
DNS Tag

Select or enter a unique tag for the DNS resource instance you are creating. This fieldprovides a default tag name which you can change if desired.

A Record
Owner NameEnter the name of the server whose A and PTR records will be updated in DNS. If you want
to update DNS records that belong to a LifeKeeper alias of the server, enter the LifeKeeper
alias name here. SteelEye Protection Suite will protect DNS records for the LifeKeeper
alias name in DNS mapping to the IP address you will select later.

IP AddressEnter the IP address of the server or LifeKeeper alias name whose A record will be
updated. The A record mapping to this IP address will be updated upon failover switchover.

DNS Server
Name (Fully
Qualified)Enter the fully qualified name of a DNS server, in the form of <DNS Server Name><mydomain>.com, where the Resource Records can be modified. The DNS server shouldbe accessible from the primary server, preferably in the same site. Upon failover orswitchover, records on the NS (Name Server) in the environment will also be updated.

Enter the user name of the Windows DNS/Domain administrator. This user account should
DNS
have privileges to make changes in the DNS configuration and should be a member of the
Administrative "Domain Admins" group in the same domain as the DNS server. Enter the user ID in
User Name<DomainName>\<UserID> format where <DomainName> is the NetBIOS name of thedomain.
DNS
Administrator
Password

Enter the password associated with the Windows DNS/Domain administrator account.

SteelEye Protection Suite for Windows Technical Documentation
Page 32

Creating a File Share Resource Hierarchy

5. After receiving the message that the resource hierarchy has been created successfully, click Next tocontinue. If SteelEye Protection Suite has detected a problem, an ERROR will appear in the information box, the partially created resource hierarchy will be removed, and the Next button will be disabled. In that case, click Cancel to exit the Wizard.

Creating a File Share Resource Hierarchy
The Windows File Manager function allows you to define file shares. If you install the SteelEye Protection
Suite LAN Manager Recovery Kit, you can create a file share list resource that includes one or more of thosefile shares.

Criteria for File Share Resources
Not all file shares are available to be shared. The following statements will help you to determine which files
shares are available.
l

The share name must reside on a volume that is shared between the machines.

l

The shared volume can already be protected between the two machines where the file share resource
is being created; however, it should not exist on a third machine until you extend the file sharehierarchy to that machine.

l

If the share name already exists on the second machine then both share names must point to the exact
same directory.

l

If the share name is already protected on either machine, it is not eligible.

l

It is the responsibility of the administrator to ensure that any share names created actually point todirectories. It is possible to create a share name for a directory and then delete the directory. If this is
the case then the administrator should ensure that the share name is deleted as well.

Note: After a file share has been brought in-service on a backup server it becomes a share on that machine.
The share remains even after the hierarchy is deleted.

File Share Resource Creation
To create a file share resource hierarchy, follow the steps below.
1. Select the server, and then select Create Resource Hierarchy from the server context menu orserver context toolbar.
2. The Create Protected Application window appears displaying the Primary and Backup Servers inyour cluster. If not already selected, choose the appropriate systems to configure.
3. A dialog appears with a list of all recognized recovery kits installed within the cluster. Select File
Share List and click Next.
4. The Configuration Wizard will prompt you to enter the following information. When the Back buttonis active in any of the dialog boxes, you can go back to the previous dialog box. This is especiallyhelpful should you encounter an error that might require you to correct previously entered information. If

SteelEye Protection Suite for Windows Technical Documentation
Page 33

Creating a Generic Application Resource Hierarchy

you click Cancel at any time during the sequence of creating your hierarchy, SteelEye Protection Suite
will cancel the entire creation process.

Field

Tips

File
Share
and Path
Name

Select one or more file shares to be protected. If "none found" is displayed, verify that thevolume where the file share exists is under SteelEye Protection Suite protection.

File
Select or enter a unique tag for the File Share resource instance you are creating. This field
Share
provides a default tag name FSList.x (where x is a number assigned by SteelEye
Resource
Protection Suite, starting with ) which you can change if desired.
Tag
5. After all of the data is entered, the Next button will appear. When you click Next, SteelEye Protection
Suite will create and validate your resource hierarchy.
6. After receiving the message that the resource hierarchy has been created successfully, click Next tocontinue. If SteelEye Protection Suite has detected a problem, an ERROR will appear in theinformation box, the partially created resource hierarchy will be removed, and the Next button will bedisabled. In that case, click Cancel to exit the Wizard.

Creating a Generic Application Resource Hierarchy
Use this option to protect an application that has no associated recovery kit.

Before Creating a Resource Hierarchy
1. The first task is to create scripts for the five basic SteelEye Protection Suite action functions:l

RestorelRemovel

Quick Checkl

Deep Checkl

Local Recovery

Perl and VB Script templates are provided for these scripts in $LKROOT\admin\kit\app\templates. Be
sure to copy these templates to another directory on the same volume as $LKROOT before
customizing and testing them for the application that you wish to protect.
Note: If you want to use optional Create, Extend and Delete scripts, also include them in the folder
with your other scripts. The script selection wizard will search for them by these names (andextension) and automatically enter them for you.
2. For applications depending upon other resources such as a volume or IP address, create each of theseresources separately before creating your Generic Application resource hierarchy. You can create theSteelEye Protection Suite for Windows Technical Documentation
Page 34

Creating Your Resource Hierarchy

appropriate dependencies later using Add Dependency.

Creating Your Resource Hierarchy
Now you are ready to create the Generic Application resource hierarchy using the modified scripts.
1. Select the server, and then select Create Resource Hierarchy from the server context menu orserver context toolbar.
2. The Create Protect Application window appears displaying the Primary and Backup Servers in yourcluster. If not already selected, choose the appropriate systems to configure. Click Next.
3. A dialog appears with a list of all recognized recovery kits installed within the cluster. Select Generic
Application and click Next.
4. The Configuration Wizard will prompt you to enter the following information. Note: When the Backbutton is active in any of the dialog boxes, you can go back to the previous dialog box. This isespecially helpful should you encounter an error that might require you to correct previously enteredinformation. If you click Cancel at any time during the sequence of creating your hierarchy, SteelEye
Protection Suite will cancel the entire creation process.

Field

Tips

RestoreScriptEnter the path and filename for the Restore Script for the application. This is thecommand that starts the application. A template restore script is provided in thetemplates directory. The restore script must not impact applications that are alreadystarted.

RemoveScriptEnter the path and filename for the Remove Script for the application. This is thecommand that stops the application. A template remove script is provided in thetemplates directory.

Quick
Check
Script[optional]

Enter the path to the Quick Check Script for the application. This is the command thatmonitors the application. A template quickchk script is provided in the templates
directory.

Deep
Check
Script[optional]

Enter the path to the Deep Check Script for the Application. This command monitors
the protected application in more detail than the Quick Check Script. A template
deepchk script is provided in the templates directory.

Local
Recovery
Script[optional]

Enter the path to the Local Recovery Script for the application. This is the commandthat attempts to restore a failed application on the local server. A template recover script
is provided in the templates directory.

Application
Enter any Application Information next. This is optional information about theInformation
application that may be needed by the restore, remove, recover, and quickCheck scripts.
[optional]
Resource
Tag Name

This field provides a default tag name App.x (where x is a number assigned by SteelEye
Protection Suite, starting with 0) which you can change if desired.

SteelEye Protection Suite for Windows Technical Documentation
Page 35

Creating a LAN Manager Resource Hierarchy

5. After all of the data is entered, the Create Instance button will appear. When you click Create
Instance, SteelEye Protection Suite will create and validate your resource hierarchy.
6. After receiving the message that the resource hierarchy has been created successfully, click Next tocontinue. If SteelEye Protection Suite has detected a problem, an ERROR will appear in theinformation box, the partially created resource hierarchy will be removed, and the Next button will bedisabled. In that case, click Cancel to exit the Wizard.

Creating a LAN Manager Resource Hierarchy
The LAN Manager Recovery Kit provides a way to create a computer alias name with associated file shares.
The computer alias name acts as a"switchable" computer name, and its associated file shares become
available on the system that has the SteelEye Protection Suite LAN Manager hierarchy in service. In
addition, an IP address can be associated with the computer alias name as part of the hierarchy.
1. Select the server, and then select Create Resource Hierarchy from the Server Context Menu orServer Context Toolbar.
2. The Create Protect Application window appears displaying the Primary and Backup Servers in yourcluster. If not already selected, choose the appropriate systems to configure. Click Next.
3. A dialog appears with a list of all recognized recovery kits installed within the cluster. Select LAN
Manager and click Next.
4. The Configuration Wizard will prompt you to enter the following information. When the Back buttonis active in any of the dialog boxes, you can go back to the previous dialog box. This is especiallyhelpful should you encounter an error that might require you to correct previously entered information. If
you click Cancel at any time during the sequence of creating your hierarchy, SteelEye Protection Suite
will cancel the entire creation process.

Field

Tips

ComputerEnter a name to be used for the computer alias, or you can accept the default nameAlias
offered by SteelEye Protection Suite.
Name
LAN
Select or enter a unique tag for the LAN Manager resource instance you are creating.
ManagerThis field provides a default tag name (the same as the computer alias name entered in
Resource
the previous step) which you can change if desired.
Tag
5. After all of the data is entered, the Next button will appear. When you click Next, SteelEye Protection
Suite will create and validate your resource hierarchy.
6. After receiving the message that the resource hierarchy has been created successfully, click Next tocontinue. If SteelEye Protection Suite has detected a problem, an ERROR will appear in theinformation box, the partially created resource hierarchy will be removed, and the Next button will bedisabled. In that case, click Cancel to exit the Wizard.

SteelEye Protection Suite for Windows Technical Documentation
Page 36Creating a Volume Resource Hierarchy

Creating a Volume Resource Hierarchy
When you want to protect resources on shared SCSI disks, you partition the shared disk into logical volumes
using the Windows Disk Management tool. SteelEye Protection Suite can protect shared volumes by defining
a volume resource instance. Each instance is assigned a drive letter (for example, G:).
SteelEye Protection Suite brings the volume resource instance into service on the primary server andprovides software locks so that a backup server cannot access the volume while it is active on the primaryserver. In case of a failure of the primary server, SteelEye Protection Suite automatically brings the volume
resource into service on the backup server and locks the primary server from accessing the volume resource
when it is repaired.
SteelEye Protection Suite also automatically changes the primary and designations so that the failed server is
now locked from access to the volume resource. In this way, the resource is protected from inappropriate
access while you repair the failed server.
This dynamic redefinition of primary and backup servers is SteelEye Protection Suite's intelligent switchback
feature that allows you to select the appropriate time to bring the resource back into service on the repaired
system.
To create a volume resource, follow the steps below. Since SteelEye Protection Suite maintains the volume
locks, do not stop SteelEye Protection Suite after creating the resource, as this would disable the locks.
Note: Before creating and extending a mirrored volume resource, be sure to exit from any DataKeeper GUI
processes that are connected to any of the SteelEye Protection Suite cluster systems.
1. Select the server, and then select Create Resource Hierarchy from the server context menu orserver context toolbar.
2. The Create Protected Application window appears displaying the Primary and Backup Servers inyour cluster. If not already selected, choose the appropriate systems to configure.
3. A dialog appears with a list of all recognized recovery kits installed within the cluster. When the Backbutton is active in any of the dialog boxes, you can go back to the previous dialog box. This isespecially helpful should you encounter an error that might require you to correct previously enteredinformation. If you click Cancel at any time during the sequence of creating your hierarchy, SteelEye
Protection Suite will cancel the entire creation process.

Field
VolumeTips
Select the volume to be protected. If "none found" is displayed, verify that the volume is under
SteelEye Protection Suite protection.

The Volume tag is a resource identifier. SteelEye Protection Suite provides a default volume tag
Volumename in the form: Volume.X, where X is the drive letter. You can change the tag name, but it mustTag
be unique.

SteelEye Protection Suite for Windows Technical Documentation
Page 37

After the Volume Resource is Created

4. After the data is entered, the Next button will appear. When you click Next, SteelEye Protection Suite
will create and validate your resource hierarchy.
5. After receiving the message that the resource hierarchy has been created successfully, click Next tocontinue. The Extend Volume Resource window displays. Refer to the help topic, Extending a
Volume Resource Hierarchy for additional information while completing this procedure.
6. If SteelEye Protection Suite has detected a problem, an ERROR will appear in the information box, thepartially created resource hierarchy will be removed and the Next button will be disabled. In that case,click Cancel to exit the Wizard.

After the Volume Resource is Created
After a SteelEye Protection Suite volume is created or deleted, the following command is executed for the
SteelEye Protection Suite protected volume:
chkntfs /x <vol_1> <vol_2> ... <vol_n>
This Windows command excludes the volumes listed from being checked by chkdsk at system startup. Thisis required for SteelEye Protection Suite protected volumes so that they will not be accessed - particularly on
backup systems - before LifeKeeper has a chance to start. If no SteelEye Protection Suite volumes remain,
chkntfs /d is executed to restore the Windows default settings.
Caution: The chkntfs /x command does not remember previous volumes it was applied to, so if a user
executes this command, it could disable the SteelEye Protection Suite settings, (and likewise, SteelEye
Protection Suite could subsequently override the user’s settings). If you wish to exclude a non-SteelEye
Protection Suite volume from checking at startup, you should also include all the SteelEye Protection Suitevolumes in the chkntfs /x command.

Creating an IP Address Resource Hierarchy
SteelEye Protection Suite provides the ability to monitor local switchable IP addresses and moves them toanother network adapter in the same system when a failure is detected. This can avoid an entire resource
hierarchy failing over to a backup server.
IP Local Recovery imposes requirements and limitations on the system configuration.

Requirements for IP Local Recovery
IP local recovery allows you to specify a single backup network interface for each SteelEye Protection Suiteprotected IP address on a server. In order for the backup interface to work properly, it must be attached to thesame physical network as the primary interface. The system administrator is expected to ensure that a validinterface is being chosen. Note that it is reasonable and valid to specify a backup interface on one server but
not on another within the cluster (i.e., the chosen backup interface on one server has no impact on the choiceof a backup on any other server).
The backup adapter, also known as the Local Recovery Adapter where the switchable address will become
active after a failure of the primary adapter,must be configured in the following way:

SteelEye Protection Suite for Windows Technical Documentation
Page 38

Requirements for IP Local RecoverylBoth adapters must be connected to the same physical subnet.

l

For routing purposes, all addresses on the Local Recovery Adapter must be on a different logicalsubnet than any permanent addresses on the Primary adapter. They must also be on a different logicalsubnet than any SteelEye Protection Suite-protected switchable addresses that are configured on thePrimary adapter.

l

The IP Local Recovery feature requires that a network gateway exist on the network. Specifically, thedefault gateway field in the TCP/IP configuration for the system must contain the address of a network
gateway. In addition, the local recovery adapter must also be configured with the same network
gateway.

l

Cabling and network routing must be configured to permit a ping command issued from either logicalsubnet to reach the protected IP address and its associated subnet when it is placed on either the
primary network card or the local recovery network card. This can be verified by manually issuing aping command from other systems on each logical subnet. A failed ping command indicates a network
routing problem.

l

IP Local Recovery can only be enabled at the time the IP resource is created. Local Recovery can not
be added to an IP resource by modifying its resource attributes after the resource has been created.

l

IP Local Recovery may be disabled for an IP resource by using the "ins_setlocalrecovery" commandline utility. This utility is located in the LifeKeeper \bin directory (C:\LK\bin by default). From acommand prompt, type "ins_setlocalrecovery" for the usage and switch options.

Before you create and use IP Address resources in SteelEye Protection Suite hierarchies, your network
should be configured and tested as described in the Verifying Network Configuration topic.
Also verify that the switchable IP address you plan to use is unique using the ping command. The switchable
IP address does not need to be created as a prerequisite; it is created when you create the IP address
hierarchy.
To create an IP address resource hierarchy from the primary server, you should complete the following steps:
1. Select the server, and then select Create Resource Hierarchy from the server context menu orserver context toolbar.
2. A dialog entitled Application to Protect will appear with a list of all recognized recovery kits installed
within the cluster. Select IP Address and click Next.
3. The Wizard will prompt you to enter the following information. When the Back button is active in anyof the dialog boxes, you can go back to the previous dialog box. This is especially helpful should you
encounter an error that might require you to correct previously entered information. If you click Cancel
at any time during the sequence of creating your hierarchy, SteelEye Protection Suite will cancel theentire creation process.

SteelEye Protection Suite for Windows Technical Documentation
Page 39

IP Local Recovery Scenario

Field

Tips

This is the switchable IP address or hostname that SteelEye Protection Suite will use
for this resource. This is used by client applications to login to the parent application
over a specific network interface. If you use a hostname, it must exist in the local%windir%\system32\etc\drivers\hosts file or be accessible via a Domain Name
IP Address
Service (DNS). Alias names and domain names are acceptable as long as they meetthe criteria listed above. No defaults are provided for this information field. Note: If you
choose to use a hostname, be advised that when you extend this resource, the actual
IP address will appear in one of the dialog boxes as the TCP/IP resource designation.

SubnetMask

The IP subnet mask which your TCP/IP resource will use on the target server. Anystandard netmask for the class of the specific TCP/IP resource address is valid. Note:
The subnet mask you choose, combined with the IP address, determines the subnet
that will be used by the TCP/IP resource and should be consistent with the network
configuration.

IP
Resource
Tag

Select or enter a unique IP Resource Tag name for the IP resource instance you arecreating. This field is populated automatically with a default tag name that matches theresource name or IP address. You can change this tag if you want to.

This is the physical Ethernet card that the IP address is interfacing with. Valid choices
will depend on the existing network configuration and values chosen for the TCP/IP
Network
resource address and netmask. The default value is the interface within the set of valid
Connection
choices which most closely matches the address and netmask values you haveselected in previous dialogs.
Local
Recovery If you answered "Yes" to Local Recovery, you must select a network connection to
Network
use as the backup interface. Specify the backup NIC if one exists; otherwise, specify
Connection the primary NIC.

4. After all of the data is entered, click Next and SteelEye Protection Suite will create and validate yourresource hierarchy.
5. After receiving the message that the resource hierarchy has been created successfully, click Next tocontinue. If SteelEye Protection Suite has detected a problem, an ERROR will appear in theinformation box, the partially created resource hierarchy will be removed, and the Next button will bedisabled. In that case, click Cancel to exit the Wizard.
Note: If using teaming software or if network cards are changed after creating a switchable IP resource, theswitchable IP resource should be deleted and recreated as the associated index number for the card canchange.

IP Local Recovery Scenario
When IP Local Recovery is enabled and the IP resource fails its deepcheck (a periodic extensive check of the
IP resource), then SteelEye Protection Suite will do the following:

SteelEye Protection Suite for Windows Technical Documentation
Page 40

Editing Resource PrioritieslFirst, SteelEye Protection Suite will attempt to bring the IP address back in service on the current
network interface.

l

If that fails, SteelEye Protection Suite will check the resource instance to determine if there is a
backup interface available. If so, it will then attempt to move the IP address to the backup interface.

l

If all local recovery attempts fail, SteelEye Protection Suite will perform a failover of the IP address andall dependent resources to a backup server.

Even if you do not have a backup adapter, you can enable Local Recovery so that SteelEye Protection Suite
will retry the primary network interface before initiating failover to a backup server.

Editing Resource Priorities
You can edit or reorder the priorities of servers on which a resource hierarchy has been defined. First, bring up
the Resource Properties dialog just as you would for viewing resource properties. The Resource
Properties dialog displays the priority for a particular resource on a server in the Equivalencies tab as shown
below.

SteelEye Protection Suite for Windows Technical Documentation
Page 41

Using the Up and Down Buttons

There are two ways to modify the priorities:lReorder the priorities by moving an equivalency with the Up/Down buttons, orlEdit the priority values directly.

Using the Up and Down Buttons
1. Select an equivalency by clicking on a row in the Equivalencies table. The Up and/or Down buttons
will become enabled depending on which equivalency you have selected. The Up button is enabled
unless you have selected the highest priority server. The Down button is enabled unless you haveselected the lowest priority server.
2. Click Up or Down to move the equivalency in the priority list.
The numerical priorities column will not change, but the equivalency will move up or down in the list.

SteelEye Protection Suite for Windows Technical Documentation
Page 42Editing the Priority Values

Editing the Priority Values
1. Select a priority by clicking on a priority value in the Priority column of the Equivalencies table. A box
appears around the priority value and the value is highlighted.
2. Enter the desired priority and press Enter.
Note: Valid server priorities are 1 to 999
After you have edited the priority, the Equivalencies table will be re-sorted.

Applying Your Changes
Once you have the desired priority order in the Equivalencies table, click Apply (or OK) to commit yourchanges. The Apply button applies any changes that have been made. The OK button applies any changes
that have been made and then closes the window. The Cancel button closes the window without saving any
changes made since Apply was last clicked.

Incomplete Resource Priority Modification
A hierarchy in SteelEye Protection Suite is defined as all resources associated by parent/childrelationships. For resources that have multiple parents, it is not always easy to discern from the GUI all of theroot resources for a hierarchy. In order to maintain consistency in a hierarchy, SteelEye Protection Suite
requires that priority changes be made to all resources in a hierarchy for each server. The GUI enforces thisrequirement by displaying all root resources for the hierarchy selected after the OK or Apply button ispressed. You have the opportunity at this point to accept all of these roots or cancel the operation. If you
accept the list of roots, the new priority values will be applied to all resources in the hierarchy.
You should ensure that no other changes are being made to the hierarchy while the Resource Properties
dialog for that hierarchy is displayed. Before you have edited a priority in the Resource Properties dialog,
any changes being made to SteelEye Protection Suite are dynamically updated in the dialog. Once you havebegun making changes, however, the values seen in the dialog are frozen even if underlying changes arebeing made in SteelEye Protection Suite. Only after selecting the Apply or OK button will you be informedthat changes were made that will prevent the priority change operation from succeeding as requested.
In order to minimize the likelihood of unrecoverable errors during a priority change operation involving multiple
priority changes, the program will execute a multiple priority change operation as a series of individualchanges on one server at a time. Additionally, it will assign temporary values to priorities if necessary to
prevent temporary priority conflicts during the operation. These temporary values are above the allowed
maximum value of 999 and may be temporarily displayed in the GUI during the priority change. Once theoperation is completed, these temporary priority values will all be replaced with the requested ones. If an error
occurs and priority values cannot be rolled back, it is possible that some of these temporary priority values willremain. If this happens, follow the suggested procedure outlined below to repair the hierarchy.

SteelEye Protection Suite for Windows Technical Documentation
Page 43

Restoring Your Hierarchy to a Consistent State

Restoring Your Hierarchy to a Consistent State
If an error occurs during a priority change operation that prevents the operation from completing, the priorities
may be left in an inconsistent state. Errors can occur for a variety of reasons, including system andcommunications path failure. If an error occurs after the operation has begun, and before it finishes, and theprogram was not able to roll back to the previous priorities, you will see a message displayed that tells you
there was an error during the operation and the previous priorities could not be restored. If this should happen,
you should take the following actions to attempt to restore your hierarchy to a consistent state:
1. If possible, determine the source of the problem. Check for system or communications path failure.
Verify that other simultaneous operations were not occurring during the same time that the priority
administration program was executing.
2. If possible, correct the source of the problem before proceeding. For example, a failed system orcommunications path must be restored before the hierarchy can be repaired.
3. Re-try the operation from the Resource Properties dialog.
4. If making the change is not possible from the Resource Properties dialog, it may be easier to attempt
to repair the hierarchy using the command line hry_setpri. This script allows priorities to bechanged on one server at a time and does not work through the GUI.
5. After attempting the repair, verify that the SteelEye Protection Suite databases are consistent on allservers by executing the eqv_list command for all servers where the hierarchy exists and observing
the priority values returned for all resources in the hierarchy.
6. As a last resort, if the hierarchy cannot be repaired, you may have to delete and re-create the hierarchy.

Editing Resource Properties
1. To edit the properties of a resource, bring up the Resource Properties dialog just as you would forviewing resource properties.
2. If you are logged into that server with the appropriate permissions, the following items will be editable.
l

SwitchbacklResource Configuration (only for resources with specialized configuration settings)lResource Properties

3. Once you have made changes, the Apply button will be enabled. Clicking this button will apply yourchanges.
4. When you are finished, click OK to save any changes and close the window or Cancel to close thewindow without applying changes.

Extending Resource Hierarchies
The SteelEye Protection Suite Extend Resource Hierarchy option copies an existing hierarchy from one

SteelEye Protection Suite for Windows Technical Documentation
Page 44Extending a DNS Resource Hierarchy

server and creates a similar hierarchy on another SteelEye Protection Suite server. Once a hierarchy isextended to other servers, cascading failover is available for that resource. The server where the existinghierarchy currently resides is referred to as the template server. The server where the new extended hierarchy
will be placed is referred to as the target server.
The target server must be capable of supporting the extended hierarchy and it must be able to communicate
with equivalent hierarchies on other remote servers (via active SteelEye Protection Suite communication
paths). This means that all recovery kits associated with resources in the existing hierarchy must already beinstalled on the target server as well as every other server where the hierarchy currently resides.
Note: When you create a new resource hierarchy, you will be prompted to extend that hierarchy immediately
afterwards.
1. To extend an existing resource hierarchy, select that server hierarchy you want to extend and thenselect Extend Resource Hierarchy from the resource context menu or resource context toolbar.
2. Select the Backup Server and click Next.
3. A dialog will then display the results of SteelEye Protection Suite's pre-extend checks. If these tests
succeed, SteelEye Protection Suite will display a message stating that the pre-extend scripts weresuccessful. Click Next to enter any remaining data needed for the specific type of resource hierarchy
that you are extending.
Note: ALL roots in a multi-root hierarchy must be extended together, that is, they may not be extended as
single root hierarchies.

Extending a DNS Resource Hierarchy
This operation can be started automatically after you have finished creating a DNS resource hierarchy, or froman existing DNS resource hierarchy, as described in the section on extending resource hierarchies. The
following additional data is required to extend a DNS resource hierarchy.

Field

Tips

IP AddressEnter the IP address of the A record associated with the protected primary server or alias
name. The record will be updated with this IP address when the DNS resource is brought inservice on this server.

DNS Server
Name (Fully
Qualified)Enter fully qualified name of a DNS server, in format <DNS
ServerName>.<mydomain>.com, where the Resource Records can be modified. The DNS
server should be accessible from the backup server, preferably in the same site.

Extending a File Share Resource Hierarchy
This operation can be started automatically after you have finished creating a file share resource hierarchy, orfrom an existing file share resource hierarchy, as described in the section on extending resource hierarchies.
No additional data is required to extend a file share resource hierarchy.

SteelEye Protection Suite for Windows Technical Documentation
Page 45

Extending a Generic Application Resource Hierarchy

Extending a Generic Application Resource Hierarchy
This operation can be started automatically after you have finished creating a generic application resource
hierarchy, or from an existing generic application resource hierarchy, as described in the section on extending
resource hierarchies. No additional data is required to extend a generic application resource hierarchy.

Extending a LAN Manager Resource Hierarchy
This operation can be started automatically after you have finished creating a LAN manager resource
hierarchy, or from an existing LAN manager resource hierarchy, as described in the section on extending
resource hierarchies. No additional data is required to extend a LAN manager resource hierarchy.

Extending a Volume Resource Hierarchy
This operation can be started automatically after you have finished creating a volume resource hierarchy, orfrom an existing volume resource hierarchy, as described in the section on extending resource hierarchies.
The following additional data is required to extend a volume resource hierarchy.

Field

Tips

Volume Type

Select Shared Disk if using shared storage, Create Mirror if using SteelEye
DataKeeper and the mirror does not exist, or Existing Mirror if using
SteelEye DataKeeper and the mirror has already been created.

Network end points(Target/Source)

If Volume Type Create Mirror or Existing Mirror, select the network end
points for the mirror. End points must be IP addresses.
If Volume Type Create Mirror, then select the mode of the mirror.
Asynchronous Mirror: Source writes are queued for transmission to thetarget, and return immediately. Less reliable than synchronous, but source
writes are quicker.

Mode

Synchronous Mirror: All writes to the source volume will be committed tothe target volume immediately. Higher reliability, lower performance.
When extending the volume resource to a third system in the cluster, you must specify the volume type foreach of the equivalent systems in the cluster.
Volume Type (Shared or
SteelEye DataKeeper))

Select Shared Disk or the network end points for the mirror between theequivalent systems.

Note: Mirrors created from the LifeKeeper GUI will be deleted when the volume resource hierarchy is deleted.
To prevent the mirror deletion, set the LifeKeeper Delete Mirror Flag to False.

Extending an IP Address Resource Hierarchy
This operation can be started automatically after you have finished creating an IP address resource hierarchy

SteelEye Protection Suite for Windows Technical Documentation
Page 46

Unextending a Hierarchyor from an existing IP address resource hierarchy as described in the section on extending resource
hierarchies. The following additional data is required to extend an IP address resource hierarchy.

Field
Subnet
Mask

Tips
Enter the subnet mask to use for the IP resource on the target server. SteelEye Protection
Suite will, by default, offer the subnet mask used on the template server.

Network
Select the network connection to use on the target server.
Connection
This feature applies to three-node SteelEye Protection Suite clusters where two nodes are on
a LAN (same subnet) and the third node is on a WAN (different subnet). The restore mode of
the IP resource would be enabled on the LAN nodes and disabled on the WAN node.

TargetRestoreMode

TargetLocal
RecoverySelect the appropriate Restore Mode for this IP resource on the target system. In somesituations a protected IP address should not be used on a remote target system. For example,
the remote target system may be connected to a different subnet than other systems in thecluster. In this situation the IP resource may be extended using the "Disable" Restore Mode.
When using the "Disable" Restore Mode option, SteelEye Protection Suite will not configure
the IP address on the target system when the resource is placed in-service there andmonitoring for the IP resource will be disabled. In these situations, network redirection may
be implemented some other way or by using a SteelEye Protection Suite DNS resource. You
may use the IP resource properties page on the target system to change your selection at alater time. See Managing IP Resources.
Click Yes if you wish to enable IP Local Recovery on the target server; otherwise choose No.

TargetLocal
If you answered Yes to Local Recovery, you must select a network connection to use as theRecoverybackup interface. Specify the backup NIC if one exists; otherwise, specify the primary NIC.
Network
Connection
Note: A disabled IP resource can not be extended to another system. As part of the extend operation, a pingcommand is performed to verify that the IP resource is reachable from the remote system. In the case of adisabled IP resource, the IP resource will be In-service, but will not respond to the ping command.

Unextending a Hierarchy
The Unextend Resource Hierarchy option removes a complete hierarchy, including all of its resources, froma single server. This is different than the Delete Resource Hierarchy selection which removes a hierarchy
from all servers.
When using Unextend Resource Hierarchy, the server from which the existing hierarchy is to be removed isreferred to as the target server.
The Unextend Resource Hierarchy selection can be used from any SteelEye Protection Suite server thathas active SteelEye Protection Suite communication paths to the target server.

SteelEye Protection Suite for Windows Technical Documentation
Page 47

Adding a Resource Dependency

1. Select a server-specific resource instance from the hierarchy that you want to unextend, and thenselect Unextend Resource Hierarchy from the resource context menu or resource context toolbar.
2. The dialog will display a message verifying the server and resource hierarchy that you have specified
to be unextended. Click Unextend to perform the action.
3. If the output panel is enabled, the dialog closes, and the results of the commands to unextend theresource hierarchy are shown in the output panel. If not, the dialog remains up to show these results,
and you click Done to finish when all results have been displayed.

Adding a Resource Dependency
While most Recovery Kits create their dependencies during the original resource hierarchy creation task,
under certain circumstances, you may want to create new or additional resource dependencies or delete
existing ones. An example might be that you wish to change an existing IP dependency to another IP address.
Instead of deleting the entire resource hierarchy and creating a new one, you can delete the existing IP
dependency and create a new dependency with a different IP address.
1. Select a server-specific resource instance as the parent to which you want to add a child dependency,
and then select Add Dependency... from the resource context menu or resource context toolbar.
2. Select a Parent Resource IP Address from the drop down box. Click Next.
3. Select a Child Resource Tag from the drop down box of existing and valid resources on the server.
The dialog will display all the resources available on the server with the following exceptions:l

The parent resource, its ancestors and its children.

l

A resource that has not been extended to the same servers as the parent resource.

l

A resource that does not have the same relative priority as the parent resource.

l

Any resource that is not in-service on the same server as the parent, if the parent resource is inservice.

Click Next to proceed to the next dialog.
4. The dialog will then confirm that you have selected the appropriate parent and child resource tags foryour dependency creation. Click Add Dependency to create the dependency on all servers in thecluster to which the parent has been extended.
5. If the output panel is enabled, the dialog closes and the results of the commands to create thedependency are shown in the output panel. If not, the dialog remains up to show these results, and you
click Done to finish when all results have been displayed.

Removing a Resource Dependency
1. Select a server-specific resource instance as the parent from which you want to remove a childdependency, and then select Remove Dependency from the resource context menu or resource
context toolbar.

SteelEye Protection Suite for Windows Technical Documentation
Page 48

Deleting a Hierarchy from All Servers

2. Select the Child Resource from the drop down box. This should be the name of the child in thedependency that you want to delete. Click Next to proceed to the next dialog box.
3. The dialog then confirms that you have selected the appropriate parent and child resource tags for yourdependency deletion. Click Remove Dependency to delete the dependency on all servers in thecluster.
4. If the output panel is enabled, the dialog closes, and the results of the commands to delete thedependency are shown in the output panel. If not, the dialog remains up to show these results, and you
click Done to finish when all results have been displayed.

Deleting a Hierarchy from All Servers
1. Select a server-specific resource instance in the hierarchy that you want to delete, and then selectDelete Resource Hierarchy from the resource context menu or resource context toolbar.
2. The dialog will display a message verifying the hierarchy you have specified for deletion. Click Delete
to perform the action. Deletion will begin on the sever that you initially selected.
3. If the output panel is enabled, the dialog closes, and the results of the commands to delete the hierarchy are shown in the output panel. If not, the dialog remains up to show these results, and you click
Done to finish when all results have been displayed.

Man Pages
LCD - Miscellaneous LCD Programs

Synopsislcdremexec [-e] -d destname -- cmd [arg1 arg2 ... argn]
lcdsync [-d destname]lcdrecover -g {remote|restore|delete} -- [arg1 arg2 ... argn] | -G {remote|restore|delete} -- [arg1 arg2 ... argn] | -p
primarytest /| [-o resource]
lcdrcp file1 file2 file3 ... {dest:ofile | dest:odir}lkstart [-w waitperiod]
lkstop [-f or -r|-n]]SteelEye Protection Suite for Windows Technical Documentation
Page 49

Description

Description
These programs have various uses by application developers. They are all found in the directory%LKROOT%\bin.

Exit Codes
The following exit codes could be returned by these commands:
0 The operation has succeeded.
1 A system call or library call has internally returned failure.
2 A user-specified syntax error occurred.
3 LifeKeeper internal error.
4 A request to perform an operation on an object that already exists.
5 An argument specified is illegal.
6 Index out-of-range.
7 A request has been made on an object that does not exist.
8

A request was made to delete a resource instance on which another non-deleted resource instancedepends.

9 An attempt to communicate with another system failed.

lcdrcplcdrcp file1 file2 file3 ... {dest:ofile | dest:odir}
lcdrcp is a general purpose program used to transfer the ASCII files file1 file2 file3 ... to another system using
the LifeKeeper communications path. Binary files cannot be copied using lcdrcp.
LifeKeeper transfers the files to dest in the directory odir. If only one file is sent, the alternate form including
the destination file name at location ofile on system dest is provided. Take extra caution while using Windows
drive names (like D:), as destination arguments as they could be misinterpreted as destination names if a
destination name is missing. However, if a destination system name is specified, drive names are interpreted
properly.

lcdrecoverlcdrecover -g {remove|restore|delete} -- [arg1 arg2 ... argn] | -G
{remote|restore|delete} -- [arg1 arg2 ... argn] | -p primarytest | [-oresource]

SteelEye Protection Suite for Windows Technical Documentation
Page 50

lcdrecover

The -g option takes one of three arguments, remove, restore, or delete. This option will run the preglobal
scripts for the specified argument. The preglobal scripts are registered by applications to run before certain
events. For example, with the restore argument, this option runs the prerestore script registered by
LifeKeeper, then any prerestore scripts registered by all of the applications. Normally, perform_action [seeLRACI-perform_action] automatically performs the prerestore scripts, except when the -G option is specified
to perform_action.
The -G option of perform_action allows multiple perform_action commands to be run, with the preglobal
scripts running only once before the first perform_action execution using lcdrecover -g restore. An
application may register a preglobal script by installing the script at the path:%LKROOT%\ subsys\<appname>\actions\prerestore.ksh
arg1, arg2, ... argn are arguments that will be passed to the preglobal scripts when they are executed.
Similar scripts (preremove) exist for the remove argument. They can be run before a perform_action -G -aremove is run. They are run when lcdrecover -g remove is executed.
The predelete scripts are similar, but they are run before the ins_remove -G ... [see LCDI-instance] programis run, unless -G for ins_remove is left out.
The -G option for lcdrecover is analogous to -g, except that it specifies that the postglobal scripts should berun. The -G option should not be used without running an earlier lcdrecover -g arg, and it should be run after
all of the perform_action or ins_remove programs are run. If you are executing the -G option within agetlocks protected region (after getlocks and before rlslocks), set arg1 to -m to avoid executing a second
instance of getlocks, which would cause the operation to hang.
The following example runs multiple perform_action commands where the preglobal and postglobal scripts
run only once:
lcdrecover -g restore# run "preglobal" restore scripts
perform_action -G -a restore -t tagname# neither scripts are run
perform_action -G -a restore -t tagname2# neither scripts are runlcdrecover -G restore -- -m# run "postglobal" restore scripts# use -m arg when in getlocks protected region of code
This example runs multiple prerestore and postrestore scripts:
perform_action -a restore -t tagname# all scripts once
perform_action -a restore -t tagname2# all scripts again

SteelEye Protection Suite for Windows Technical Documentation
Page 51

lcdremexec

The -p option for lcdrecover is used to determine if a particular resource is on a resource hierarchy that is on
the primary system or the secondary system. Specify the resource tag name with primary test, and it will printout to standard output the string primary if the resource is on the primary hierarchy, or secondary if it is not.
The -o option can be used to retrieve the remote system associated with the resource tag specified.

lcdremexec
lcdremexec [-e] -d destname -- cmd [arg1 arg2 arg3 ... argn]
This program sends a remote request over the LifeKeeper communication paths to the system destname, to
execute the command cmd remotely with arguments arg1 arg2 arg3 ... of the and returns the standard output
and standard error of the remote command to standard output of the lcdremexec command. The exit code of
the remote command is returned by lcdremexec.
Note: If destname is the current system, no messages are sent; lcdremexec will execute it locally.
The -e option will split standard output and standard error of the remote command and first print standard
output of the remote command to standard output of lcdremexec, then print standard error of the remotecommand to standard error of the lcdremexec command. This option has no effect for local commands,
which have their standard output and standard error unchanged.
cmd can be either a Korn shell script or a Win32 executable. It will be executed with %LKROOT% on
destname as the current working directory, thus being able to accept path names relative to %LKROOT%.
Before executing, the directory %LKROOT%\BIN is always added to the head of the PATH variable on
destname. If destname is DEAD or goes DEAD in the middle of the execution, lcdremexec returns a nonzero exit code.

lcdsynclcdsync [-d destname]
This program checks to see if the LifeKeeper resource hierarchy configuration and communication path status
data stored in shared memory has been modified. If it is different, the data is "synchronously" written to disk.
Therefore, when this program returns, the data is guaranteed to be on disk properly. If destname is not
specified, the current system is assumed.
Note: The commands used to modify resource hierarchy configurations or communication paths (such as
ins_create, dep_create, ins_setit, eqv_remove,...) only modify the shared memory segment and are notreflected in the permanent file storage of LifeKeeper, until the lcdsync program is run.

lkstartlkstart [-w waitperiod]
This program starts up LifeKeeper on the current system if it is currently not running. lkstart modifies entries
in the %LKROOT%\etc\LKinit.config file pertaining to the LifeKeeper daemons so that they will be
respawned if they die.

SteelEye Protection Suite for Windows Technical Documentation
Page 52

lkstop

The -w option, with waitperiod in seconds, can be used to change the timeout interval. Use the -w argument
to specify a wait period before the startup.
The LifeKeeper service can be started using the Services mmc under Administrative Tools, or from acommand prompt using either "sc start LifeKeeper" or "net start LifeKeeper"'
Note: This program must be run from the console.

lkstoplkstop [-n] [-f] [-r]This script shuts down LifeKeeper on the system, if it is currently running. LifeKeeper will automaticallyrestart at system boot.
The table below describes the actions taken by LifeKeeper when each lkstop option is entered:CommandLine

ActionlkstopResources in service are removed from service and are NOT switched over to a backup
server.

lkstop -nSame as lkstop with no options specified.

lkstop -f

Resources in service do not get removed from service.

lkstop -r

Same as -f.

The LifeKeeper services can also be stopped using the using the Services tool under Administrative Tasks in
the Windows Control Panel.

LCDI Applications

Synopsisapp_create [-d destsys] -a appname
app_remove [-d destsys] -a appname
app_list [-d destsys]

Description
A LifeKeeper application is a group of related resource types. When an application is removed, all resource
types installed under it are also removed.

SteelEye Protection Suite for Windows Technical Documentation
Page 53

Exit Codes

These programs provide an interface for generating new applications in the configuration database andremoving existing ones. All commands exit 0, if successful, and a nonzero code (see EXIT CODES section)
and an error message prints to standard error for failure.

Exit Codes
The following exit codes could be returned by these commands:
0 The operation has succeeded.
1 A system call or library call has internally returned failure.
2 A user-specified syntax error occurred.
3 LifeKeeper internal error.
4 A request to perform an operation on an object that already exists.
5 An argument specified is illegal.
6 Index out-of-range.
7 A request has been made on an object that does not exist.
8

A request was made to delete a resource instance on which another non-deleted resource instancedepends.

9 An attempt to communicate with another system failed.

app_create
app_create [-d destsys] -a appname
Creates a new application. The application is tied to system destsys, using the name called appname. If
destsys is not supplied, the application is created locally.

app_list
app_list [-d destsys]
This command prints to standard output a list of applications that have installed software to work with
LifeKeeper on the system destsys. If destsys is not specified, the current system is assumed.

app_remove
app_remove [-d destsys] -a appname
Removes the given application from the configuration database set of known applications. All resource types,
resource instances, and equivalencies relating to this application are also removed. Failure can occur
because the application is not known to the configuration database.

SteelEye Protection Suite for Windows Technical Documentation
Page 54LCDI Instances

LCDI Instances

Synopsis
ins_gettag [-d destsys] -i id
ins_create [-d destsys] -a appname -r restyp [-I{AUTORES_ISP|INIT_ISP| INIT_OSU}] [-v info] -t tag -i id [-QquickChkInt] [-DdeepChkInt] [-l localRecover{Y/N}] [ -s AUTOMATIC/INTELLIGENT]
ins_remove [-d destsys] [-R roottag] [-a appname] [-r restyp] [-ttag] [-i id] [-v] [-I] [-N] [-G]
ins_setin [-d destsys] -t tag [-v info]
ins_setit [-d destsys] -t tag -I {AUTORES_ISP|INIT_ISP|INIT_OSU}
ins_setst [-d destsys] -t tag -S {ISP|ISU|OSU} [-R reason] [-A]
ins_list [-d destsys] [-fC] [-R top] [-a appname] [-r typ] [-t tag] [-i id]
ins_setchkint [-d destsys] -t tag -c {q=quick|d=deep} -vinterval
ins_setlocalrecover [-d destsys] -t tag -l {Y=enable|N=disable}
ins_setas [-d destsys] -t tag -s {INTELLIGENT|AUTOMATIC}

Description
Resources are used by LifeKeeper to represent volumes, applications, or system objects known by thesystem. Resource types are classifications of resources; resource instances are actual instances of a
resource type. For example, resource types would include file system volumes, file shares, IP addresses,
LAN Manager names and various servers like SQLServer. Generic, user-definable types permit users to build
custom fault resilient setups. Multiple instances may exist for a resource type.
Resource instances may exist in a number of states. These states may take on the following values andmeanings:
ISP

Resource is in service, protected. ISP is the normal state of resources on the primary node.

Out of service, unimpaired. The resource is not available on this system because it was brought outof service by executing its remove script. The OSU state also is used for objects that have
OSU
dependencies on children in the OSF or OSU state or when the equivalent object on the backup
machine is in the ISP or ISU state. OSU is the normal state of resources on the secondary node.
OSF

Out of service due to a failure. The resource is not available on this system because a failure has
occurred trying to restore the object.

SteelEye Protection Suite for Windows Technical Documentation
Page 55

Exit Codes

Exit Codes
All commands exit 0 if successful. For a failure, all commands exit to a nonzero code and prints to standard
error. The following exit codes could be returned by these commands:
0 The operation has succeeded.
1 A system call or library call has internally returned failure.
2 A user-specified syntax error occurred.
3 LifeKeeper internal error.
4 A request to perform an operation on an object that already exists.
5 An argument specified is illegal.
6 Index out-of-range.
7 A request has been made on an object that does not exist.
8

A request was made to delete a resource instance on which another non-deleted resource instancedepends.

9 An attempt to communicate with another system failed.

ins_list
ins_list [-d destsys] [-fC] [-R top] [-a appname] [-r typ][-t tag] [-i id]
This command prints lines relating to a set of resource instances to standard output. Each line contains all of
the current information known about a particular resource instance. Examples of the lines are:
LKSYS1-filesys-volume-ISSUTILS-K:--ISP-restore action hassucceededAUTORES_ISP--0-0Each line contains fields separated by a delimiter character. The default delimiter character is ^A (\001). If the-fC option is specified, the delimiter is changed to the specified character. The above example shows a dash(-) as a delimiter. The fields in the example command above are as follows:
LKSYS1Name of the system the resource the instance resides on.

filesys

Application name of resource type.

volumeResource type name.

ISSUTILS

User-defined resource instance tag identifier.

K:

LifeKeeper internal identifier for resource instance.

--

If this field is not empty, as in the example, it provides additional instanceinformation (type dependent).

ISP

Current state of resource instance ISP, ISU, OSU, or OSF.

SteelEye Protection Suite for Windows Technical Documentation
Page 56

Initialization Strategy

restore action has
succeeded

Reason for last state change.

AUTORES_ISP

Available resource initialization options are: AUTORES_ISP, INIT_ISP, and
INIT_OSU.
If this field is not empty, as in the example, it indicates that the resource iscurrently being reserved for:--RESTORE: restoring the resource to service
REMOVE: removing the resource from service
RECOVER: performing local recovery on resource

0

Process ID of process that has reserved resource.

0

Reserved.

180

Quick check interval, in seconds.

300

Deep Check interval, in seconds.

0

Local recovery option. 0 = disabled; 1 = enable

The other arguments limit the number of resource instances included in the list. If none of the arguments areused, then all resources on destsys are listed. These are the limiting arguments:
destsys. If destsys is not specified, the current system is assumed; otherwise, data from the remote system
is printed.
top. If top is the space string " ", only the root resources will be printed. If top is specified (but not the space
string), the report lists the top resource and all children resources below it, recursively.
appname. If appname is specified, all resource instances associated with all resource types defined by thisapplication are printed. If appname is not specified, all resource instances for all applications defined on thesystem are printed.
typ. If typ is specified, all resource instances of type, typ, in application appname are printed.
tag or id. If tag or id is specified, the resource instance associated with that tag or id is printed.

Initialization Strategy
It is recommended that you accept the default Auto ISP Initialization Strategy. These are the actions taken
when LifeKeeper starts (initializes):
Autores ISP

Resource is automatically brought into service if it is not in service on the paired node.

Init ISP

Resource is always initialized into the ISP state.

Init OSU

Resource is always initialized into the OSU state.

SteelEye Protection Suite for Windows Technical Documentation
Page 57

Initial State

Initial State
The state is the current processing status for the resource. For example, the normal state for a resource on
the primary system is ISP - in service, protected. The normal state for a resource on the secondary system is
OSU - out of service, unimpaired.
It is recommended that you accept the default initial state. If you set the Initial State to OSU, you must
manually bring the resource into service.

ins_create
ins_create [-d destsys] -a appname -r restyp [-I {AUTORES_ISP|INIT_ISP|INIT_
OSU}][-v info] -t tag -i id [-Q quickChkInt][-D deepChkInt][-l localRecover{Y|N}] [-s AUTOMATIC|INTELLIGENT]
Defines a new resource instance on system destsys in the configuration database. The resource instance is
described by the arguments given. If destsys is not specified, the current system is assumed. The command
offers the following string tag options:l

The -a and -r options indicate the preexisting application and resource type associated with this new
instance.

l

Initialization type field specified by the -I option indicates how the resource instance should beinitialized if LifeKeeper restarts (for example, at boot time).

lOptional string info specified by the -v option is a field that can contain additional resource type specificinformation and does not necessarily have to be unique per resource type.

l

String tag specified by the -t option is a string that names the resource instance and is unique on asystem. It is a string that is meaningful externally to LifeKeeper.

lString id specified by the -i option is also unique per system, but may be meaningful only internally to
LifeKeeper.

l

Quick check interval provided with -Q option should be in seconds. The value should be zero if
quickchk.ksh script doesn’t exist for the resource. LifeKeeper waits this interval time between two
consecutive execution of quickchk.ksh script. Valid range of value: 0 - 604800.

l

Deep check interval provided with -D option should be in seconds. The value should be zero if
deepchk.ksh script doesn’t exist for the resource. LifeKeeper wait this interval time between two
consecutive execution of deepchk.ksh script. Valid range of value: 0 - 604800.

l

Local recover option indicates whether resource should be recovered byexecuting recover.ksh script.
This option should be "N” if recover.ksh script doesn’t exist for the resource.

ins_gettag
ins_gettag [-d destsys] -i id

SteelEye Protection Suite for Windows Technical Documentation
Page 58

ins_remove

Prints to standard output the tag name that corresponds to the internal identifier provided in id on the systemwith name destsys. If destsys is not specified, the current system is assumed.
Note: The tag name and id name for a resource are unique on a system, but may be reused to indicate
different resource instances on different systems.
The resource tag provides an understandable handle (human readable name) for a resource instance, forexample, user-partition, whereas the id is an internal descriptor. The resource name id is used by theapplication software associated with the resource to uniquely describe the resource.

ins_remove
ins_remove [-d destsys] [-R roottag] [-a appname] [-r restyp][-t tag] [-i id][-v] [-I] [-N] [-G]
Removes resource instance(s) on system destsys from the configuration database. Associateddependencies and equivalencies will also be removed. If destsys is not specified, the current system isassumed.
Note: All resources that depend upon any of the selected resources directly or indirectly will also be removed
before the selected resource is removed.
When a resource instance is removed, and if a delete action was defined for the resource type of the instancebeing removed, the delete action is run before the instance is removed.
The command has the following options:
The -R option is for removing entire sub-hierarchies and the resources that depend on them. The- roottag string defines a list of instance tag names (separated by the ^A character) for which theseR resources and the resources below on the hierarchy will be recursively removed, until a resource isencountered for which a resource not being removed depends.
-a If the -a option is specified, only resources from that application will be removed.
-r If the -r option is specified, all resources of the specified resource type will be removed.
-t
If the -t option or -i option is specified, the instance with the matching tag or id will be removed alongorwith the resources that depend on them.
-i-v

If the -v option (verbose) is specified, the function prints a message to standard output including the tag
names of all the removed resource instances.

The -I option initializes the resource hierarchy so that ins_remove can work properly. This option
should be used by the"highest-level" recursive call to ins_remove, but not necessarily in a lower-level-I
recursive call such as inside a delete script. The -I option should NOT be used by a recursive call to
ins_remove from inside a delete script.
The -N option tells ins_remove NOT to reinitialize the resource hierarchy. The assumption when using- this option is that a higher level call of ins_remove will perform the -I option. The -N option MUST be
N used inside a delete script, since a delete script is being called from a parent invocation of ins_remove
and the -N option prevents hierarchy cycles from occurring.

SteelEye Protection Suite for Windows Technical Documentation
Page 59ins_setas

The -G option indicates that the predelete and postdelete scripts [see LCD] should not be performed aspart of this call to ins_remove. This option is useful if you wish to perform multiple top-level calls to
ins_remove and have the predelete and postdelete run manually [using lcdrecover-g delete of LCD]
G
before and after (respectively) the calls to ins_remove. It would also be wise to use the -G option in thedelete scripts since the highest-level ins_remove should perform the predelete and postdelete scripts.

ins_setas
ins_setas [-d destsys] -t tag -s {INTELLIGENT|AUTOMATIC}
Sets the switchback type of a root resource on system destsys with tag name tag to the strategy specified in
the -s option. Use only on root resource to change the switchback type of the root resource and all its
dependent resources.

ins_setchkint
ins_setchkint [-d destsys] -t tag -c {q=quick|d=deep} -v intervalThis command modifies the quick check or deep check interval for the resource specified by the tag name "-t".
The interval must be entered in seconds.
Examples:To change the quick check interval for the file share resource FSList.0 to two minutes, run the following
command from $LKROOT\bin:ins_setchkint-t FSList.0 -c quick -v 120
To disable the deep check for the file share resource FSList.0, run the following commandfrom $LKROOT\bin:ins_setchkinst -t FSList.0 -c deep -v0

ins_setin
ins_setin [-d destsys] -t tag [-v info]
The string info specified by the -v option is a field that can contain additional resource type specific informationand does not necessarily have to be unique per resource type. For example, an instance of a resource of fileshare type will have the names of all shares managed by this instance in its info value.

ins_setit
ins_setit [-d destsys] -t tag -I {AUTORES_ISP | INIT_ISP | INIT_OSU}
Indicates to LifeKeeper how it should initialize the state of a resource when LifeKeeper itself initializes (forexample, at system boot time). If you do not set this option, LifeKeeper sets the initialization state to default
options.
These are the restore options you can specify:

SteelEye Protection Suite for Windows Technical Documentation
Page 60

ins_setlocalrecover

AUTORES_ISP. If resource initialization is set to AUTORES_ISP, the resource is first set to the OSU state,then the restore action is performed and, if successful, the resource is put into the ISP state. If restore fails,
the resource is placed into the OSF state.
INIT_ISP. If INIT_ISP is set, LifeKeeper assumes resource initialization by other means and places theresource into the ISP state.
INIT_OSU. If INIT_OSU is set, LifeKeeper assumes the resource is not started up during initialization andthat the system administrator will manually start up the resource using LifeKeeper Graphical User Interface(GUI) application.

ins_setlocalrecover
ins_setlocalrecover [-d destsys] -t tag -l {Y=enable|N=disable}
This command modifies the local recovery setting for the resource specified by the tag name "-t".
Example:To disable local recovery for the file share resource FSList.0, run the following command from$LKROOT\bin:ins_setlocalrecover -t FSList.0 -l N

ins_setst
ins_setst [-d destsys] -t tag -S {ISP|ISU|OSU} [-R reason] [-A]
Sets the resource state on system destsys with tag name tag to the state specified in the -S option. If
destsys is not specified, the current system is assumed. Use this command cautiously because the resource
state will be changed by the resource’s action script (e.g. remove or restore script). The caller is responsible
for making sure the new state reflects the actual state of the application.
Additional text explaining the reason for the change of state may be provided by the -R option. The -A option
sets the state of the specified resource and all the resources that depend on it, recursively up the hierarchy.

LCDI-relationship

Synopsis
dep_create [-d destsys] -p partag -c chdtag
dep_remove [-d destsys] [-p partag] [-c chdtag]
dep_list [-d destsys] [-fC] [-C allchild | -P allparent | -c ofparenttag | -p ofchildtag] [-r typ] [-a app]
eqv_create [-d destsys] [-s sys] -t tag [-p sysPriority] [-Sothersys] -o othertag [-r othersysPriority] -e
SHARED

SteelEye Protection Suite for Windows Technical Documentation
Page 61

Description

eqv_remove [-d destsys] [-s sys] -t tag [-S othersys] -o othertag -e SHARED
eqv_list [-d destsys] [-s sys] [-t tag] [-fC]

Description
LifeKeeper resources exist in relationship to one another. Two resources may be unrelated or they may be ina dependency relationship. In a hierarchy, a resource may have several resources depending upon it,and it
may depend upon several resources. Each resource also relates to a like resource on the paired system witha shared equivalency. This shared equivalency ensures that a resource is active on only one system at atime. Equivalency object also indicates priority of the system for the resource. This priority value determines
the order of cascading failover. A higher priority system has precedence over a lower priority system inrecovering the resource. A priority value of 1 is the highest. The higher the numerical value the lower thepriority. Two systems can’t be assigned same priority for a resource. Valid range is 1 to 1024.

Exit Codes
All commands exit 0, if successful, and a nonzero code and prints to standard error, for failure. The following
exit codes could be returned by these commands:
0 The operation has succeeded.
1 A system call or library call has internally returned failure.
2 A user-specified syntax error occurred.
3 LifeKeeper internal error.
4 A request to perform an operation on an object that already exists.
5 An argument specified is illegal.
6 Index out-of-range.
7 A request has been made on an object that does not exist.
8

A request was made to delete a resource instance on which another non-deleted resource instancedepends.

9 An attempt to communicate with another system failed.

dep_create
dep_create [-d destsys] -p parent -c childThis function creates a dependency relationship between the resource instances with tags parent and child.
Both resources must be on the same system destsys. If destsys is not specified, the current system isassumed. This implies the parent resource now requires the child for proper operation. Both resource
instances must already exist and must be in the same state (ISP or OSU) for proper operation.

SteelEye Protection Suite for Windows Technical Documentation
Page 62dep_list

dep_list
dep_list [-d destsys] [-fC] [-C allchild | -P allparent | -c ofparenttag | -p
ofchildtag] [-r typ] [-a appname]
This function prints strings to standard output describing dependency relationships between resource
instances. If destsys is not specified, the current system is assumed. Each string is in the following form:
LK0-LKSYS:135.66.249.201
LK0-LKSYSA:FSLIST.0
FSLIST0:fi.vo.0
There are two fields in each string that are separated by a delimiter character. The default delimiter characteris ^A (\001). If the -fC option is specified, the delimiter is changed to the character specified. The example
above shows a colon (:) as a delimiter. The first field indicates the parent tag name of the relationship and thefield on the right is the child tag name.
You can use options to limit the contents of the list. If you use no options, all dependencies are printed. The
command has the following options:- If the -C option is specified, this command will print out all direct and indirect child dependencies of the
C resource specified in allchild.
- If the -P option is specified, this command will print out all direct and indirect parent dependencies of the
P resource specified in allparent.
- If the -c option is specified, this command will print out only the direct child dependencies of thec resource specified in ofparenttag.
- If the -p option is specified, this command will print out only the direct parent dependents of the resource
p specified in ofchildtag.
-r Specifying the -r option lists all the dependencies of child typ.
Specifying the -a option lists all the dependencies of application appname.
adep_remove
dep_remove [-d destsys] [-p parent] [-c child]
Removes the dependency relationship(s) from the database on system destsys. If destsys is not specified,the current system is assumed. If child is not specified, all dependencies of parent are removed. If parent is
not specified, all dependents with tag child are removed. If both are not specified, all dependencies are
removed.

SteelEye Protection Suite for Windows Technical Documentation
Page 63eqv_create

eqv_create
eqv_create [-d destsys] [-s sys] -t tag [-p sysPriority][-S othersys] -oothertag [-r othersysPriority] -e SHARED
Creates an equivalency in the configuration database on system destsys (local, if not specified).
LifeKeeper will automatically add a SHARED equivalency on a remote system, if either sys or othersys is
specified. The resource specified as tag on system sys will be assumed by LifeKeeper to be the ”primary”
resource that runs under normal conditions; the resource specified as othertag on system othersys will be the”secondary” resource on the paired system. When LifeKeeper initializes, the primary resource is set
depending upon resource initialization set up [see LCDI_instances]. If the spare system boots, LifeKeeper on
the spare checks the primary system to see if the primary system is functioning and if the primary resource isin the ISP state. If both cases are true, LifeKeeper puts the secondary resource into the OSU state (resource
initialization ignored). If either case is false, the secondary resource will be initialized according to ”resource
initialization.” The priority value specified with -p option is the priority of system sys for the resource tag. The
priority value specified with -r option is the priority of system othersys for the resource othertag.

eqv_list
eqv_list [-d destsys] [-s sys] [-t tag] [-e SHARED] [-fC]
This function prints strings to standard output describing equivalency relationships between resource
instances. If destsys is not specified, the current system is assumed. Each line contains fields separated bya delimiter character. The default delimiter character is ^A (\001). If the -fC option is specified, the delimiter ischanged to C.
The example listings below show a colon (:) as a delimiter.
LKSYSA:135.66.249.201:LKSYSB:135.66.249.201:SHARED
LKSYSA:FSLIST.0:LKSYSB;FSLIST.0:SHARED
LKSYSA:LK0-LKSYSA:LKSYSB:LK0-LKSYSA:SHARED
Using LKSYSA:fi.vo.0:LKSYSB;fi.vo.0:SHARED, these are the fields:
LKSYSA

Primary system name where the resource resides.

fi.vo.0

Volume resource tag on the primary system.

LKSYSB

System name for the secondary system, where the resource equivalency resides.

fi.vo.0

Volume resource tag for the equivalent resource on the secondary system

SHARED Equivalency type.
The remaining arguments limit the information output as specified below:-s sys. This option limits the output to include only the equivalencies relating to the system specified by thesys argument.

SteelEye Protection Suite for Windows Technical Documentation
Page 64eqv_remove-t tag. This option limits the output to include only the equivalencies relating to the tag specified by the tagargument.
-e SHARED. This option prints all SHARED equivalency information.

eqv_remove
eqv_remove [-d destsys] [-s sys] -t tag [-S othersys]-o othertag [-e SHARED]
Removes equivalency from the configuration database on system destsys (local if not specified) of
equivalency type, specified by the -e option, between the resources tag and othertag existing on systems sys
and othersys, respectively. If sys or othersys is not specified, the current system is assumed.

LCDI-resource_type
Synopsis
typ_create [-d destsys] -a appname -r restyptyp_remove [-d destsys] -a appname -r restyp
typ_list [-d destsys] [-fC] [-a appname]

Description
Resources are used by LifeKeeper to represent volumes, applications or other objects known by the system.
Resource types are classifications of resources and are distinguished by a common set of recovery
procedures that can be applied to all instances. Resource type examples would include:lFile system volumes, for example K:lFile shares, for example UTIL_SHAREl

IP addresses, for example 153.66.232.21.

The typ_create and typ_remove commands provide an interface for generating new types in theconfiguration database. The command typ_list provides an interface to the configuration database forlisting all resource types existing on a specific system.

Exit Codes
All commands exit 0 if successful. On failure, they return a nonzero code (see EXIT CODES section) andprint to standard error. The following exit codes could be returned by these commands:

SteelEye Protection Suite for Windows Technical Documentation
Page 65

typ_create

0 The operation has succeeded.
1 A system call or library call has internally returned failure.
2 A user-specified syntax error occurred.
3 LifeKeeper internal error.
4 A request to perform an operation on an object that already exists.
5 An argument specified is illegal.
6 Index out-of-range.
7 A request has been made on an object that does not exist.
8

A request was made to delete a resource instance on which another non-deleted resource instancedepends.

9 An attempt to communicate with another system failed.

typ_create
typ_create [-d destsys] -a appname -r restypCreates a new resource type in the configuration database on system destsys (local, if not specified). The
resource type is named restyp and is installed under the already-existing application, appname. Failure
occurs if the system or application is not known or if the resource type already exists.

typ_list
typ_list [-d destsys] [-fC] [-a appname]
This command prints to standard output a list of resource types that have been defined on the application,
appname, installed on system destsys (local,if not specified). If appname is not specified, all resource types
for all applications are printed in the following format:
filesys:volumecomm:ip
database:informix
The application name is to the left of the delimiter and the resource typename is to the right. Each line
contains fields separated by a delimiter character. The default delimiter character is ^A (\001). If the -fC
option is specified, the delimiter is changed to the specified character. The above example shows a colon (:)
as the delimiter.

typ_remove
typ_remove [-d destsys] -a appname -r restyp

SteelEye Protection Suite for Windows Technical Documentation
Page 66

typ_remove

Removes the given resource type from the configuration database set of known resource types of system
destsys (local, if not specified). All resource instances, dependencies, and equivalencies associated withthis type are also removed. Failure occurs if the resource type is not known to the configuration database.

SteelEye Protection Suite for Windows Technical Documentation
Page 67LCDI-systems

LCDI-systems
Synopsis
sys_create [-d destsys] -s sys
sys_remove [-d destsys] -s sys
sys_getds [-d destsys] -s sys
sys_getst [-d destsys] -s sys
sys_list [-d destsys]

Description
The LifeKeeper configuration database knows about related systems. Because resources and resource types
are specific to the systems on which they exist, it is necessary for the configuration database interface tocontain the concept of a system.
The LCDI-systems commands return (or create) information into or remove information out of the database.

Exit Codes
All commands exit 0, if successful, and a nonzero code and prints to standard error, for failure. The following
exit codes could be returned by these commands:
0 The operation has succeeded.
1 A system call or library call has internally returned failure.
2 A user-specified syntax error occurred.
3 LifeKeeper internal error.
4 A request to perform an operation on an object that already exists.
5 An argument specified is illegal.
6 Index out-of-range.
7 A request has been made on an object that does not exist.
8

A request was made to delete a resource instance on which another non-deleted resource instancedepends.

9 An attempt to communicate with another system failed.

SteelEye Protection Suite for Windows Technical Documentation
Page 68sys_create

sys_create
sys_create [-d destsys] -s sys
Creates a new system definition in the configuration database on system destsys (local, if not specified). The-s sys option is required to identify the system to which the system name is assigned.

sys_getds
sys_getds [-d destsys] -s sys
Prints to standard output the optional text description of why the system has gone to the current state from thedatabase on system destsys (local, if not specified).

sys_getst
sys_getst -s sys
Prints the system’s state to standard output as one of the strings:
DEAD

The system is believed to be unavailable.

ALIVE

The system is believed to be available.

UNKNOWN System state is unavailable.

sys_list
sys_list [-d destsys]
This command prints to standard output a list of systems that LifeKeeper knows about from the database on
system destsys (local, if not specified).

sys_remove
sys_remove [-d destsys] -s sys
Removes a system definition from the configuration database on system destsys (local, if not specified). The-s sys option is required to identify the system to which the system name is assigned.

LifeKeeper Flags
Near the end of the detailed status display, LifeKeeper provides a list of the flags set for the system. A
common type is a Lock LCD flag used to ensure that other processes wait until the process lock completes its
action. The following is the standard LCD lock format:!action!processID!time!machine:id.

SteelEye Protection Suite for Windows Technical Documentation
Page 69

flg_create

These are examples of general LCD lock flags:l!action!02833!701236710!<servername>:Restore_hierarchy. The creation of a filesystem hierarchy produces a flag in this format in the status display. The filesys designation can beappdp for applications with disk partition hierarchies or appfs for applications with file systemhierarchies.

lOther typical flags include !nofailover!machine and shutdown_switchover. The!nofailover!machine flag is an internal, transient flag created and deleted by LifeKeeper which
controls aspects of server failover. The shutdown_switchover flag indicates that the shutdown
strategy for this server has been set to switchover such that a shutdown of the server will cause aswitchover to occur. See LCDI Flags for more detailed information on the possible flags.

flg_create
flg_create [-d destsys] -f flag
The flag flag is created on system destsys.
Note: This only modifies the ”shared memory” segment of the LifeKeeper configuration database.
The LifeKeeper lcdsync command should be run after this command to ensure that the shared memorychanges are reflected into the permanent storage onto a disk file.

flg_list
flg_list [-d destsys]
flg_list prints to standard output a short listing, one flag per line, of all of the flags currently defined on thissystem (unless destsys is specified). The listing is not in any particular order.

flg_remove
flg_remove [-d destsys] -f flag

The flag flag is removed on system destsys.
Note: This only modifies the shared memory segment of the LifeKeeper configuration database.
The LifeKeeper lcdsync command should be run after this command to ensure that the shared memorychanges are reflected into the permanent storage onto a disk file.

flg_test
flg_test [-d destsys] -f flag
A check is made to see if the flag flag exists on system destsys. Returns 0 or 7.

SteelEye Protection Suite for Windows Technical Documentation
Page 70

LCDI Flags

LCDI Flags
Synopsisflg_create [-d destsys] -f flag
flg_remove[-d destsys] -f flag
flg_test[-d destsys] -f flag
flg_list[-d destsys]

Description
LifeKeeper provides a facility to dynamically set flags to perform various tasks. The following special purpose
flags can exist.
!nofailover!uname
If this flag exists, failover is inhibited for resources on the system with name, uname, that have defined thesystem with the flag on it as their backup system. Note: This is a temporary flag that will be removed
automatically when LifeKeeper detects that system uname is ALIVE.
!action!procid!timestamp!uname:identifierThis is an example of an ”admin lock flag” [see getlocks]. These flags are used for actions that require that noother action be performed at the same time on any of the systems in a LifeKeeper configuration. For example,
you may not create a hierarchy on one system while creating a hierarchy on another. The ”admin lock flags”
are used to ensure that one of these ”global” operations is not performed until the one currently runningcompletes.
The identifier field of the ”admin lock flag” identifies the kind of action being performed. The system that theprocess that requested the”admin lock flag” was running on is specified by uname. The flag was created attimestamp number of seconds after Jan 1, 1970, by a process with a process ID of procid that called getlocks[see getlocks].
An example of such a flag is as follows:!action!01525!701120147!cindy:Create_Hierarchy
This flag indicates that the action Create_Hierarchy is in progress, indicating a hierarchy is being created.
The process with process ID1525 requested the ”admin lock flag,” at the time 701120147 on system cindy.
!restoreThis flag is set by LifeKeeper when the prerestore scripts [see LCD] are run. It indicates that the postrestore
scripts should be run. Normally, this is a transitory condition that LifeKeeper automatically fixes when the
postrestore scripts [see LCD] run. The only exception is if the postrestore scripts are being explicitly run
using the following command:%LKROOT%\bin\lcdrecover -G restore!restore!uname

SteelEye Protection Suite for Windows Technical Documentation
Page 71

lk_chg_value

When this flag is set it indicates that the postrestore scripts [see LCD] should be run remotely on system
uname. When the postrestore scripts are run on this system, LifeKeeper sends a remote request to system
uname to run its postrestore scripts. Normally, this is a transitory condition that LifeKeeper automatically
fixes. The only exception is if the postrestore scripts are being explicitly run using the%LKROOT%\bin\lcdrecover -G restore command.
!remove
This flag is set by LifeKeeper when the preremove scripts [see LCD] are run. It indicates that the postremove
scripts should be run at a later time. Normally, this is a transitory condition that LifeKeeper automatically fixes
when the postremove scripts [see LCD] are run at a later time. The only exception is if the postremove scripts
are being explicitly run using the following command:%LKROOT%\bin\lcdrecover -G remove!remove!uname
When this flag is set it indicates that the postremove scripts [see LCD] should be run remotely on system
uname. When the postremove scripts are run on this system, a remote request is sent to system uname to run
its postremove scripts. Normally, this is a transitory condition that LifeKeeper automatically fixes. The only
exception is if the postremove scripts are being explicitly run using the %LKROOT%\bin\lcdrecover -G
remove command.
!deleteThis flag is set by LifeKeeper when the predelete scripts [see LCD] are run. It indicates that the postdelete
scripts should be run at a later time. Normally, this is a transitory condition that LifeKeeper automatically fixes
when the postdelete scripts [see LCD(1M)] are run. The only exception to this is if the postdelete scripts arebeing explicitly run by using the following command:%LKROOT%\bin\lcdrecover -G delete!delete!uname
When this flag is set it indicates that the postdelete scripts [see LCD] should be run remotely on system
uname. When the postdelete scripts are run on this system, a remote request is sent to system uname to run
its postdelete scripts. Normally, this is a transitory condition that LifeKeeper automatically fixes. The only
exception is if the postdelete scripts are being explicitly run using the following command:%LKROOT%\bin\lcdrecover -G delete

lk_chg_value
NAME
lk_chg_value.ksh --- changes specified values in local LifeKeeper configuration database files

SYNOPSIS
lk_chg_value.ksh {-o old_value -n new_value | -f filename} [-vFIMT]

SteelEye Protection Suite for Windows Technical Documentation
Page 72

DESCRIPTIONDESCRIPTIONThis command is to be used to modify arbitrary values in local LifeKeeper configuration database files (e.g.
LifeKeeper uname, communication path addresses, resource tag names, etc.). lk_chg_value.ksh needs tobe run locally with the Administrator login on each machine within a LifeKeeper configuration while LifeKeeper
is not running. Also, you must use the LifeKeeper provided shell (sh.exe) to invoke the script as shown
above. This command does not modify the system's uname or network interfaces. If the LifeKeeper uname
or communication path addresses are to be modified, the system uname and network interfaces must be
modified prior to the execution of this command using system utilities. In order for LifeKeeper to be properly
updated, this command must be run on every system in the cluster.
The values to be modified may be specified on the command line using the -o and -n options or in a file using
the -f option. The syntax of a file containing substitutions is old_value=new_value, with one substitution perline (lines not in this form are ignored).
To see the changes lk_chg_value.ksh will make without modifying any LifeKeeper files, use the -M option.
To see the files lk_chg_value.ksh is examining, use -v. To not modify tag names, use the -T option. To not
modify resource ids, use the -I option.
Because a resource id may contain structured information, lk_chg_value.ksh does not allow substitutions
that completely replace the id field. To override this behavior, use the -F option.

EXAMPLES
Systems A, B, and C have been configured in a LifeKeeper configuration. Systems A and B manage adatabase resource and system A also manages a communication resource with System C. To modify theuname and comm path address of System A with comm path old address, the following must be performed:
1. Stop LifeKeeper by executing the lkstop command on each affected system. However, if theresources being managed are to stay available to the user community, execute lkstop -f.
2. Change System A's uname to X and change the network address to new_address. Create asubstitutions file, /tmp/lksubs, containing the substitution pairs:
A=X old_address=new_address
As Administrator, login to System A and execute the following:
set LKROOT=<LKROOT> (i.e. set LKROOT=C:\LK)<LKROOT>\bin\sh.exe

lk_chg_value.ksh-vf /tmp/lksubs

This changes all local occurrences of A and old_address found within the LifeKeeper core and recovery
kits on System A, which is now identified by System X, to refer to X and new_address, respectively.
3. Copy the substitutions file from System A to Systems B and C. As Administrator, login to Systems B
and C and execute the following:
set LKROOT=<LKROOT> (i.e. set LKROOT=C:\LK)

SteelEye Protection Suite for Windows Technical Documentation
Page 73EXIT CODES<LKROOT>\bin\sh.exe

lk_chg_value.ksh-vf /tmp/lksubs

This changes all occurrences of A and old_address found within the LifeKeeper configuration databaseon Systems B and C to refer to X and new_address, respectively.

EXIT CODES
0 Execution of command completed successfully.
1 Interrupt occurred... files restored.
2 Invalid arguments passed to command.
3 LifeKeeper processes are still running.
4 Command needs to be executed by an Administrator login.
5 ID field change attempted. Resource ID cannot be changed without using -I option.
6 LKROOT environment variable not set.
7 No matches were found.

NOTES
The lk_chg_value.ksh utility is located in the <LKROOT>\bin folder.
The lk_chg_value.ksh utility is case sensitive.
As shown above you must use the LifeKeeper provided shell (sh.exe) to invoke the lk_chg_value.ksh script.
<LKROOT> refers to the LifeKeeper home directory. The default home directory is C:\LK, but this can be
modified during LifeKeeper installation.

FILES<LKROOT>\bin\lk_chg_value.ksh

lk_errSynopsislk_err -c Category -n Error number -p Process Name [-d {TO_LOG |TO_STDERR}]”Message”

SteelEye Protection Suite for Windows Technical Documentation
Page 74

Description

Description
This utility is used within recovery scripts to log errors to the Microsoft Event Log. It also prints messages tostderr.
The arguments are:Category. The following is a list of LifeKeeper message categories and their Event Log classifications:

LK Category Event Category Event TypeFRS_MES

GeneralInformation

FRS_WARN

GeneralWarning

FRS_ERR

GeneralError

Error Number. Must be a positive integer.
Process Name. Name of the script calling lk_err.
Destination. The destination parameter is optional. By default, events generated by lk_err will be directed toboth the Windows Event Log (TO_LOG) and to the system console stderr message stream (TO_STDERR). However, with the -d option you may direct events specifically to one destination or the other.
Please note, however, that messages directed to the stderr (TO_STDERR) by programs or scripts that are
executed by the LifeKeeper core will not display on the system console because the LifeKeeper core runs
them as background tasks without interactive properties. Therefore, directing messages to stderr is useful
only as a manual script testing and debugging aid.
Message. Message string must be enclosed in ” ”.

perform_action
Synopsis
perform_action [-G] [-s] [-b] [-n] -t tag-name -a action-name [- - arg1 arg2... argn]

Description
The LRACI program perform_action performs processes in the following order:lFinds the resource specified by the tag-name argument of the -t option.

lFinds the action script specified by the action-name argument of the -a option.

SteelEye Protection Suite for Windows Technical Documentation
Page 75

DescriptionlExecutes the action script on the tag-name resource instance.

The arguments after the -- argument are passed unchanged to the action script(s). These are arguments thatthe developer of the action may optionally require to use the action.
The perform_action program finds the action script by the following algorithm: it first searches in the actions
directory for the resource type of the resource instance specified by tag-name:%LKROOT%\subsys\appname\resources\restypname\actions\action-name.ksh
and if not there, it checks the actions directory of the application the resource instance belongs to:%LKROOT%\subsys\appname\actions\action-name.ksh
The restore and remove actions are special cases for LRACI. The restore action moves an application
hierarchy that may be in-service on the remote system to the local system. For restore, LRACI first checks tomake certain that the resource instance tag-name is not already in the ISP state. If it is not, it recursively
checks all of the resource instances that this resource depends upon. The check continues until a resource isfound that either depends on no resources, or all of the resources it depends on are already in the ISP state. If
the resource was in the ISU state,it is placed in the ISP state.
If the resource was in the OSU or OSF state, LRACI executes the remove script for any affected resourceson the remote system. When this completes, LRACI finds the restore action using the above algorithm andruns it. If the script fails, the resource is placed in the OSF state and LRACI stops. If it succeeds, LRACI
recursively ”restores” the resources up the tree, until the resource specified by tag-name is restored. Then the
LRACI recursively checks and ”restores” the parent resource instances in a similar fashion until all related root
resource instances are restored. In each case, LRACI uses the above algorithm to find the correct restore
script using the resource application and resource type of the resource currently being scanned by LRACI, not
the resource application and resource type of the tag-name resource.
For the remove action, the resources are moved recursively in the opposite direction. LRACI calls the remove
script of all resources starting at the root resources that depend directly or indirectly on the tag-name resource
down to, and including, the tag-name resource if any of those resources are in the ISP or ISU state.
Resources not in the ISP or ISU state are ignored. If one of the remove scripts fails, LRACI places the failingresource into the OSF state and stops. In each case, LRACI uses the algorithm to find the correct remove
script using the resource application and resource type of the resource currently being scanned by LRACI, not
the resource application and resource type of the tag-name resource.
The remove and restore actions automatically have the -t tag-name and -i ident-field arguments added to theargument list that corresponds to the resource instance being acted upon.
The following sections discuss the arguments accepted by perform_action.

SteelEye Protection Suite for Windows Technical Documentation
Page 76

Description

This option is only used if action-name is remove, restore, or delete. If this option is not specified,
LRACI performs the preglobal and postglobal scripts before and after the actions are performed[see lcdrecover in LCD]. If the option is specified, LRACI does not run the preglobal andpostglobal scripts.
-G

This option is useful if you need to run perform_action more than once, but you only want to run
the preglobal and postglobal scripts once. It is also useful if you need to run perform_action while
creating a resource hierarchy. The preglobal and postglobal scripts should not be run by perform_
action during hierarchy create because the hierarchy creation scripts should be set up to obtain the”admin lock flags” [see LCDI_flag] and postrestore also requires the ”admin lock flags” which
would lead to contention problems.

-s

The default behavior for the restore action is to bring all objects above and below the specified tag
into service, and the default behavior for the remove action is to bring all objects above thespecified tag out of service. The -s option limits the scope of the operation to just the specified flag.

-b

The default behavior for the restore action is to bring all objects above and below the specified tag
into service. The -b option changes this behavior to just objects below the specified tag. This
option has no effect on the remove action.
This option is only used if the action-name is remove or restore. If this option is specified, theresource reserves are not to be checked and the actions are performed whether the resources arereserved or not.
WARNING: EXTREME CAUTION SHOULD BE TAKEN WHEN USING THIS OPTION!

-n

If this option is not specified, before any remove or restore scripts are executed, LRACI checks to
see if any of the resources on which any of the actions will be run are currently reserved by anotherprocess. A resource can be reserved while the following operations are being performed on them:a resource ”remove from service” is in progress, a ”resource restore to service” is in progress, or aresource ”recovery” is in progress.
If any resource is so reserved, LRACI waits a specified period of time for the process to remove
the reserve on the resource. If that period expires, LRACI removes the reserve. In either case,LRACI reserves all of the resources, then follows the specified algorithm to perform the action(s).

-t tagnameThis is the last resource instance the action will be performed on.

-aactionname This is the resource action that will be performed.

-- arg1
Argument(s) the resource action developer can optionally define to be passed to the action script.
arg2
When executing perform_action within a getlocks protected region and the -G option is not used,...
set arg1 to -m to avoid executing a second instance of getlocks, which would cause the operationargn
to hang.

SteelEye Protection Suite for Windows Technical Documentation
Page 77

Example

ExampleThe following is an example of calling an action:
perform_action -t SCSI-USR-DISK -a reset-heads -- -h 7
The LRACI program perform_action would find the action corresponding to reset-heads and execute it withthe arguments:
reset-heads -t SCSI-USR-DISK -h 7

Exit Codes
The following exit codes could be returned by LRACI:
0 The operation has succeeded.
1 A system call or library call has internally returned failure.
2 A user-specified syntax error occurred.
3 LifeKeeper internal error.
4 A request to perform an operation on an object that already exists.
5 An argument specified is illegal.
6 Index out-of-range.
7 A request has been made on an object that does not exist.
8

A request was made to delete a resource instance on which another non-deleted resource instancedepends.

9 An attempt to communicate with another system failed.

sendeventSynopsis%LKROOT%\bin\sendevent -C class-of-event -E event -m monitor-name -nname-ofobj-inst [-s severity]

Description
The event notification facility consists of two parts: an event notification mechanism(%LKROOT%\bin\sendevent) and an application registration environment. Applications wishing to use theSteelEye Protection Suite for Windows Technical Documentation
Page 78

Description

event facility should ”register” to get notification of specific events or alarms (or all occurrences of
event/alarms).
The sendevent command is a program invoked by a daemon monitor process when the monitor has detected
an event (failure or recovery) in the objects that it is monitoring. This command is not intended to be run
directly at the shell level by a regular user or by a system administrator (only by a daemon process or anothercommand).
The sendevent command is used to notify a ”registered” application of the occurrence of an event. For
example, an application may want to be notified of an impending system shutdown so it can appropriately
save files and data; or, in a client-server environment, the application may need to reconfigure itself to analternate service provider. The application is responsible for providing the appropriate command support tohandle the event.
The sendevent command passes all of its options to the event-response commands of the application.
An application registers to receive notification of events or alarms by installing its event-response commands
in a specific registration directory, %LKROOT%\events. This should be done at application installation time.
The events under %LKROOT%\events are further categorized in classes of events. Create separate
subdirectories, genclass (for general events) and allclass to be used by applications to register to be notified
upon occurrence of any event.
Note: If an event occurs which causes an application to place application-response commands in both thespecific event location and the all location, both scripts run.
Each class directory contains a subdirectory for each event within that class. Each add-on package thatmonitors events and uses this event notification mechanism documents events it monitors and supports.
It is the responsibility of the application object monitor package to maintain a file called ACTIVE in the events
subdirectories. If the ACTIVE file exists, it is a signal to the applications that a monitor is currently actively
running and monitoring its objects for that specific event. If the package containing the monitor program isremoved, the files named ACTIVE for the affected monitored events are removed too (by the package remove
script) to indicate to applications that the event is no longer being monitored. The removal of the package
should not remove event-response commands or event directories even if they are empty.
For those applications that may depend upon standard commands from another application, the application
registration environment provides other application-specific directories, %LKROOT%\subsys\applicationname\actions, for applications to place ”sharable” action commands. For example, application X may depend
upon application Y being up and running after an event recovery. If this is not the case, application X may
invoke the start command for application Y from the LKROOT%\subsys\Y\actions\start directory.
Interdependencies between applications must be resolved and specified by the application developers.
The -C (class of event), -E (event), -m (monitor name), and -n (name of object instance) options are required.
If the -s (severity) option is not specified, sendevent will default to a severity of MAJOR alarm.
Upon invocation of the sendevent command by a monitoring process, sendevent determines which eventclass and event has occurred based upon the arguments to the -C and -E options. The sendevent commandexecutes in the background until it finishes processing all the event-response commands (if any) placed in theregistration directory corresponding to that class/event pair and all of the commands registered in the all
directory.
The following options are supported:

SteelEye Protection Suite for Windows Technical Documentation
Page 79

Output-C class-of-event
Events are grouped together into classes. This required option indicates which class the event belongs to.
-E event
This required option indicates which event in a class is being triggered.
-m monitor-name
Each application object monitor that can send alarms/events is identified by a name in the form:
OM-product-name:OM-component-name
OM-product-name is an ASCII string, of up to eight characters. It is an abbreviated identifier specifying the
product that monitors the objects that cause alarms or events. OM-component-name is an ASCII string, of up
to 16 characters. It is defined by the object monitor to identify the component of the object monitor that
detected the alarm or event.
The monitor names are used to distinguish between different products that may be used to monitor the same
object.
-n name-of-obj-inst
This option is used to name a specific instance of an application object. It is an ASCII string with a maximum
length of 64 characters. For example, D: may be the name of a volume application object, whereas 1234
could be used to identify a specific process object.
-s severity
Each alarm or event must specify the severity of the problem it is reporting. If this option is not specified,sendevent internally adds the default severity for MAJOR alarm. Severity is an ASCII represented integerinterpreted as follows:
0 CLEARED alarm specified by ”id-of-alarm/event” has been recovered
1 INFORMATIONAL alarm (INFO message or cmn_err() NOTICE message)
2 WARNING alarm (WARNING message)
3 MINOR alarm (MINOR message)
4 MAJOR alarm (MAJOR or ERROR message) (default)
5 CRITICAL alarm (CRITICAL message or cmn_err() PANIC or HALT message)

OutputThe output this command generates occurs in one of two conditions:lError messages are printed to standard error and a nonzero exit code is returned.

l

The identifier for the alarm\event called id-of-alarm/event is printed to standard output at each call tosendevent.

SteelEye Protection Suite for Windows Technical Documentation
Page 80

Exit Codes

Exit Codes
The following exit codes are returned by sendevent:
0 The sendevent command has completed successfully without errors.
1 Syntax error in the argument list.
2

No class corresponding to the string passed with the -C option exists in the %LKROOT%\events
directory.

3

No event corresponding to the string passed with the -E option exists in the%LKROOT%\events\<class> directory.

4 The -A option is internally generated and may not be specified directly.
5 The -i option must be specified if the -s 0 (severity CLEARED) option is used.

volumeSynopsisvolume [ -d | -D ][-l | -u | -p | -U

volume_letter ]Description
This command is used to lock and unlock volumes on the Windows server. It may also be used to registerwith the LifeKeeper Service. When used in this fashion, it determines which volumes should be protected(locked) by LifeKeeper at startup. The lock provides LifeKeeper with exclusive access to the volume and will
not allow any other process to access the volume.
LifeKeeper must be running in order for this command to succeed. The command interfaces with the
LifeKeeper Service to provide the locking mechanism.
The following options are available where volume_letter is the drive letter to be locked\unlocked orprotected\unprotected (i.e. C to Z).
Display the currently locked volumes.
d- Display the volumes that are registered with LifeKeeper. This would display volumes that have been
D added with the -p option. Generally, -D displays a different list than the one shown by the -d option.
-l

Lock the volume for exclusive access. The lock will fail if a remote user has opened the volume or a
local application has opened the volume for a write operation.

Unlock the volume from exclusive access.
u

SteelEye Protection Suite for Windows Technical Documentation
Page 81Example- Register the volume with LifeKeeper, so that on subsequent reboots or restarts of LifeKeeper, thep volume is automatically locked.
Unregister the volume with LifeKeeper so that it is not automatically locked on LifeKeeper startup
U

ExampleThe following illustrates how the volume command should be used:## Register drive volume e: to be locked by LifeKeeper#
ret=`volume -p E`
if [ $ret -gt 0 ]then#Report error that it wasn’t protectedfi## Lock volume e: for exclusive access#ret=`volume -l E`
if [ $ret -gt 0 ]then#Report error that it wasn’t lockedfiExit Codes
The following exit codes could be returned by this command:0

The operation has succeeded.

greater than 0

The operation has failed. An error message is printed to standard error.

SteelEye Protection Suite for Windows Technical Documentation
Page 82

LKSUPPORTLKSUPPORTLKSUPPORT, found in the LK/SUPPORT directory, is used to collect important configuration information andevent log files and put them in a zip file. SIOS Support Engineers will commonly request this zip file as part of
the Support process. To run this utility, simply double-click LKSUPPORT and the zip file will be created in thesame Support directory.

Setting Browser Security Parameters
In order to run the GUI web client, you must set your browser security settings to low. For Internet Explorer,
follow the procedures below.
WARNING: Be careful of other sites you visit with low security settings.

Internet Explorer
The most secure method for using Internet Explorer is to add the SteelEye Protection Suite server to theTrusted Sites zone as follows:
1. From the Tools menu, click Internet Options.
2. Click the Security tab.
3. Select Trusted Sites zone and click Custom Level.
4. Under Reset custom settings, select Medium/Low, then click Reset.
5. Click Sites.
6. Enter the server name and port number for the SteelEye Protection Suite server(s) to which you
wish to connect (for instance: http://server1:81).
An alternative, but possibly less secure method is to do the following:
1. From the Tools menu, click Internet Options.
2. Select either Internet or Local Intranet (depending upon whether your remote system and theSteelEye Protection Suite cluster are on the same intranet).
3. Adjust the Security Level bar to Medium (for Internet) or Medium-low (for Local Intranet). These are
the default settings for each zone.
4. Click OK.

IP Local Recovery
When IP Local Recovery is enabled and the IP resource fails its deepcheck (a periodic extensive check of the
IP resource), then SteelEye Protection Suite will do the following:

SteelEye Protection Suite for Windows Technical Documentation
Page 83

Overview of SteelEye Protection Suite Event Forwarding via SNMPlFirst, SteelEye Protection Suite will attempt to bring the IP address back in service on the current
network interface.

l

If that fails, SteelEye Protection Suite will check the resource instance to determine if there is a
backup interface available. If so, it will then attempt to move the IP address to the backup interface.

l

If all local recovery attempts fail, SteelEye Protection Suite will perform a failover of the IP address andall dependent resources to a backup server.

Even if you do not have a backup adapter, you can enable Local Recovery so that SteelEye Protection Suite
will retry the primary network interface before initiating failover to a backup server.

Overview of SteelEye Protection Suite Event Forwarding via
SNMP
The Simple Network Management Protocol (SNMP) defines a device-independent framework for managing
networks. Devices on the network are described by MIB (Management Information Base) variables that aresupplied by the vendor of the device. An SNMP agent runs on each node of the network and interacts with a
Network Manager node. The Network Manager can query the agent to get or set the values of its MIB
variables, thereby monitoring or controlling the agent's node. The agent can also asynchronously generatemessages called traps to notify the manager of exceptional events. There are a number of applications
available for monitoring and managing networks using the Simple Network Management Protocol (SNMP).
SteelEye Protection Suite has an event notification mechanism for registering applications that wish to be
notified of specific events or alarms (see the sendevent man page). SteelEye Protection Suite can be easily
enabled to send SNMP trap notification of key SteelEye Protection Suite events to a third party network
management console wishing to monitor SteelEye Protection Suite activity. SteelEye Protection Suite
installs an MIB file under %LKROOT%\include\LifeKeeper-MIB.txt which describes SteelEye
Protection Suite trap definitions.
The remote management console receiving SNMP traps must first be configured through the administration
software of that system; SteelEye Protection Suite provides no external SNMP configuration. The remotemanagement server is typically located outside of the SteelEye Protection Suite cluster (i.e., it is not a
SteelEye Protection Suite node).

SteelEye Protection Suite Events Table
The following table contains the list of SteelEye Protection Suite events and associated trap numbers. The
entire Object ID (OID) consists of a prefix followed by a specific trap number in the following format:
prefix.0.specific trap number
The prefix is .1.3.6.1.4.1.7359, which expands to iso.org.dod.internet.private.enterprises.7359 in the MIB
tree. (7359 is SIOS's enterprise number, followed by 1 for LifeKeeper.) For example, the LifeKeeper Startup
Complete event generates the OID: .1.3.6.1.4.1.7359.1.0.100

SteelEye Protection Suite for Windows Technical Documentation
Page 84

SteelEye Protection Suite Events Table

SteelEye Protection Suite Event/Description

Trap #

Object ID

LifeKeeper Startup Complete
100.1.3.6.1.4.1.7359.1.0.100

101.1.3.6.1.4.1.7359.1.0.101

102.1.3.6.1.4.1.7359.1.0.102

110.1.3.6.1.4.1.7359.1.0.110

111.1.3.6.1.4.1.7359.1.0.111

112.1.3.6.1.4.1.7359.1.0.112

120.1.3.6.1.4.1.7359.1.0.120

121.1.3.6.1.4.1.7359.1.0.121122.1.3.6.1.4.1.7359.1.0.122

130.1.3.6.1.4.1.7359.1.0.130131*.1.3.6.1.4.1.7359.1.0.131

Sent from a node when LifeKeeper is started on that node
LifeKeeper Shutdown InitiatedSent from a node beginning LifeKeeper shutdown
LifeKeeper Shutdown Complete
Sent from a node completing LifeKeeper shutdown
LifeKeeper Manual Switchover Initiated on Server
Sent from the node from which a manual switchover was
requested
LifeKeeper Manual Switchover Complete – recovered
list
Sent from the node where the manual switchover wascompleted
LifeKeeper Manual Switchover Complete – failed list
Sent from the node where the manual switchover wascompleted
LifeKeeper Node Failure Detected
Sent from each node within the cluster when a node in thatcluster fails
LifeKeeper Node Recovery Complete – recovered list
Sent from each node within the cluster that has recoveredresources from the failed node
LifeKeeper Node Recovery Complete – failed list
Sent from each node within the cluster that has failed torecover resources from the failed node
LifeKeeper Resource Recovery InitiatedSent from a node recovering a resource; a 131 or 132 trap
always follows to indicate whether the recovery wascompleted or failed.
LifeKeeper Resource Recovery Failed
Sent from the node in trap 130 when the resource being
recovered fails to come into service

SteelEye Protection Suite for Windows Technical Documentation
Page 85

SteelEye Protection Suite Events Table

SteelEye Protection Suite Event/Description

Trap #

Object ID

LifeKeeper Resource Recovery Complete
Sent from the node in trap 130 when the recovery of theresource is completed

132.1.3.6.1.4.1.7359.1.0.132

150.1.3.6.1.4.1.7359.1.0.150

160.1.3.6.1.4.1.7359.1.0.160

Mirror State Change
Sent from the node, who is the source of the mirror, when the
mirror state changes. Displays the volume letter, mirror stateand IP address of the target node.
Valid Mirror States:-1: Invalid State
0: No Mirror
1: Mirroring
2: Mirror is resyncing
3: Mirror is broken
4: Mirror is paused
5: Resync is pending
LifeKeeper replicated volume Split-Brain detected
Sent from the node where LifeKeeper has detected mirror is
Source on both sides. Displays volume letter and IP addressof the target node.

The following variables are used to "carry" additional information in thetrap PDU:
Trap message

all.1.3.6.1.4.1.7359.1.1

Resource Tag

130.1.3.6.1.4.1.7359.1.2

Resource Tag

131.1.3.6.1.4.1.7359.1.2

Resource Tag

132.1.3.6.1.4.1.7359.1.2

List of recovered resources

111.1.3.6.1.4.1.7359.1.3

List of recovered resources121.1.3.6.1.4.1.7359.1.3

List of failed resources112.1.3.6.1.4.1.7359.1.4

List of failed resources122.1.3.6.1.4.1.7359.1.4* This trap may appear multiple times if recovery fails on multiple backup servers.

SteelEye Protection Suite for Windows Technical Documentation
Page 86

Steps to Upgrade Java Runtime Environment (JRE) Version for SteelEye Protection Suite for Windows

Steps to Upgrade Java Runtime Environment (JRE) Version
for SteelEye Protection Suite for Windows
1. Download and install the latest 32-bit JRE from java.com. (Note: Make sure you are downloading the
32-bit Java.)
2. Run the installer. The first screen for the installer will have a check box to change the location of thedestination folder. This box SHOULD be checked.
3. Make a new subfolder in c:\lk (e.g. c:\lk\jre1.7) as the destination folder.
4. Repeat the above procedure (Steps 1-3) on the other node(s).
5. Stop LifeKeeper on the backup node(s).
net stop lifekeeper
6. Edit the registry keys.
Example For 64-bit OS
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SteelEye\LifeKeeper\JavaGUI :JavaVersion from "1.7.0_10" to "1.7"
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SteelEye\LifeKeeper\JavaGUI\
Server : JavaVersion from "1.7.0_10" to "1.7"
Example For 32-bit OS
HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\JavaGUI :JavaVersion from "1.7.0_10" to "1.7"
HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\JavaGUI\Server :JavaVersion from "1.7.0_10" to "1.7"

SteelEye Protection Suite for Windows Technical Documentation
Page 87

Notes

NOTE: The 1.7 points to the key that JavaSoft installed in the previous step as shown in the picture, make the appropriate adjustment
if the key is different.
7. If firewall is enabled, open the Windows firewall inbound rule "LifeKeeper Java" and edit the property"Programs and Services" tab and select the Java executable (e.g. c:\lk\jre1.7\bin\java.exe).
Change the description to state that it is for Java JRE <version number>.
8. Start LifeKeeper.
net start lifekeeper
9. Repeat Steps 5-8 on other backup nodes (if any).
10. Log in to SteelEye Protection Suite and switch the hierarchy to the backup node.
11. Repeat the procedure (Steps 5-8) on the primary node.
12. Bring the hierarchy in service on the primary node.
At this point, SteelEye Protection Suite has been upgraded using the latest version of Java.

Notes
1. If a repair is done on your SteelEye Protection Suite installation using the installer/repair option, repeat
the above Step 6 as a repair will reset the registry settings. The directory created in Step 3 should be
intact.
2. When uninstalling SteelEye Protection Suite, the directory created in Step 3 will need to be manually
removed.
3. The above steps assume that SteelEye Protection Suite was installed in the default folder c:\lk. If
not, change accordingly and replace c:\lk with the appropriate subdirectory.

SteelEye Protection Suite for Windows Technical Documentation
Page 88

Chapter 5: User Guide
The User Guide is a complete, searchable resource containing detailed information on the many tasks thatcan be performed within the LifeKeeper GUI.
The User Guide is broken up into the following areas:
LifeKeeper GUI - These topics give an overview and description of the LifeKeeper Graphical User Interface.
Common Tasks - These topics cover basic tasks that can be performed by any user such as connecting to acluster, viewing server or resource properties, viewing log files and changing GUI settings.
Operator Tasks - This section covers more advanced tasks that require Operator permission such as bringing
resources in and out of service.
Advanced Topics - This section details information on the LifeKeeper Configuration Database and LifeKeeper
Communications.
Maintenance Tasks - The topics in this section cover the tasks necessary for maintaining SteelEye Protection
Suite.
Data Replication - The topics in this section provide details on using data replication with SteelEye Protection
Suite.
The table below lists the default tasks that are available for each user permission. Additional tasks may beavailable for specific resource types, and these will be described in the associated resource kit
documentation.

Task

Permission
Guest

Operator

Administrator

View servers and resources

X

X

X

Connect to and disconnect from servers

X

X

X

View server properties and logs

X

X

X

Modify server properties

X

Create resource hierarchies

X

Create and delete comm paths

X

View resource properties

X

X

Modify resource properties
Take resources into and out of service

X
X

X

SteelEye Protection Suite for Windows Technical Documentation
Page 90

X

LifeKeeper GUI

Task

Permission
Guest

Operator

Administrator

Extend and unextend resource hierarchies

X

Create and delete resource dependencies

X

Delete resource hierarchiesX

LifeKeeper GUI
LifeKeeper Graphical User Interface
The GUI components should have already been installed as part of the SteelEye Protection Suite Coreinstallation.
The LifeKeeper GUI uses Java technology to provide a graphical user interface to SteelEye Protection Suiteand its configuration data. Since the LifeKeeper GUI is a client/server application, a user will run the clientcomponent to monitor or administer SteelEye Protection Suite. The client and the server components may or
may not be run on the same system.

GUI Overview
The GUI allows users working on any machine to administer, operate or monitor servers and resources in any
cluster as long as they have the required group memberships on the cluster machines. (For details, see
Configuring GUI Users.) The GUI Server and Client components are described below.

GUI Server
The GUI server is initialized on each SteelEye Protection Suite server at system startup. It communicateswith GUI clients using Hypertext Transfer Protocol (HTTP) and Remote Method Invocation (RMI).

GUI Client
The GUI client can be run either as a web client on any Java-enabled system or as an application on a
SteelEye Protection Suite server.
The client includes the following components:l

The status table on the upper left displays the high level status of connected servers and theirresources.

l

The properties panel on the upper right displays detailed information about the most recently selected
status table object.

l

The output panel on the bottom displays command output.

l

The message bar at the very bottom of the window displays processing status messages.

SteelEye Protection Suite for Windows Technical Documentation
Page 91

Starting GUI Clientsl

The context (in the properties panel) and global toolbars provide fast access to frequently-used tasks.

l

The context (popup) and global menus provide access to all tasks.

Starting GUI Clients
Starting the Web Client
To run the web client on a SteelEye Protection Suite server, click Start then point to All Programs, then point
to SteelEye->LifeKeeper->LifeKeeper. This will invoke a web browser and connect to the local GUI serverusing http://localhost:81.
On systems outside the SteelEye Protection Suite cluster, open a web browser and go to the URL
http://<server name>:81 where <server name> is the name of a SteelEye Protection Suite server. This will
load the web client from the GUI server on that machine.
After the web client has finished loading, you should see the Cluster Connect Dialog which allows you toconnect the web client to any GUI server.
Note: When you run the web client, if your system does not have the required Java Plug-in, you will be
automatically taken to the web site for downloading the plug-in. See the Java Upgrade topic for steps toupgrade. You must also set your browser security parameters to enable Java.
If you have done this and the client still is not loading, see Web Client Troubleshooting.

Starting the Application Client
Users with administrator privileges on a SteelEye Protection Suite server can run the application client fromthat server. Click Start, then point to All Programs, then SteelEye->LifeKeeper->LifeKeeper (Admin
Only).
If you have done this and the client still is not loading, see Network-Related Troubleshooting.

Exiting GUI Clients
Select Exit from the File Menu to disconnect from all servers and close the client.

Status TableThe status table provides a visual representation of the status of connected servers and their resources. Itshowslthe state of each server in the top row,l

the global (cross-server) state and the parent-child relationships of each resource in the left-mostcolumn, andlthe state of each resource on each server in the remaining cells.

The states of the servers and resources are shown using graphics, text and color. An empty table cell under aserver indicates that a particular resource has not been defined on that server.

SteelEye Protection Suite for Windows Technical Documentation
Page 92

Properties PanelIf you select a server or a resource instance in the status table, detailed state information and a contextsensitive toolbar for that item are shown in the properties panel. You can also pop up the appropriate server
context menu or resource context menu for any item by right-clicking on that cell.
The status table is split into two sections. The relative sizes of the left and right sections can be modified bymoving the divider between them. The status table can also be collapsed to show only the highest level itemsin the hierarchy trees. Collapsing or expanding resource items in the tree causes the hierarchies listed in thetable to also expand and collapse.

Properties Panel
The properties panel displays the properties of the server or resource that is selected in the status table. The
properties panel has the same functionality as the server properties dialog or the resource properties dialog
plus a context-sensitive toolbar to provide fast access to commonly used commands. The caption at the topof this panel is server_name if a server is selected, or server_name: resource_name if a resource isselected.
The context-sensitive toolbars displayed in the properties panel are the server context toolbar and theresource context toolbar. Server or resource toolbars may also be customized.
The buttons at the bottom of the properties panel function as follows.
l

The Apply button applies any changes that have been made to editable properties on the panel. Thisbutton is only enabled if you have changed an editable property.

l

The Refresh button queries the server for the current values of all properties clearing any changes thatyou may have made. This button is always enabled.

You increase or decrease the size of the properties panel by sliding the separator at the left of the panel to theleft or right. If you want to open or close this panel, use the Properties Panel checkbox on the View Menu.

Output Panel
The output panel collects output from commands issued by the GUI client. When a command begins to run, atime stamped label is added to the output panel and all of the output from that command is added under thislabel. If you are running multiple commands at the same time (typically on different servers), the output fromeach command is sent to the corresponding section making it easy to see the results of each.
You increase or decrease the size of the output panel by sliding the separator at the top of the panel up or
down. If you want to open or close this panel, use the Output Panel checkbox on the View Menu. When the
output panel is closed, the dialog that initiates each command will stay up, the output will be displayed on that
dialog until you dismiss it, and you will not be able to review the output from any command after you haveclosed that dialog. After the output panel is reopened, the GUI will return to its default behavior.

Message Bar
The message bar appears beneath the status window. It is used for displaying messages in a single text line.
Messages such as "Connecting to Server X" or "Failure to connect to Server
X" might be displayed.

SteelEye Protection Suite for Windows Technical Documentation
Page 93

ToolbarslTo hide the message bar, clear the Message Bar checkbox in the View Menu.

l

To display the message bar, select the Message Bar checkbox in the View Menu.

l

To see a history of messages displayed in the message bar, see Viewing Message History.

Toolbars
SteelEye Protection Suite for Windows Toolbars

Global Toolbar
This toolbar is a combination of the default server context toolbar and resource context toolbar which aredisplayed on the properties panel, except that you must select a server and possibly a resource when you
invoke actions from this toolbar.

Connect. Connect to a cluster.

Disconnect. Disconnect from a cluster.

Refresh. Refresh GUI.

View Logs. View log messages.

Create Resource Hierarchy. Create a resource hierarchy.

Delete Resource Hierarchy. Remove a resource hierarchy from all servers.

SteelEye Protection Suite for Windows Technical Documentation
Page 94Resource Context Toolbar

Create Comm Path. Create a communication path between servers.

Delete Comm Path. Remove communication paths from a server.

In Service. Bring a resource hierarchy into service.

Out of Service. Take a resource hierarchy out of service.

Extend Resource Hierarchy. Copy a resource hierarchy to another server for failover support.

Unextend Resource Hierarchy. Remove an extended resource hierarchy from a single server.

Add Dependency. Create a parent/child relationship between two resources.

Remove Dependency. Remove a parent/child relationship between two resources.

Resource Context Toolbar
The resource context toolbar is displayed in the properties panel when you select a server-specific resource
instance in the status table. The default toolbar is described here but this toolbar might be customized forspecific resource types in which case the custom toolbar will be described in the appropriate resource kit
documentation.
The actions are invoked for the server and the resource that you select. Actions that are not available forselection for a resource will be grayed out.

SteelEye Protection Suite for Windows Technical Documentation
Page 95

Server Context Toolbar

In Service. Bring a resource hierarchy into service.

Out of Service. Take a resource hierarchy out of service.

Extend Resource Hierarchy. Copy a resource hierarchy to another server for failover support.

Unextend Resource Hierarchy. Remove an extended resource hierarchy from a single server.

Add Dependency. Create a parent/child relationship between two resources.

Remove Dependency. Remove a parent/child relationship between two resources.

Delete Resource Hierarchy. Remove a resource hierarchy from all servers.

Server Context Toolbar
The server context toolbar is displayed in the properties panel when you select a server in the status table.
The actions are invoked for the server that you select.

SteelEye Protection Suite for Windows Technical Documentation
Page 96

Server Context Toolbar

Disconnect. Disconnect from a cluster.

Refresh. Refresh GUI.

View Logs. View log messages.

Create Resource Hierarchy. Create a resource hierarchy.

Create Comm Path. Create a communication path between servers.

Delete Comm Path. Remove communication paths from a server.

SteelEye Protection Suite for Windows Technical Documentation
Page 97

MenusMenus
SteelEye Protection Suite for Windows Menus

Resource Context Menu

The resource context menu appears when you right-click on a global (cluster-wide) resource, as shown above,or a server-specific resource instance, as shown below, in the status table. The default resource context
menu is described here, but this menu might be customized for specific resource types in which case themenu will be described in the appropriate resource kit documentation.
The actions are invoked for the resource that you select. If you select a resource instance on a specificserver, the action is invoked for that server while if you select a global (cluster-wide) resource, you will need to
select the server.
In Service. Bring a resource hierarchy into service.
Out of Service. Take a resource hierarchy out of service.
Extend Resource Hierarchy. Copy a resource hierarchy to another server for failover support.
Unextend Resource Hierarchy. Remove an extended resource hierarchy from a single server.
Add Dependency. Create a parent/child relationship between two resources.
Remove Dependency. Remove a parent/child relationship.
Delete Resource Hierarchy. Remove a resource hierarchy from all servers.

SteelEye Protection Suite for Windows Technical Documentation
Page 98

Server Context Menu

Local Recovery - Select Yes to enable Local Recovery for this Resource. Local recovery for a file sharemeans that if the folder becomes inaccessible, SteelEye Protection Suite will attempt to re-share the folder.
Quick Check Interval - Enter the interval (in minutes) between basic checks of the resource's availability.
Different values can be specified for each system. The default value is 3 minutes. The value range is
between 0 and 10080. Setting the interval value to 0 will disable the quick check feature.
Deep Check Interval - Enter the interval (in minutes) between extensive checks of the resource's availability.
This program utilizes Quickcheck for its Deepcheck implementation. Different values can be specified foreach system. The default value is 5 minutes. The valid entry range is between 0 to 10080. Setting the intervalvalue to 0 will disable the Deepcheck feature.
Properties. Display the resource properties dialog.

Server Context Menu
The server context menu appears when you right-click on a server in the status table. The actions are always
invoked on the server that you select.

View Logs. View SteelEye Protection Suite log messages.
Create Resource Hierarchy. Create a resource hierarchy.
Create Comm Path. Create a communication path between servers.
Delete Comm Path. Remove communication paths.
Disconnect. Disconnect from a cluster.
Refresh. Refresh GUI.
Properties. Display the server properties dialog.

SteelEye Protection Suite for Windows Technical Documentation
Page 99

File Menu

File Menu

Connect. Connect to a SteelEye Protection Suite cluster (requires login authentication on each server).
Exit. Disconnect from all servers and close the GUI window.

Edit Menu - ResourceThis submenu of the main menu bar is the same as the default resource context menu except that you mustselect a resource and server when you invoke actions from this menu. The Edit > Resource menu cannot be
customized.

In Service. Bring a resource hierarchy into service.
Out of Service. Take a resource hierarchy out of service.
Extend Resource Hierarchy. Copy a resource hierarchy to another server for failover support.
Unextend Resource Hierarchy. Remove an extended resource hierarchy from a single server.

SteelEye Protection Suite for Windows Technical Documentation
Page 100

Edit Menu - Server

Add Dependency. Create a parent/child relationship between two resources.
Remove Dependency. Remove a parent/child relationship.
Delete Resource Hierarchy. Remove a resource hierarchy from all servers.
Properties. Display the Resource Properties dialog.

Edit Menu - ServerThis submenu of the main menu bar is the same as the default server context menu except that you mustselect a server when you invoke actions from this menu. The Edit > Server menu cannot be customized.

View Logs. View SteelEye Protection Suite log messages.
Create Resource Hierarchy. Create a resource hierarchy.
Create Comm Path. Create a communication path between servers.
Delete Comm Path. Remove communication paths.
Disconnect. Disconnect from a cluster.
Refresh. Refresh GUI.
Properties. Display the server properties dialog.

SteelEye Protection Suite for Windows Technical Documentation
Page 101

View Menu

View Menu

Expand Tree. Expand the status table to show all resources in all hierarchies.
Collapse Tree. Collapse the status table to show only the top resource in each hierarchy.
Row Height. Modify the row viewing size of the resources in the resource hierarchy tree and table. Selectsmall, medium or large row height depending upon the number of resources displayed.
Column Width. Modify the column with viewing size of the resources in the resource hierarchy tree andtable. Select fill available space, large, medium or small depending upon the resource displayed.
Resource Labels
This option group allows you to specify whether resources are viewed in the resource hierarchy tree by
their tag name or ID.
By tag name:SteelEye Protection Suite for Windows Technical Documentation
Page 102

Help Menu

By ID:

Sort Resources by Label will sort resources by resource label only.
Group Resources by Cluster will sort by server cluster and resource label such that resources belonging inthe same cluster of servers will be grouped together.
Comm Path Redundancy Warning specifies the representation of comm path status in the server status
graphic.
l

If selected, the display will show a server warning graphic if the comm paths between a set of servers
are not configured with a redundant comm path.

l

If not selected, the display will ignore a lack of redundant comm paths between a pair of servers but will
still present server warning graphic if there are comm path failures.

Global Toolbar. Display this component if the checkbox is selected.
Message Bar. Display this component if the checkbox is selected.
Properties Panel. Display this component if the checkbox is selected.
Output Panel. Display this component if the checkbox is selected.
History. Display the newest message bar messages in the message history dialog.

Help Menu

The Help Menu provides links to the Release Notes and Technical Documentation as well as descriptionsof this documentation as follows:
Release Notes: Each product version provides Release Notes containing not only new features but also
important information such as package versions, last-minute changes to instructions and procedures, productrestrictions and troubleshooting hints and tips that were discovered through final product testing. It is

SteelEye Protection Suite for Windows Technical Documentation
Page 103

LifeKeeper GUI Server and Client Components

important that you review this document before installing and configuring your software as it contains lastminute information that must be considered before, during and after installation.
Technical Documentation: This online documentation resource is designed to provide the most up-to-date,detailed information about your SteelEye product in an easy-to-use format. SIOS Technology Corp. maintains
documentation for all supported versions of SteelEye products on this site. For older versions of products,
please request documentation from support@us.sios.com.
Select About to display the GUI version number.

LifeKeeper GUI Server and Client Components
The LifeKeeper GUI server is initialized on each SteelEye Protection Suite server at system startup. It
communicates with LifeKeeper GUI clients using Hypertext Transfer Protocol (HTTP) and Remote Method
Invocation (RMI).
You can connect to the LifeKeeper GUI server with a web client that can be run from any system that canconnect to Ports 81 and 82 of all servers in the cluster or with an application client that ships with SteelEye
Protection Suite and is designed to run on a server in the cluster.
Both SteelEye Protection Suite clients include the same graphical components:lPop-up server and resource context menus provide access to server- and resource-related actions.

l

The menu bar provides access to all LifeKeeper GUI actions.

l

The toolbar provides quick access to many SteelEye Protection Suite actions.

l

The status window displays a graphical representation of the servers connected in the cluster,
resource hierarchies and the status of resources and servers.

l

The message bar at the bottom of the window displays processing information to the user.

SteelEye Protection Suite for Windows Technical Documentation
Page 104

Running the SteelEye Protection Suite Web Client

Running the SteelEye Protection Suite Web Client
If you wish to administer SteelEye Protection Suite from a system outside your cluster, you must use the web
client. This is possible for remote systems running any operating system. SteelEye Protection Suite forWindows cannot manage both Linux and Windows servers in a single session, but it can manage either
Windows or Linux systems no matter what OS it is running on. Whichever type of server OS you first connect
to will determine the type of OS you can manage in that session. If you need to simultaneously manage bothLinux and Windows servers, you will need to open up two browser windows, one for each.
The remote system’s browser must provide JRE 1.4 or later support. Refer to the SteelEye Protection Suite
for Windows Release Notes for information on the supported platforms and browsers for the SteelEye
Protection Suite web client. The following sections explain steps for configuring the web browser on a remotesystem.
Follow the procedure below to run the SteelEye Protection Suite web client.

SteelEye Protection Suite for Windows Technical Documentation
Page 105

Configuring the Browser Security Level

1. Open the URL http://<server name>:81 for the SteelEye Protection Suite web page (where <server
name> is the name of the SteelEye Protection Suite server). The web page contains the SteelEye Protection Suite splash screen and applet.
When you run the web client for the first time, if you are using Internet Explorer and your system does
not have the required Java plug-in, you will be automatically taken to the appropriate web site fordownloading the plug-in. See the Java Upgrade topic for steps to upgrade.
Notes:l

You should close and restart your browser after installing the plug-in and whenever plugin properties are changed. Thus you will need to enter the SteelEye Protection Suite
server’s URL again as stated above.
When the web page is opened, the following actions take place:lthe splash screen is displayedlthe applet is loadedl

the Java Virtual Machine is startedlsome server files are downloadedlthe applet is initialized

Depending upon your network and system configuration, these actions may take up to 20 seconds.
Typically, browsers provide some minimal status as the applet is loading and initializing.
Note: You may receive a Java Plug-In Security Warning stating “Unable to verify the certificate - code
will be treated as unsigned.” Click OK.
Next, a Start button should appear in the applet area at the bottom of the splash screen. If the splash
screen does not display a Start button or you suspect that the applet failed to load and initialize, refer tothe GUI Network-Related Troubleshooting section in this guide.
2. Click Start. The SteelEye Protection Suite web client appears and the Cluster Connect dialog is automatically displayed. Enter the Server Name you wish to connect to followed by the login and password. Once a Server Name has been entered and connection to the cluster established, the GUI
window appears.
Note: Some browsers add “Warning: Applet Window” to windows and dialogs created by an applet.
This is normal and should be ignored.

Configuring the Browser Security Level
In order to run the SteelEye Protection Suite web client, you may need to modify your browser security
settings. Follow the procedures below.

SteelEye Protection Suite for Windows Technical Documentation
Page 106Internet Explorer

Internet Explorer
Internet Explorer will likely automatically put your SteelEye Protection Suite servers in the Local intranet
zone. If not, you should manually add all SteelEye Protection Suite servers to the Local intranet zone asfollows:
1. From the Tools menu, click Internet Options.
2. Click the Security tab.
3. Select Local intranet zone
4. Click Sites.
5. Click Advanced.
6. Enter the server name(s) and port number(s) for all SteelEye Protection Suite server(s)to which you
wish to connect (for instance: http://server1:81), clicking Add after each.
7. Click OK until you’re done.

Mozilla Firefox
1. From the Tools menu, select Options.
2. In the Options dialog box, click the Content Category.
3. Select the “Enable Java” and “Enable Java Script” options.
4. Click OK.

Running the GUI Application on a SteelEye Protection Suite
ServerYou can also run the LifeKeeper GUI as an application on a SteelEye Protection Suite server. By doing so,
you are, in effect, running the GUI client and server on the same system. Only users with administrator
privileges on the SteelEye Protection Suite server are allowed to run SteelEye Protection Suite applications.
1. Start the LifeKeeper GUI by clicking Start->AllPrograms->SteelEye->LifeKeeper->LifeKeeper(Admin only).
2. After the application is loaded, the LifeKeeper GUI appears and the Cluster Connect dialog isdisplayed. Enter the Server Name you wish to connect to followed by the login and password. See
LifeKeeper GUI User Accounts for additional information on logging in.
3. Once a connection to the cluster is established, the GUI window appears.
To run the LifeKeeper GUI on a SteelEye Protection Suite server using the web client, click Start->All
Programs-> SteelEye->LifeKeeper->LifeKeeper. This will invoke a web browser and connect to SteelEye
Protection Suite using localhost:81.

SteelEye Protection Suite for Windows Technical Documentation
Page 107

LifeKeeper GUI User Accounts

LifeKeeper GUI User Accounts
All LifeKeeper GUI users must belong to SteelEye Protection Suite security groups. The SteelEye Protection
Suite administrator for a cluster can use local groups and user accounts on each server, or you can set up
domain groups and users with local logon privileges.

Logging In
If the SteelEye Protection Suite account is the same for each server in the cluster (same login and password),then logging in to one server in the cluster will allow you to access the other servers without additional logins.
You may need to enter the domain name with the user name, for example: “Southdomain\john”.
If the SteelEye Protection Suite account is different for each server in the cluster (different login names and/or
passwords), then upon logging in to the first server in the cluster, you will receive the following message when
SteelEye Protection Suite attempts to use the login for the next server in the cluster:Access denied: invalid user name or bad password. Only users
with local privileges can use LifeKeeper. Would you like to reenter the authentication data?
Click Yes for a prompt to login to the next server.

Configuring GUI Users
There are three classes of GUI users with different permissions for each.
1. Users with Administrator permission throughout a cluster can perform all possible actions through theGUI.
2. Users with Operator permission on a server can view configuration and status information and canbring resources into service and take them out of service on that server.
3. Users with Guest permission on a server can view configuration and status information on that server.
The best practice is to always grant permissions on a cluster-wide basis. It is possible to grant permissions on
a single-server basis, but that is confusing to users and makes it impossible to perform administrative tasks.
User administration is performed by assigning users to local user groups on each server. Users assigned to
the local Administrators group have Administrator permission, users in the local LK_OPERATOR group have
Operator permission and users in the local LK_GUEST group have Guest permission. The local Administratorsgroup is built in to all Windows machines, but the other two local groups are not, so you will need to createthem.
The group names can be configured on English-language machines by editing the entries in the file Server_
RB_en.properties which can be found in the folder$LKROOT/htdoc/com/steeleye/LifeKeeper/locale. You can also localize the group names bycreating a file Server_RB_xx.properties in the same folder,where "xx" is your locale code, and editing
the entries in that file.

SteelEye Protection Suite for Windows Technical Documentation
Page 108

Common Tasks

If you are working in a Domain Controller environment with no local groups or users on your servers, you cancreate the LK_OPERATOR and LK_GUEST groups as trusted global security groups. You will then need to set
the group security policy to allow local logon to those groups.
To enable a user or a group to login locally on a Windows server, follow the instructions described below.
1. Log in to the machine using an account with local Administrator privileges.
2. Open the Local Security Policy MMC in the Administrative Tools program group.
3. Scroll down to Local Policies -> User Rights Assignment.
4. In the details pane, double-click Allow Logon Locally policy for Windows 2003.
5. Use the Add User or Group... button to add domain groups LK_OPERATOR and LK_GUEST
previously created for local login right.
IMPORTANT: Please ensure that the domain GPO does not overwrite these local policy changes.
Finally, you need to propagate these changes by executing the command SECEDIT /REFRESHPOLICYUSER_POLICY gpupdate for Windows 2003 (for more details,
see http://support.microsoft.com/?kbid=227302). Once you have done this, SteelEye Protection Suite will beable to recognize members of those groups and assign them the appropriate permissions.
Note: If you create these groups and users locally on your server, the assignments affect GUI permissions
only for that server. In that case, you should repeat the assignment on all servers in the cluster. This takes
more work but does make the cluster more robust as it is then not dependent on access to the domain
controller.

Common Tasks
This section covers basic tasks that can be performed by any user.

Connecting To A Cluster
1. From the File Menu or the Global Toolbar, select Connect.
2. In the Server Name field of the Cluster Connect Dialog, enter the name of a server within the cluster towhich you want to connect.
Note: If using an IPv6 address, this address will need to be enclosed in brackets [ ]. This will allow aconnection to be established through a machine's IPv6 address. Alternatively, a name can be assigned
to the address, and that name can then be used to connect.

SteelEye Protection Suite for Windows Technical Documentation
Page 109

Disconnecting From a Cluster

3. In the Login and Password fields, enter the login name and password of a user with SteelEye
Protection Suite authorization on the specified server.
4. Click OK.
If the GUI successfully connects to the specified server, it will continue to connect to (and add to the status
display) all known servers in the cluster until no new servers are found.
Note: If the initial login name and password fails to authenticate the client on a server in the cluster, the user is
prompted to enter another login name and password for that server. If Cancel is selected from the Password
Dialog, connection to that server is aborted and the GUI continues connecting to the rest of the cluster.

Disconnecting From a Cluster
This task disconnects your client from all servers in a cluster.
1. Select a server from which you want to disconnect and then select Disconnect from the ServerContext Menu or Server Context Toolbar.
2. A Confirmation dialog listing all servers in the cluster is displayed. Click OK in the Confirmation
dialog to confirm that you want to disconnect from all servers in the cluster.
After disconnecting from a cluster, all servers in that cluster are removed from the Status Table.

Viewing Connected Servers
The state of a server can be determined by looking at the graphic representation of the server in the GUI as
shown below. See Viewing the Status of a Server for an explanation of the server states indicated visually by
the server icon.

SteelEye Protection Suite for Windows Technical Documentation
Page 110

Viewing The Status Of A Server

Viewing The Status Of A Server
The state of a server can be determined by looking at the graphic representation of the server in the table's
header as shown below.

ServerState

VisualState

What it Means
Client has valid connection to the server.
Comm paths originating from this server to an ALIVE remote server are ALIVE.

ALIVE

Comm paths which may be marked DEAD and which target a DEAD server are
ignored because the DEAD server will be reflected in its own graphic.
Client has valid connection to the server.
One or more comm paths from this server to a given remote server are marked as
DEAD.

ALIVE

No redundant comm path exists from this server to a given remote server.
DEAD

Reported as DEAD by other servers in the cluster.

UNKNOWN

Network connection was lost. Last known SteelEye Protection Suite state is
ALIVE.

Viewing Server Log Files
To view server log files:
1. Select a server and then select View Logs from the Server Context Menu or Server Context Toolbar.
This will bring up the Log Viewer Dialog.
2. When you are finished, click OK to close the dialog.

Viewing Server Properties
To view server properties:

SteelEye Protection Suite for Windows Technical Documentation
Page 111

Viewing Resource Tags and IDsl

If the Properties Panel is enabled, simply select the server in the Status Table and the properties will
be displayed in the Properties Panel.

l

If the Properties Panel is disabled, select the server and then select Properties in the Server Context
Menu.

Viewing Resource Tags and IDs
A resource's tag and ID can be viewed quickly by positioning the cursor over a resource icon in the statuswindow and clicking the left mouse button once (single-click). The resource tag and ID of the server having
the lowest priority number are displayed in the message bar. To display the resource tag and ID for a resource
on a specific server, single-click the appropriate resource instance cell in the table.
Messages displayed in the message bar look similar to the following:
Resource Tag = F-Drive, Resource ID = F:
Under certain circumstances, the GUI may not be able to determine the resource ID in which case only the
resource tag is displayed in the message bar.

Viewing the Status of Resources
The status or state of a resource is displayed in two formats: global resource status (across all servers) andserver resource status (on a single server). The global resource status is shown in the Resource Hierarchy
Tree in the left pane of the status window. The server resource status is found in the table cell where theresource row intersects with the server column.

Server Resource Status
ServerResource
State

VisualState

What it Means

ActiveResource is operational on this server and protected (ISP)

Degraded

Resource is operational on this server but not protected by a backup
resource (ISU)StandBy

Backup resource that can take over operation from the active resource(OSU)

SteelEye Protection Suite for Windows Technical Documentation
Page 112

Global Resource Status

ServerResource
State

VisualState

What it Means

FailedProblem with resource detected on this server. For example, an attempt tobring the resource in-service failed (OSF)

Unknown

Resource has not been initialized (ILLSTATE) or SteelEye Protection
Suite is not running on this server
Empty
Panel

Server does not have the resource defined

Global Resource Status
Description

VisualState

What it Means / Causes

NormalResource is active (ISP) and all backups are active

WarningResource is active (ISP); one or more backups are marked
as unknown or failed (OSF)

FailedResource is not active on any
servers (OSF)

Resource has been taken out of service for normal reasons
Resource has stopped running by unconventional means
Recovery has not been completed or has failed

Unknown
Cannot determine state fromavailable information

More than one server is claiming to be active
Lost connection to server
All server resource instances are in an unknown state

Viewing Resource Properties
To view resource properties:l

If the Properties Panel is enabled, simply select the server-specific resource instance in the Status
Table and the properties will be displayed in the Properties Panel.

l

If the Properties Panel is disabled, select the server-specific resource instance and then selectProperties in the Resource Context Menu.

SteelEye Protection Suite for Windows Technical Documentation
Page 113

Viewing Message History

Viewing Message History
1. On the View Menu, click History. The Message History dialog is displayed (see below).
2. If you want to clear all messages from the history, click Clear.
3. Click OK to close the dialog box.
The Message History dialog displays the most recent messages from the message bar. The history list candisplay a maximum of 1000 lines. When the maximum number of lines is exceeded, the new messages will
"push out" the oldest messages.
These messages represent only the actions between the client and the server and are displayed inchronological order, the most recent messages appearing at the top of the list.

Reading the Message History<-- indicates that the message is incoming from a server and typically has a format of:<--"server name":"action"<--"server name":"app res": "action"<--"server name":"res instance":"action"--> indicates that the message is outgoing from a client and typically has a format of:-->"server name":"action"-->"server name":"app res": "action"-->"server name":"res instance":"action"
The Clear button clears the history but does not close the dialog.
The OK button closes the dialog without clearing the history.

Expanding and Collapsing A Resource Hierarchy Tree

The resource MSExch.0 is collapsed in this tree.
The resource MSExch.0 is expanded in this tree.
appears if it is collapsed.
appears to the left of a resource icon if it is expanded.

To expand a resource hierarchy,

SteelEye Protection Suite for Windows Technical Documentation
Page 114

Operator Taskslclick theorldouble-click the resource icon to the right of a.

To expand all resource hierarchies,lOn the View Menu, click Expand Tree orlDouble-click the Hierarchies button in the top left corner of the Status Table.

Note: The resource tag/ID shown in the resource hierarchy belongs to the server having the lowest priority
number. If you wish to see the tag/ID for a resource on a specific server, left-click the resource instance cell inthe table and its tag/ID will be displayed in the message bar.
To collapse a resource hierarchy,lclick theorldouble-click the resource icon to the right of a.

To collapse all resource hierarchies,lOn the View Menu, click Collapse Tree, orlDouble-click the Hierarchies button in the top left corner of the Status Table.

Operator Tasks
This section covers more advanced tasks that require Operator permission such as bringing resources in andout of service.

Bringing A Resource In Service
To bring a resource in service:
1. Select a server-specific resource instance that you want to bring in service and then select In Service
from the Resource Context Menu or Resource Context Toolbar.
2. A dialog appears confirming the server and resource(s) that you have selected to bring into service.
This dialog will include a warning if you are bringing a dependent child resource into service without
bringing its parent resource into service as well. Click In Service to bring the resource(s) into
service along with any dependent child resources.
3. If the output panel is enabled, the dialog closes and the results of the commands to bring the resource(s) in service are shown in the output panel. If not, the dialog remains up to show these results, and you
click Done to finish when all results have been displayed.
4. Errors that occur while bringing a resource in service are logged in both the LifeKeeper log and the GUIlog of the server on which you want to bring the resource into service.

SteelEye Protection Suite for Windows Technical Documentation
Page 115

Taking a Resource Out Of Service

Taking a Resource Out Of Service
To take a resource out of service:
1. Select a server-specific resource instance that you want to take out of service and then select Out ofService from the Resource Context Menu or Resource Context Toolbar.
2. A dialog appears confirming the selected resource(s) to be taken out of service. This dialog will include
a warning if you are taking a dependent child resource out of service without taking its parent resourceout of service as well. Click Out of Service to take the resources out of service.
3. If the output panel is enabled, the dialog closes and the results of the commands to take the resource(s) out of service are shown in the output panel. If not, the dialog remains up to show these results andyou click Done to finish when all results have been displayed.
4. Errors that occur while taking a resource out of service are logged in both the LifeKeeper log and the
GUI log of the server on which you want to take the resource out of service.

Taking Volume Resources In and Out Of Service
Some background processes such as virus scanners and Windows Services will try to access a sharedvolume for write access. These processes may be required to run applications and cannot be arbitrarily turned
off for long periods of time.
In most cases, these applications will have no effect on the manual switchover of SteelEye Protection Suitevolumes. However, if you see error messages similar to the following during a manual switchover (actual
failovers are not affected), you should use the Volume Remove Stop/Restart feature described below.
*ERROR* [No. 12035] Unable to lock volume <volume ID> on <system name>machine at this time as it may be in use by some application. Please
free this volume and try again.
If the volume has users doing non-write access only (remote links, local opens), removing the volume fromservice succeeds as does restoring the volume on the other system (for example, manual switchover). The
existing user "opens" are, of course, no longer valid. However, they prevent the volume from being restored toservice on the original system whether it is manually switched back over or automatically failed back over tothe original system. Attempts to do so result in the following error message:*ERROR* [No. 12046] LifeKeeper RESTORE VOLUME <volume ID> FAILED(err=<error number>).
The end result is that removing or restoring a volume, switching a volume over or back or switching any
hierarchy that includes a volume resource over or back fails if the volume has any users, local or remote.
In addition, the system’s PATH variable must not contain any file shares that exist on the volume to beprotected by SteelEye Protection Suite. File shares in the PATH variable may also cause volume operations
to fail. Remove any such shares prior to creating the volume resource in SteelEye Protection Suite. The
PATH variable may be modified by selecting System then Environment from the Windows Control Panel.

SteelEye Protection Suite for Windows Technical Documentation
Page 116

Volume Remove Stop/Restart Programs and Services

Volume Remove Stop/Restart Programs and Services
SteelEye Protection Suite provides configurable registry keys that permit the user to specify programs andservices to be stopped and restarted on a system during a volume remove operation. This feature starts andstops user specified programs and services when SteelEye Protection Suite detects open handles on any
volume that is being removed and taken out of service on that system. However, if SteelEye Protection Suite
detects no open handles on the volume being removed from service, it will not attempt to stop anything on thatsystem. Instructions for using this feature are as follows:
1. Determine which programs and services are accessing the volume in question and preventing
successful volume failovers.
2. Specify programs to stop and start by adding a subkey for each program under:l32-Bit: HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\VolumeRemoveStopPrograms\*l64-Bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SteelEye\LifeKeeper\VolumeRemoveS
topPrograms\*
For example, to stop a program called "myapp.exe", add the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\VolumeRemoveStopPrograms\myapp.exe\

3. Under the subkey for each program, add the following values (all are REG_SZvalues):
ProgramName the program name only (Note: Must match subkey name from Step 2.)
ProgramPaththe program name, including full path

Restarta value of 0 indicates that the program should not be restarted; a value of 1
indicates that the program should be restarted

StartCmdLine optional command line arguments to be used when starting the programused by SteelEye Protection Suite to save the number of instances of the programthat were running before stopping them; should be initialized to 0

WasRunning

For example, values could be entered to stop and start "myapp.exe /a /t /p" with its associatedarguments as follows:
ProgramName myapp.exe
ProgramPath

C:\mydir\myapp.exe

Restart1

StartCmdLine /a /t /p
WasRunning0

Note: By default, SteelEye Protection Suite includes a subkey for stopping perfmon.exe and the restart
option is disabled.

SteelEye Protection Suite for Windows Technical Documentation
Page 117

Volume Restore Stop/Restart Programs and Services

1. Specify services to stop and restart by adding a subkey for each service under:l

32 Bit: HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\VolumeRemoveStopServices\l

64 Bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SteelEye\LifeKeeper\VolumeRemoveS
topServices\
For example, to stop a service called "mysvc", you would add the following
subkey: HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\VolumeRemoveStopServices\
mysvc\

2. Under the subkey for each service, add the following values (all are REG_SZvalues):
ServiceName The service display name (Note: Must match subkey name from Step 4.)
RestartA value of 0 indicates that the program should not be restarted; a value of 1 indicates thatthe program should be restarted

WasRunning

Used by SteelEye Protection Suite to save the number of instances of the program thatwere running before stopping them; should be initialized to 0

StopWait

The number of seconds to wait for the service to reach the STOPPED state. If StopWait isnegative, then it (and the failover) will wait indefinitely for the service to reach the
STOPPED state

StartWait

The number of seconds to wait for the service to reach the RUNNING state. If the service
does not reach the RUNNING state in the configured period, an error is logged in the Event
Log. If StartWait is negative, then the failover will wait indefinitely for the service to start. If
it is set to 0, then the service will be started but will not wait for it to reach the RUNNING
state (and thus doesn't generate an Event Log message if the service can't be restarted)

For example, values could be entered to stop and start "mysvc" as follows:
ServiceName mysvc
Restart1

WasRunning 0
StopWait

120

StartWait

120

Volume Restore Stop/Restart Programs and Services
SteelEye Protection Suite provides configurable registry keys that permit the user to specify programs andservices to be stopped and restarted on a system during a volume restore operation. This feature is similar tothe Volume Remove Stop/Restart Programs and Services feature described above with the following
differences:

SteelEye Protection Suite for Windows Technical Documentation
Page 118

Volume Shadow Copy (VSS)ll

Programs to stop and restart are specified as subkeys under:l

32 Bit: HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\VolumeStopPrograms\l

64 Bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SteelEye\LifeKeeper\VolumeStopPrograms\

Services to stop and restart are specified as subkeys under:l

32 Bit: HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\VolumeStopServices\l

64 Bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SteelEye\LifeKeeper\VolumeStopServices\

Volume Shadow Copy (VSS)
Using Volume Shadow Copy (VSS) with DataKeeper/SteelEye Protection
Suite Volumes
On Windows 2003 and 2003 R2, VSS Shadow Copy cannot be enabled on SteelEye Protection Suiteprotected (shared or replicated) volumes. Configuring a snapshot of a protected volume, even if the snapshot
is stored on a different volume, will prevent SteelEye Protection Suite and DataKeeper from being able to lockthe volume making it impossible to protect the data on the volume.
On Windows 2008 and 2008 R2, VSS Shadow Copy can be enabled for SteelEye Protection Suite-protected(shared or replicated) volumes. However, the following guidelines apply:l

VSS snapshot images must not be stored on a SteelEye Protection Suite-protected volume.
Storing VSS snapshots on a SteelEye Protection Suite-protected volume will prevent SteelEye
Protection Suite from being able to lock the volume and switch it over to another node.

lWhen a SteelEye Protection Suite-protected volume is switched or failed over, any previous
snapshots that were taken of the SteelEye Protection Suite protected volume are discarded andcannot be reused.

l

VSS snapshot scheduling is not copied between the SteelEye Protection Suite servers. If snapshots
are scheduled to be taken twice a day on the primary server and a switchover occurs, this schedule will
not be present on the backup server and will need to be redefined on the backup server.

lThere is a slight difference in behavior when switching back to a server where snapshots werepreviously enabled:l

If the volume is a shared volume, VSS snapshots must be re-enabled.

l

If the volume is a replicated volume, VSS snapshots are automatically re-enabled.

Volume Locking for Shared SCSI Volumes
When you want to protect resources on shared SCSI disks, you partition the shared disk into logical volumes

SteelEye Protection Suite for Windows Technical Documentation
Page 119

Advanced Topics

using the Windows Disk Management tool. SteelEye Protection Suite can protect shared volumes bydefining a volume resource instance. Each instance is assigned a drive letter (for example, G:).
SteelEye Protection Suite brings the volume resource instance into service on the primary server andprovides software locks so that a backup server cannot access the volume while it is active on the primaryserver. In case of a failure of the primary server, SteelEye Protection Suite automatically brings the volume
resource into service on the backup server and locks the primary server from accessing the volume resource
when it is repaired.
SteelEye Protection Suite also automatically changes the primary and designations so that the failed server is
now locked from access to the volume resource. In this way, the resource is protected from inappropriate
access while you repair the failed server.
This dynamic redefinition of primary and backup servers is SteelEye Protection Suite’s intelligent switchback
feature that allows you to select the appropriate time to bring the resource back into service on the repaired
system.
Since SteelEye Protection Suite maintains the volume locks, do not stop SteelEye Protection Suite, as thiswould disable the locks.

Advanced Topics
This section details information on the LifeKeeper Configuration Database and LifeKeeper Communications.

LifeKeeper Configuration Database (LCD)
The LifeKeeper configuration database (LCD) maintains the object-oriented resource hierarchy informationand stores recovery direction information for all resource types known to SteelEye Protection Suite. The datais cached within system shared memory and stored in files so that configuration data is retained over system
restarts. The LCD also contains state information and specific details about resource instances required forrecovery.
See the following topics for information on the LCD directory structure, types of data stored, resource types
available and use of application scripts:l

LCD Directory StructurelDiagram of LCD Directory in $lkroot/LifeKeeperl

LCD Configuration Data

LCD Directory Structure
Major subdirectories under $LKROOT (by default, c:\LK):l

Admin. Scripts for SteelEye Protection Suite core and Recovery Kits.

l

Config. SteelEye Protection Suite configuration files, including shared equivalencies.

lBin. SteelEye Protection Suite executable programs.

SteelEye Protection Suite for Windows Technical Documentation
Page 120

Diagram of LCD DirectorylSubsys. Resources and types. SteelEye Protection Suite provides resource and type definitions in
subdirectories of Subsys. For instance, communications resources are stored in comm, volume
resources are stored in filesys, and generic application resources are stored in gen. Optional Recovery
Kits may create different resource types stored in different directories. For example, databaseapplication resources are stored in database.

lEvents. Event alarms.

lOut. LifeKeeper logs. SteelEye Protection Suite sends a variety of error and status messages toseveral different logs in this directory.

lperl. Perl binary executables and libraries.

The structure of the LCD directory in $LKROOT is shown in the topic Diagram of LCD Directory.
Note: The location of these subdirectories can be changed by modifying the value of LKROOT in theenvironment.

Diagram of LCD Directory
The following diagram shows the directory structure of \$lkroot.

SteelEye Protection Suite for Windows Technical Documentation
Page 121

LCD Configuration DataLCD Configuration Data
LCD stores the following related types of data:l

Dependency InformationlResource Status InformationlInter-Server Equivalency Information

Dependency Information
For each defined resource, SteelEye Protection Suite maintains a list of dependencies and a list of
dependents (resources depending on a resource). For more information, see the LCDI_relationship and LCDI_
instances manual pages.

Resource Status Information
LCD maintains status information in memory for each resource instance. The resource states recognized by
LCD are ISP, OSF, OSU, and ILLSTATE. Resources may change from one state to another when a system
event occurs or when an administrator takes certain actions. When a resource changes states, the statuschange is reflected in the LCD on the local server as well as in the database of the backup servers for that
resource.

Inter-Server Equivalency Information
Relationships may exist between resources on various servers. A shared equivalency is a relationshipbetween two resources on different servers that represent the same physical entity. When two servers have a
resource with a shared equivalency relationship, SteelEye Protection Suite attempts to ensure in its actions
that only one of the two servers has the resource instance in the in-service, protected [ISP] state at any one
time. Both servers can have the resource instance in an out-of-service state [OSU or OSF], but for data
integrity reasons, only one server can have the resource in service at any given time.
Disks on a Small Computer System Interface (SCSI) bus are one example of equivalent resources.
Furthermore, the dependency relationships within a hierarchy guarantee that all resources that depend upon
the volume, such as a file share, are in service on only one server at a time.

LCD Resource Types
The LCD is maintained in both shared memory and in the $LKROOT directory. As highlighted on the directory
structure diagram, subsys contains application resource sets you can use to define your application interface:lfilesys - file system related resources like volumelcomm - communications related resources like IP, volshare (fileshare) and lanmanldatabase - database resources such as Oracle

SteelEye Protection Suite for Windows Technical Documentation
Page 122

Resources Subdirectories

These subdirectories are discussed in Resources Subdirectories.

Resources Subdirectories
The filesys, comm, WebServer, database, mail and appsuite directories each contain a resources
subdirectory. The content of those directories provides a list of the resource types that are currently definedand managed by SteelEye Protection Suite:lfilesys resource types. You find these resource types in the$LKROOT\LifeKeeper\subsys\filesys\resources directory:lllcomm resource types. You find these resource types in the/$LKROOT/LifeKeeper/subsys/comm/resources directory:l

IP—created by the IP Recovery Kitl

DNS—created by the DNS Recovery Kitlvolshare—fileshare resources created by the LAN Manager Recovery Kitllanman—computer alias created by the LAN Manager Recovery Kit

WebServer resource types. You find these resource types in the$LKROOT\LifeKeeper\subsys\WebServer\resources directory:ll

IIS—created by the IIS Recovery Kit

database resource types. You find these resource types in the$LKROOT\LifeKeeper\subsys\database\resources directory:llvolume—disk partitions or virtual disk devices

Microsoft SQL Server

mail resource types. You find these resource types in the$LKROOT\LifeKeeper\subsys\mail\resources directory:

Each resource type directory contains one or more of the following:linstances. This file reflects the permanent information saved in the LCD about resource instances. It
contains descriptive information for the resource instances associated with this resource type.

lactions. This directory contains the set of recovery action programs that act only on resource
instances of the specific resource type. If, for your application, any actions apply to all resource types
within an application, place them in an actions subdirectory under the application directory rather thanunder the resource type directory.

Recovery direction software is used to modify or recover a resource instance. Two actions, remove andrestore, must exist in the actions directory for each resource type.

SteelEye Protection Suite for Windows Technical Documentation
Page 123

Resource Actions

Resource Actions
The actions directory for a resource type contains the programs (most often shell scripts) that describe
specific application functions. Two actions are required for every resource type—restore and remove.
The remove and restore programs should perform symmetrically opposite functions; that is, they undo theeffect of one another. These scripts should never be run manually. They should only be run by executing the
LifeKeeper Recovery Action and Control Interface (LRACI) perform_action shell program described in
theLRACI-perform_action man page.

LCDI Commands
SteelEye Protection Suite provides two mechanisms for defining an application resource hierarchy:l

LifeKeeper GUIl

LifeKeeper Configuration Database Interface (LCDI) commands

The LCDI is a set of interface commands provided by SteelEye Protection Suite that you can use to create
and customize resource hierarchy configurations to meet your application needs. You use the commandinterface when an application depends upon multiple resources (such as two or more file systems).
For a description of the commands, see the LCDI manual pages. This topic provides a development scenariothat demonstrates the way you can use both the GUI and command functions to create a resource hierarchy.

LifeKeeper Communications Manager (LCM)
The LifeKeeper Communication Manager (LCM) provides reliable communication between processes on one
or more SteelEye Protection Suite servers. This process can use redundant communication paths between
systems so that failure of a single communication path does not cause failure of SteelEye Protection Suite or
its protected resources. The LCM supports a variety of communication alternatives including TCP/IP andshared disk connections.
The LCM provides the following:l

SteelEye Protection Suite Heartbeat. Periodic communication with other connected SteelEye
Protection Suite systems to determine if the other systems are still functioning. SteelEye Protection
Suite can detect any total system failure that is not detected by another means by recognizing theabsence of the heartbeat signal.

lAdministration Services. The administration functions of SteelEye Protection Suite use the LCM
facilities to perform remote administration. This facility is used for single-point administration,
configuration verification and sanity checking of administrative actions.

lConfiguration and Status Communication. The LifeKeeper configuration database (LCD) tracks
resource status, availability and configuration through the LCM facilities. These facilities allow the
LCD to maintain consistent resource information between the primary and secondary systems.

lFailover Recovery. If a resource fails on a system, the LCM notifies SteelEye Protection Suite torecover the resource on a backup system.

SteelEye Protection Suite for Windows Technical Documentation
Page 124

Communication Status Information

Communication Status Information
The Communication tab of the Server Properties dialog lists the servers known to SteelEye Protection Suiteand their current state followed by information about each communication path.

Maintenance Tasks
The topics in this section cover the tasks necessary for maintaining SteelEye Protection Suite.

Starting and Stopping LifeKeeper
Because LifeKeeper is typically started automatically after installation and each time the server is booted, you
should not normally need to start/stop LifeKeeper. (The only exception is if you chose to do a Custom
installation and opted not to start LifeKeeper at that time.)
In the event that you need to start or stop LifeKeeper manually, you should do so using the Services tool
under Administrative Tasks in the Windows Control Panel.

Starting LifeKeeper
LifeKeeper consists of two services:l

LifeKeeperl

LifeKeeper External Interfaces

Generally, these two services should be stopped and started together. However, since LifeKeeper ExternalInterfaces is a dependency of the LifeKeeper service, stopping it will also stop the LifeKeeper service.
Likewise, it must be started before the LifeKeeper service can be started.
Select LifeKeeper and click Start. This will automatically start the LifeKeeper External Interfaces service.

Stopping LifeKeeper
In the Services tool, select LifeKeeper External Interfaces and click Stop. This will stop both services.
Note that the length of time that it takes to stop LifeKeeper will vary depending upon the hierarchies currently
configured although the Services tool shows the services as stopped immediately.
Using the command line to enter $LKROOT\bin\lkstop will more accurately show the services being
stopped, and it will confirm with the message "LIFEKEEPER NOW STOPPED".
Note: Stopping LifeKeeper takes all protected hierarchies out of service. This means that any protected
applications will not be accessible.

Managing IP Resources
To view configuration information associated with a protected IP resource from the LifeKeeper GUI, right-click

SteelEye Protection Suite for Windows Technical Documentation
Page 125

Managing DNS Resourceson the IP resource (on the right-hand side of the LifeKeeper GUI) and select Properties, then select the IP
Configuration tab. The example below shows the configuration details for the SteelEye Protection Suite
protected IP resource 172.17.100.118.

To enable or disable the IP address restore capabilities on the selected server while still allowing the SteelEye
Protection Suite IP resource to report a successful in-service operation, click the Modify button, then selectEnable or Disable for the restore mode. This feature applies to three-node SteelEye Protection Suite
clusters where two nodes are on a LAN (same subnet) and the third node is on a WAN (different subnet). The
restore mode of the IP resource would be enabled on the LAN nodes and disabled on the WAN node.

Managing DNS Resources
To change the Domain administrative user and password associated with a protected DNS resource from the
LifeKeeper GUI, right-click on the DNS resource (on the right-hand side of the LifeKeeper GUI) and selectProperties, then select the Resource Settings tab. Select Manage Account on the Resource Settings

SteelEye Protection Suite for Windows Technical Documentation
Page 126

Managing DNS Resources

page to change the Domain administrative user and password for your DNS resource.

Manage Account :
Field

Tips

Enter the user name of the Windows DNS/Domain administrator. This user accountshould have privileges to make changes in the DNS configuration and should be aEnter User ID
member of the "Domain Admins" group in the same domain as the DNS server. Enter(Domain\UserID)
the user ID in <DomainName>\<UserID> format where <DomainName> is the
NetBIOS name of the domain.
Enter Password

Enter the password for the account previously entered.

SteelEye Protection Suite for Windows Technical Documentation
Page 127

Displaying List of Protected File Shares

Displaying List of Protected File Shares
To display the list of file shares associated with a protected file share resource from the LifeKeeper GUI, rightclick on the File Share resource (on the right-hand side of the LifeKeeper GUI) and select Properties, thenselect the Protected Share List tab.

EditFileShareResource Utility
The EditFileShareResource utility can be used to update a file share resource with all current file shareson the associated volume(s). This can be useful in environments where there are a large number of file sharesand file shares have been added or deleted since the resource was created. Using the utility can prevent theneed to delete and re-create the file share resource.
To invoke the utility, on the command line enter:

SteelEye Protection Suite for Windows Technical Documentation
Page 128

Transferring Resource Hierarchies

EditFileShareResource <Tag name>where <Tag name> is the tag name of a file share resource that is currently in service.
The utility protects all eligible file shares defined on the protected volumes that are associated with the fileshare hierarchy. It deletes any previously protected shares that have been deleted from the system and adds
newly defined shares (meeting the eligibility criteria) to the list. It will also update the file share permissions
defined on the file share.

Transferring Resource Hierarchies
When you need to perform routine maintenance or other tasks on a SteelEye Protection Suite Server, you can
use the LifeKeeper GUI to move in-service resources to another server. To transfer in-service resource
hierarchies from Server A to Server B, use the GUI to bring the hierarchies into service on Server B. Repeat
until all of Server A’s resources have been placed in-service on their respective backup servers. See Bringing
a Resource In Service for instructions.
When all of Server A’s resources are active on their backup server(s), you can shut down Server A without
affecting application processing. For the maintenance period, however, the resources may not have SteelEye
Protection Suite protection depending on the number of servers in the cluster.

Performing Offline Maintenance On A Shared Disk
When performing offline maintenance on a shared SCSI host adapter or a disk on a shared bus, you must stop
LifeKeeper and power down all servers and shared disks. Perform these actions in the following order:
1. Stop LifeKeeper. Use the Services tool to stop the LifeKeeper and LifeKeeper External Interfaces
services on each SteelEye Protection Suite server. Your resources are now unprotected.
2. Shut down Windows. Shut down the Windows operating system on all servers in the cluster.
3. Power down all servers.
4. Power OFF all shared disks.
5. Perform maintenance. Perform the necessary maintenance on the shared SCSI host adapter orshared disk.
6. Power ON all shared disks.
7. Power ON all servers, one at a time. Let each server boot the Windows operating systemcompletely before powering on the next server.
8. Start LifeKeeper. Log on as administrator, then use the Services tool to start the LifeKeeper and
LifeKeeper External Interfaces services on each SteelEye Protection Suite server. SteelEye
Protection Suite automatically mounts all shared file systems and restarts and brings into service all
databases on shared disks.

Maintaining a SteelEye Protection Suite Protected System
When performing shutdown and maintenance on a SteelEye Protection Suite-protected server, you must put

SteelEye Protection Suite for Windows Technical Documentation
Page 129

Configuring Generic Application Scriptsthat system’s resource hierarchies in-service on the backup server before performing maintenance. This
process stops all activity for shared disks on the system needing maintenance. For off-line maintenance of ashared disk, see Off-Line Maintenance of a Shared Disk.
Perform these actions in the order specified where Server A is the primary system in need of maintenance andServer B is the backup server:
1. Bring hierarchies in-service on Server B. On the backup, Server B, use the LifeKeeper GUI to bringin-service any resource hierarchies that are currently in-service on Server A. This will unmount any filesystems currently mounted on Server A that reside on the shared disks under SteelEye Protection
Suite protection. See Bringing a Resource In Service for instructions.
2. Stop LifeKeeper on Server A. In the Services tool, select LifeKeeper External Interfaces and click
Stop. This will stop both services. Your resources are now unprotected.
3. Shut down Server A. Shut down the Windows operating system on Server A, then power off theserver.
4. Perform maintenance. Perform the necessary maintenance on Server A.
5. Power on Server A. Power on Server A and bring up the Windows operating system.
6. Bring hierarchies back in-service on Server A, if desired. On Server A, use the LifeKeeper GUI to
bring in-service all resource hierarchies that were switched over to Server B.

Configuring Generic Application Scripts
Use this feature to update a script that has been created to protect an application that has no associatedSteelEye Protection Suite Recovery Kit.
1. Right-click on the generic application resource and select Properties. Select the SteelEye Protection
Suite Generic Application Configuration tab.

SteelEye Protection Suite for Windows Technical Documentation
Page 130

Configuring Generic Application Scripts

2. Select the Script Update button. Use the following table to complete the fields in the Generic
Application Configuration procedure.

SteelEye Protection Suite for Windows Technical Documentation
Page 131

Configuring Generic Application Scripts

Field

Tips
Select the SteelEye Protection Suite action name for the resource that will be
updated. Select:

Select the
Action Script toUpdatelrestore to update the script responsible for in-service operations.

lremove to update the script responsible for out-of-service operations.

lquickCheck to update the script responsible for monitoring the application.

ldeepCheck to update the script that performs in-depth monitoring of theapplication.

lrecover to update the script responsible for resource recover operations.

ldelete to update the script that performs any additional actions required toremove the application from SteelEye Protection Suite protection.

lextend to update the script responsible for additional actions required toprepare the application for protection with SteelEye Protection Suite on thetarget server(s)Enter the pathname for the shell script or object program for the application.

Full Path to
New Scriptl

The restore script is responsible for bringing a protected application
resource in-service. (Required)l

The remove script is responsible for bringing a protected application
resource out-of-service. (Required)l

The quickCheck script is responsible for monitoring a protected
application resource after a failure event.

l

A copy of this script or program will be saved by SteelEye Protection Suitein the resource hierarchy on the server.

lThere may be a short wait while SteelEye Protection Suite validates thepathname to remove monitoring or recovery.

l

Do not specify a shell script or object program.

lValid characters allowed in the script pathname are letters, digits and thefollowing special characters: - _ ! . /3. The Basic File Statistics dialog displays old and new configuration information about the current
script. Click Continue.
4. The Update All Systems dialog displays. Select Yes to update all systems in this cluster. Select No
to only update the current system. If you choose No, you must separately update the corresponding
script for the configuration on the backup servers. Click Next.
5. Click Done to complete.

SteelEye Protection Suite for Windows Technical Documentation
Page 132

Maintaining a Resource Hierarchy

Maintaining a Resource Hierarchy
You can perform maintenance on a resource hierarchy while maintaining SteelEye Protection Suite protectionof all other hierarchies on the system. This involves taking the hierarchy in need of maintenance out of service
and then bringing it back in service after you complete the maintenance tasks.
To perform maintenance on a resource hierarchy:
1. Take the hierarchy out of service. Use the LifeKeeper GUI to take as much of the resource hierarchyout of service as you need to perform the maintenance. See Taking a Resource Out of Service for
instructions.
2. Perform maintenance. Perform the necessary maintenance on the resource hierarchy.
3. Restore the hierarchy. Use the LifeKeeper GUI to bring the resource hierarchy back in service. See
Bringing a Resource In Service for instructions.

Recovering After a Failover
After SteelEye Protection Suite performs a failover recovery from a primary server (ServerA) to a backup
server (Server B), perform the following steps:
1. Monitor failover. When SteelEye Protection Suite on Server B performs a failover recovery from
Server A, status messages are displayed during the failover ending with the following message:

FAILOVER RECOVERY OF MACHINE Server A
FINISHED AT: date time year
The exact output depends upon the configuration. Some messages on failure to mount or unmount are
expected and do not suggest failure of recovery. These messages as well as any errors that occur
while bringing the resource in-service on Server B are logged in the LifeKeeper log.
2. Perform maintenance. Determine and fix the cause of the failure on Server A. Server A may need to
be powered down to perform maintenance.
3. Reboot Server A, if necessary. Once maintenance is complete, reboot Server A if necessary.
4. Start LifeKeeper, if necessary. If LifeKeeper is not running on Server A, go to the Windows
Services tool, select LifeKeeper and click Start. This will automatically start the LifeKeeper
External Interfaces service.
5. Move application back to Server A. At a convenient time, use the LifeKeeper GUI to bring theapplication back into service on Server A. See Bringing a Resource In Service for instructions. Notethat this step may be unnecessary if the application on Server A was configured for Automatic
Switchback.

SteelEye Protection Suite for Windows Technical Documentation
Page 133

Chapter 5: Uninstalling SteelEye Protection Suite for Windows

Chapter 5: Uninstalling SteelEye Protection Suite forWindows
Before Removing LifeKeeper
Included below are the requirements for removing LifeKeeper software.
1. Move or stop applications. Before removing the software, verify that applications requiring SteelEye
Protection Suite protection are not on the server. Never remove LifeKeeper from a server where anapplication resource hierarchy is in service. Removing LifeKeeper removes all configuration data, suchas equivalencies, resource hierarchy definitions and log files. See Transferring Resource Hierarchies
for additional information.
2. Ensure LifeKeeper is running. Recovery Kits may require LifeKeeper to be running when you
remove the recovery kit software. Use the Services MMC snap-in to ensure that LifeKeeper services
are running. If it is not running, the removal process cannot remove the resource instances from other
SteelEye Protection Suite servers in the cluster which would leave the servers in an inconsistent state.
3. Remove resource hierarchies. Unextend or delete any resource hierarchies from the server where
LifeKeeper will be removed. Never remove a Recovery Kit from a server where the resource hierarchy
is in service. This will corrupt current hierarchies and they will need to be recreated when reinstalling
the Recovery Kit.
4. Remove all packages. If removing the LifeKeeper core, first remove other packages that depend upon
LifeKeeper; for example, SteelEye Protection Suite Recovery Kits. It is recommended that before
removing a SteelEye Protection Suite Recovery Kit, first remove the associated application resource
hierarchy.

Before Removing DataKeeper
If planning to uninstall DataKeeper and reinstall a previous version, all jobs/mirrors must be deleted on eachnode prior to uninstalling. These will need to be recreated once software is reinstalled.

Uninstall SteelEye Protection Suitel

In Windows Control Panel, find your list of installed programs and select SteelEye DataKeeper or
LifeKeeper.

lSelect Uninstall.

Once the uninstall process is complete, rebooting the system is required.
Note: Uninstalling automatically stops the SteelEye DataKeeper and/or LifeKeeper services and clears theregistry entries.
Once removed, the following files will not be removed by the uninstall procedure.

SteelEye Protection Suite for Windows Technical Documentation
Page 134

NotesPath and File Name<windows dir>/System32/LKLicenseor<windows dir>/SysWOW64)/LKLicense

Definition and Special
Considerations
Common license file directory for SIOS
Technology Corp. products. This is where
license files are installed and licenses for
multiple SIOS Technology Corp. products may
be installed here at any given time. We don't
remove this at uninstall so as to not disturb the
installed licenses.
Safe to remove manually, but the license willneed to be reinstalled if the software is
reinstalled at a later time.

or

A backup file created by Windows when new
performance monitor counters are installed.
This is created when we install the perfmon
counters.

<windows dir>/SysWOW64)/PerfStringBackup.ini

This should probably be left alone since it is afile created by Windows itself.

<windows
dir>/System32/PerfStringBackup.ini

This file describes the DataKeeper<windows
performance monitor counters. This file can bedir>/inf/ExtMirr/0011/ExtMirrCounters.ini
removed or left alone. It is not an executable.

Notes
l

Important: Uninstallation of SteelEye Protection Suite software requires that the Microsoft Visual C++
2008 Redistributable package be installed. Do not remove this package until SteelEye Protection
Suite has been uninstalled.

lModify or Repair must be run from the SteelEye Protection Suite setup program.

lRemoval of LifeKeeper does NOT remove SUperior SU. SUperior SU can be removed separately
using Add/Remove Programs.

lRemoval of SteelEye Protection Suite may NOT delete the SteelEye Protection Suite directory. This
directory can be deleted manually after the Add/Remove operation is complete.

l

A reboot of the system is required to completely remove SteelEye Protection Suite remnants.

Data Replication
The topics in this section provide details on using data replication with SteelEye Protection Suite.

Monitoring Replicated Volume Resources
The state of all SteelEye Protection Suite protected replicated volume resources is displayed in the

SteelEye Protection Suite for Windows Technical Documentation
Page 135

Monitoring Replicated Volume Resources

LifeKeeper GUI. Refer to the SteelEye DataKeeper topic, Mirror State Definitions, for details on mirror states.
The example below shows that the mirror state of the replicated volume resource Vol.L is Resync and that themirror state of the replicated volume resource Vol.Y is Mirroring.

The table below describes the different states for replicated volume resources and their meaning.

Resource
State

VisualState

What it Means

ActiveResource is operational on the primary server and protected (ISP)

Degraded

Resource is operational on the primary server but not protected by a backup
resource (ISU)Unknown

Resource has not been initialized (ILLSTATE) or SteelEye Protection Suite is
not running on this server.

FailedProblem with resource detected on this server. For example, an attempt to bring
the resource in-service failed. (OSF)

OfflineResource is out of service on this server. Volume is not accessible forread/write operations.

ResyncPendingResource state on the backup server is Resync Pending.

SteelEye Protection Suite for Windows Technical Documentation
Page 136

Monitoring Replicated Volume Resources

Resource
State

VisualState

What it Means

Mirroring

Resource state on the backup server is Mirroring.

PausedResource state on the backup server is Paused.

ResyncResource state on the backup server is Resync.

BrokenResource state on the backup server is Broken.

To view the configuration information for a replicated volume resource from the LifeKeeper GUI, right-click on
the volume resource and select Properties, then select the SDR Status tab. The example below shows
Vol.L is the source on Cardinal and has one target - 10.10.1.2, and that it is resycning to the target Bluejay.

SteelEye Protection Suite for Windows Technical Documentation
Page 137

Replication Settings

Replication Settings
From the Volume Resource Properties page, select the Replication Settings button to set thecompression level, the network throttling or the SteelEye Protection Suite Delete Mirror flag for a replicatedvolume.

Field
SelectTargets

Tips
Select the target server to which the action should be applied.

SteelEye Protection Suite for Windows Technical Documentation
Page 138

Performing Actions on Replicated Volumes

Field

Tips
Specify the compression level for the selected replicated volume.

Valid values are 0 to 9. Level 0 is "no compression". Values from1 to 9 specify increasingly
CPU-intensive levels of compression. Compression level 1 is a "fast" compression - it doesSet
not require as much CPU time to compress the data but results in larger (less compressed)
Compression network packets. Level 9 is the maximum amount of compression - it results in the smallest
Level
network packets but requires the most CPU time. The level can be set to somewhere in
between to balance CPU usage and network efficiency based on your system, network andworkload.
Default is 0.
Set Network
Throttling

The Bandwidth Throttle setting (specified in kilobits per second) limits the amount of
network bandwidth that the replicated volume can use for resync and normal volume writes.
Default is 0.
The SteelEye Protection Suite Delete Mirror Flag controls the behavior during delete of theSteelEye Protection Suite resource for the replicated volume. When deleting the SteelEye
Protection Suite volume resource, if the flag is set to True, then SteelEye Protection Suite
will delete the mirror; otherwise, the mirror will remain.

Set SteelEye
Protection
Select True if you want the mirror deleted when the volume resource is unextended orSuite Delete removed from SteelEye Protection Suite.
Mirror Flag
Select False if you want the mirror to remain intact.
Default is True if mirror is created using LifeKeeper GUI. Default is False if mirror iscreated outside of LifeKeeper GUI.

Performing Actions on Replicated Volumes
To perform actions on a replicated volume resource using the LifeKeeper GUI, right-click on the replicatedvolume resource and select the action you wish to perform from the context menu. If you have the Properties
Panel enabled (View->Properties Panel), the resource toolbar will be displayed for the selected volume.

ActionIcon

Meaning

Select Target

Select the target system to which the action should be applied.

Pause Mirror

Select Pause Mirror to temporarily stop the data from being mirrored. A partial
resync will be performed when you click Continue to un-pause the mirror. After
pausing a mirror, it is possible to unlock the target volume using the Unlock
Target action.

SteelEye Protection Suite for Windows Technical Documentation
Page 139

What is Split-Brain

ActionContinue
Mirror/Lock
Target

Icon

Meaning
To continue a mirror after the mirror has been paused, select theContinue/Lock Target action. This un-pauses the mirror, re-locks the target
volume (if unlocked) and resumes the mirroring process.
While pause temporarily stops the writes from being mirrored, the writes arerecorded during the pause interval. When the mirror is resumed, the recorded
writes are sent to the target volume and the mirror is automatically resynchronized (partial resync).
To unlock the target volume of a mirror, select the Unlock Target action. Thispauses the mirror (if not already paused) and unlocks the mirrored volume on thetarget system. This allows read/write access to the data on the volume.

UnlockTargetContinue Mirror will relock the target volume, perform a partial resync andresume the mirroring process.
Warning: Do not write to the target volume while the mirror is unlocked! Any
writes to the target while the mirror is unlocked will be lost when the mirror is resynchronized.

Break
Mirror/Unlock
TargetBreaking a mirror discontinues the mirror for the selected volumes and unlocks
the target volume but does not remove the mirror from the volume list. A full
resync must be performed in order to re-establish the mirror after a Break
Mirror/Unlock Target action.
Warning: Do not write to the target volume while the mirror is broken! Any
writes to the target while the mirror is broken will be lost when the mirror is resynchronized.

ResyncMirror/Lock
TargetTo re-establish a broken mirror, select Resync Mirror/Lock Target action. A
full resync will be performed.

RewindTargetVolumeThis wizard rewinds the data on the target system until you reach a good data
set and then walks you through the recovery process.

Add Rewind
Log
Bookmark

This wizard guides you through the process of viewing bookmarks and adding
bookmarks to the rewind log. Bookmarks are useful for keeping track ofimportant system events (such as upgrades) in case a rewind needs to be
performed. When you perform a rewind, all bookmarked log entries will be
displayed as choices for the rewind point.

What is Split-Brain
When all of SteelEye Protection Suite's comm paths are disconnected and if Automatic Node Failover isenabled, each side of SteelEye Protection Suite assumes that the other side is dead and attempts to bring all
the resources in service. In the case of a SteelEye DataKeeper resource, both sides become mirror sources
and allow data to be written to the volume. This condition is defined as "split-brain" and will be indicated in the

SteelEye Protection Suite for Windows Technical Documentation
Page 140

What is Split-Brain

LifeKeeper GUI with the following icon:

Refer to the topic Split-Brain Recovery for the steps required to resolve this situation.

The Properties Panel for the selected volume displays additional information about the split-brain condition
and instructions for resolving this problem.

SteelEye Protection Suite for Windows Technical Documentation
Page 141

Split-Brain Recovery

Split-Brain Recovery
After the system's comm paths have been restored and the servers detect that the volumes are in the SplitBrain state, you will have to perform the Split-Brain Recovery procedure below.
Note: If multiple volumes are detected in different resource hierarchies, you will have to perform the SplitBrain Recovery procedure on each volume. Split-Brain volumes that are in the same hierarchy will berecovered together.
1. Right-click on the volume instance icon under the system that will be the source. The Resource
Context menu displays. You can also right-click on the volume instance icon in the Hierarchies list in
the far left panel. Choose Split-Brain Recovery from the menu, and you will be prompted to selectwhich server should be the mirror source.
2. Select Split-Brain Recovery from the menu.

SteelEye Protection Suite for Windows Technical Documentation
Page 142

Split-Brain Recovery

3. The following warning message will display. Select the Continue button to complete the Split-Brain
Recovery process. Note: During this procedure, all other systems that are in the split-brain condition
will be rebooted and will become the mirror target when they complete the rebooting process.

SteelEye Protection Suite for Windows Technical Documentation
Page 143

Split-Brain Recovery

4. The following message will display as the Split-Brain Recovery process proceeds. There will be adelay while the remote systems are rebooted. Select Finish to complete.

SteelEye Protection Suite for Windows Technical Documentation
Page 144

Data Rewind Overview

5. Once the recovery is complete, the recovered resources will appear in the GUI as follows. The SplitBrain Recovery process will be completed when the target system has rebooted and the mirror will be
re-synced.

Data Rewind Overview
Data Rewind allows administrators to change the contents of a replicated volume to any point in time using
rewind and advance operations. This capability is made possible through the Rewind Log which records alldata changes that occur on the volume. As long as a timestamp is contained in the Rewind Log, the volume
can be rewound to that point in time and can then be rewound further back in time or advanced forward in time.
The Rewind Log is created and maintained on a mirror Target system. All rewind and advance operations are
performed on the Target to ensure minimal impact on the Source (primary) server. By default, rewind isdisabled on all replicated volume resources. From the Volume Resource Properties page, select the
Rewind Settings button to enable rewind for the selected replicated volume resource.

SteelEye Protection Suite for Windows Technical Documentation
Page 145

Rewind Settings

For optimal performance, the rewind log file should be on a separate physical disk. It is also recommended
that write caching be enabled for the physical disk where the log is located and for the physical disk where thereplicated data is located. To enable write caching, go to My Computer ->right-click Volume -> Properties-> Hardware tab -> Properties ->Policies tab -> Enable write caching on the disk.
If the Rewind Log file is to be stored at a different location than the default, this change must be made prior toenabling rewind for the selected replicated volume resource. From the Volume Resource Properties page,
select the Rewind Settings button to change the location of the rewind log for the selected replicated volume
resource.
To save space on your rewind log disk, you can choose to enable NTFS compression for the rewind log file.
NTFS compression must be enabled prior to enabling rewind for the selected replicated volume
resource. From the Volume Resource Properties page, select the Rewind Settings button to enable NTFS
compression for the rewind log file.
After performing rewind/advance operations and locating good data, there is one recovery option available:lManually copy data to the Source (primary) server from the Target (backup) server. After manual copy
is complete, a partial resync to the Target will be performed.

Note: If Rewind is enabled and the DataKeeper Service is not running, a RewindDump file is created. Oncethe DataKeeper service starts, this RewindDump file is processed and removed, and the actual Rewind
Log file is created. If you no longer want Rewind enabled on a particular volume, disable Rewind on thatvolume and then manually remove the RewindDump file.

Rewind Settings
From the Volume Resource Properties page, select the Rewind Settings button for enabling/disabling
rewind, changing the rewind log location, associating volumes that should be rewound at the same time (as asingle entity), setting the maximum age limit for the log file or setting NTFS compression for the selected
replicated volume resource.

Field
Enable /DisableRewindRewindLogfileLocation

Tips
Specifies whether to enable or disable rewind for the selected volume resource.
Rewind is disabled by default.
Specifies the folder where the rewind log file for this volume should be stored. The folder
must not be on any volume that is part of a mirror or that is protected by SteelEye Protection
Suite - it must be on a volume that is writable whenever this volume is a mirror Target.
Default is %extmirrbase%\RewindLogs.
Note: The location of the log file must be changed prior to enabling rewind.

SteelEye Protection Suite for Windows Technical Documentation
Page 146

Performing Rewind on Replicated Volume Resources

Field

Tips
Specifies whether the rewind log file should be created using NTFS compression.

Compressed Select True to compress the logfile.
LogfileDefault is False.
Note: The compress log file option must be set prior to enabling rewind.
Specifies which volumes should be rewound at the same time as a single entity. Associatedvolumes are specified in comma separated groups. For example, if you have two
applications, one that relies on both the D: and E: volumes and another which relies on the
P: and Q: volumes, then enter: DE,PQ.
AssociatedVolumes

Max Logfile
Size

Note: In most cases, it is not necessary to change this setting. As long as your SteelEye
Protection Suite hierarchies contain the necessary volume resources that your applications
depend on (which is normally the case), the rewind procedure will automatically associate
those volumes when performing a rewind. You only need to override the default behavior if
you have special volume associations that cannot be determined automatically by looking at
the SteelEye Protection Suite resource hierarchies.
Specifies the maximum size, in MB, that this volume's rewind log will be allowed to grow to.
A value of 0 specifies unlimited file size.
Default is 0.

Max Logfile
Age

Specifies the maximum number of minutes of data to be stored in the rewind log. A value of 0
specifies unlimited age.
Default is 0.

Specifies the minimum amount of space in megabytes that should be reserved on the
Min Log
Volume Free Rewind log file volume to avoid filling up the volume and running out of space.
Space
Default is 100MB.
Note: If Rewind is enabled and the DataKeeper Service is not running, a RewindDump file is created. Oncethe DataKeeper service starts, this RewindDump file is processed and removed, and the actual Rewind
Log file is created. If you no longer want Rewind enabled on a particular volume, disable Rewind on thatvolume and then manually remove the RewindDump file.

Performing Rewind on Replicated Volume Resources
To perform a rewind operation on a replicated volume resource using the LifeKeeper GUI, right-click on thereplicated volume resource and select Rewind Target Volume from the context menu. If you have theProperties panel enabled (View->Properties Panel), select the target of replicated volume resource to be
rewound and click onon the resource toolbar. This will start the rewind operation.

The displayed Warning message will show the volume or volumes that will be rewound during the rewind
operation. The target volume(s) will be paused and unlocked as part of the rewind operation. During the timethat the mirrors are paused, the target server will not be eligible to provide SteelEye Protection Suite recovery

SteelEye Protection Suite for Windows Technical Documentation
Page 147

Performing Rewind on Replicated Volume Resources

for the volumes. While data is being rewound on the target, all changes to the source will be tracked andwritten to the target by performing a Continue Mirror action. Click on Continue to proceed with the rewind
operation or Cancel to exit the rewind operation. The table below shows the information that is required toperform the rewind operation.

Field

Tips

Stop allapplications
Select Yes if you want SteelEye Protection Suite to stop all applications running on theonprimary <Source> server that are using volumes specified by <driveletter(s)> as part of their<Source>SteelEye Protection Suite hierarchy. Select No to leave applications running on the primarythat are<Source> server.
using
volumes
Default is No.
<driverletter(s)>?
Prepare to
Rewind andRecover
After SteelEye Protection Suite completes the process of preparing the volume(s) identified
data forby <volume tag> for rewind, click on Next to continue the rewind operation.
<volumetag>on<target>
Choose a rewind timestamp from the list provided or type in the start time you want to use.
There are many date and time formats accepted for this value including:
5/4/07 08:27
April 29 23:00
Specify
RewindPointlast Saturday 13:21
yesterday 08:23:17
The time string that you enter will be validated before being used. The progress bar at thebottom of the dialog indicates the state of the data in the rewind log as it is currently known.
At the beginning of the rewind process, all data is unknown. As the data is rewound andadvanced to various points in time, sections of the data are marked as good or bad dependingon your test results with the various data sets.

PerformrewindSteelEye Protection Suite is now rewinding the data on the target server to the rewind point
specified from above. Click Next to continue with the rewind operation.

Pleaseenter yourcomments
Evaluate the test results and enter any comments here. Comments will be stored andon the test
displayed in the list of Rewind Points to help you locate good data.
results;
Comments
are optional

SteelEye Protection Suite for Windows Technical Documentation
Page 148

Performing Rewind on Replicated Volume Resources

Field

Tips

Is the data
valid?

Indicate whether the volume contents are now valid. The answer you provide will be used toconstruct the list of timestamps that you are given for future rewind/advance operations.
SteelEye Protection Suite tries to guide you to the latest known good data by limiting the startand end timestamps that are listed based on your answers to this question. If you choose
Yes, you will not be given any choices that are earlier than the current selected timestamp. If
you choose No, you will not be given any choices that are later than the current timestamp. If
you are unsure whether the data is valid, choose Not Sure and the rewind points that you see
will not be limited.

Processing
result for
Storing evaluation and comments and adjusting Rewind Points interval. Click Next torewind time continue with the rewind operation.
below
Proceedwithrecovery or
try a
different
data set.

You may choose to rewind or advance to a different timestamp or may stop rewinding anduse the current state of the volume(s) for recovery. The progress bar at the bottom of the
dialog indicates the state of the data in the rewind log as it is currently known. At the
beginning of the rewind process, all data is unknown. As the data is rewound and advanced tovarious points in time, sections of the data are marked as good or bad depending on your test
Select Next results with the various data sets.
ActionData
RecoveryTo recover lost or corrupt data, you can leave applications running on the Source (primary)server or stop them as necessary. Manually copy any missing or corrupt data from therewound Target (backup) server to the Source (primary) server. After copying has been
completed, click on Next. The rewound volumes will be re-locked and the mirrors continued.
This completes the rewind operation and data recovery operation.

SteelEye Protection Suite for Windows Technical Documentation
Page 149

Chapter 6: DataKeeper
For complete information on SteelEye DataKeeper for Windows, see the DataKeeper for Windows TechnicalDocumentation located within the SteelEye Protection Suite for Windows online documentation on the
SIOS Technical Documentation site:l

http://docs.us.sios.com/#SPS4W

SteelEye Protection Suite for Windows Technical Documentation
Page 150

Chapter 7: Troubleshooting
The topics in this section contain important information about known issues and restrictions offering possible
workarounds and/or solutions.

Applet Troubleshooting
Description
If the web client does not display the Cluster Connect dialog, try the following:
1. Check whether the applet failed. Usually a message is printed somewhere in the browser window
specifying the state of the applet. In Internet Explorer, an icon may appear instead of the applet, in
addition to some text status. Clicking this icon may bring up a description of the failure.
2. Open the Java Console.
l

For FireFox and older versions of Internet Explorer, run the Java Plug-In applet fromyour machine's Control Panel and select the option to show the console, then restart
your browser.

l

For recent versions of Internet Explorer, select Tools > Sun Java Console. If you do
not see the Sun Java Console menu item, select Tools >Manage Add-Ons and enable
the console, after which you may need to restart your browser before the console willappear.

l

For Mozilla, select Tools > Web Development > Sun Java Console.

3. If the web client is not open, reopen the URL http://<server name>:81 to start it.
4. Check the console for any messages. The messages should help you resolve the problem. If the
problem appears to be network related, refer to the Network-Related Troubleshooting section.

SteelEye Protection Suite for Windows Technical Documentation
Page 151

CYGWIN Crash on Win2008 May Occur When LifeKeeper StoppingCYGWIN Crash on Win2008 May Occur When LifeKeeper
Stopping
SymptomCYGWIN crash on Win2008 (e.g. GREP segmentation fault) may occur when LifeKeeper is stopping.
With Terminal Service enabled as well as Data Execution Prevention enabled for the application, there is abug in Win2008 in tsappcmp.dll which occasionally causes the crash to happen.

Solution
There is a page of memory whose protection level gets changed by tsappcmp.dll, and the "EXECUTE"
permissions on that page get removed for some unknown reason. The page contains executable code andshould be able to be executed, but since the permission was modified, an exception occurs and the programcrashes.
See the following articles for additional information and a workaround solution.
http://www.eggheadcafe.com/software/aspnet/33380656/corinnayou-wrote-that-th.aspx
http://www.mail-archive.com/cygwin@cygwin.com/msg91569.html

Error When Attempting to Run SteelEye Protection Suite
Command From Command Prompt
Symptom
When attempting to run a SteelEye Protection Suite command from a command prompt, you receive thefollowing error:[File:lock.CLine:1610] Win32 Error: 2*CRITICAL* (No. 472) Can’t run this application without LCD Daemon
running.

Solution
SteelEye Protection Suite commands require “console” rights to run. If using Remote Desktop, invoke
Remote Desktop with the “/console” switch when the SteelEye Protection Suite core is running on Server
2003. When the SteelEye Protection Suite core is running on Server 2008 or later, invoke Remote Desktop
connections with the “/admin” switch.
e.g. %SystemRoot%\system32\mstsc.exe/console
You may also run the SteelEye Protection Suite command from the command prompt on the SteelEye
Protection Suite system itself.

SteelEye Protection Suite for Windows Technical Documentation
Page 152

Firewall

Firewall
Symptom
Firewall was disabled during installation but is now enabled. How do I add the rules to Windows firewall?

Solution
There is a script in the LifeKeeper directory that will allow you to enable the firewall rules. The script is locatedin:<LifeKeeper Root Directory>\support\firewallsetup.bat
By opening a command prompt and executing firewallsetup.bat <LifeKeeper Root
directory>, you can add the rules. If the rules had been added, the script will not add duplicate rules.
If you open the Windows firewall (wf.msc), you will see the inbound rules prefixed with the LifeKeeper label.
Note: If you have created specific rules that have disabled the ports required by SteelEye Protection Suite,
the installation program will disable but will not delete those rules.

GUI Error Messages
Description
Error 101: Illegal argument was passed.
Error 102: This program requires a Java Virtual Machine Version 1.5 or greater to run properly. Please refer tothe LifeKeeper GUI documentation to verify your setup.
Error 103: Could not set Look and Feel for LifeKeeper GUI.
Error 104: <filename> Image could not be loaded.
Error 106: Error trying to get data over RMI. Could not complete action.
Error 107: Failed to create Global Resource Instance.
Error 108: Failed to create Global Resource.
Error 109: Dialog requires a Server to be selected.
Error 112: Could not match Resource Instance to Global Equivalency.
Error 114: <server name> Security Exception caused connection failure to this server. Please note that thisfailure may result in degraded cluster resource rendering. Verify that your Java Policy file is installed properly.
See Running the SteelEye Protection Suite Web Client.

SteelEye Protection Suite for Windows Technical Documentation
Page 153

Description

Error 115: <server name> Name of this server could not be resolved resulting in a connection failure to thisserver. Please note that this failure may result in degraded cluster resource rendering. Please refer tothe LifeKeeper GUI documentation to verify network naming conventions. See Unknown Host Exception.
Error 116: <server name> This server could not resolve the name of this client host resulting in a connection
failure to this server. Please note that this failure may result in degraded cluster resource rendering. Pleaserefer to the LifeKeeper GUI documentation to verify network naming conventions. See Unknown Host
Exception.
Error 117: Initial connection to server failed. LifeKeeper GUI will continue trying to connect. Please refer tothe LifeKeeper GUI documentation to verify that SteelEye Protection Suite and the LifeKeeper GUI server are
active on this system. See Java RMI Binding Problem.
Error 118: Incompatible client and server packages caused connection failure. Please verify that the versions
are compatible between the target server and the server from which the client was started.
Error 119: Could not export remote object.
Error 120: Encountered exception when invoking remote method.
Error 121: Administrative java bean could not be initialized.
Error 122: Administrative java bean has no dialog classes to load. The properties file describing theadministrative java bean is missing the "list" property.
Error 123: The properties file describing the administrative java bean has a missing property.
Error 124: Failed to find property bundle.
Error 125: Security Exception trying to create URLClassLoader. Please verify that the .java.policy file grants
the proper permissions. You should typically create a .java.policy file in your home directory. The contents of
the .java.policy file are case sensitive, so it is best to copy the sample file that is distributed with the
LifeKeeper GUI package.
If you are using a browser plug-in for Java, then the user home directory that is being used for the java
environment can be verified by enabling the Java console and examining the first few lines that are displayed.
Refer to Configuring the LifeKeeper GUI for more information on configuring the GUI client.
Error 126: Could not find resource on server.
Error 127: Could not find extend properties file for this kit.
Error 128: Internal properties file error.
Error 129: Cannot establish an RMI connection to the server. Verify the LifeKeeper GUI Server is running on
the server.
Error 130: The tag entered is being used by another resource. Please enter another tag.
Error 131: Exception calling invokeAndWait method to update the user interface.
Error 132: Encountered exception when invoking administrative java bean.
Error 133: Invalid value entered for equivalency priority. The priority value must be in the range of 1 through999.

SteelEye Protection Suite for Windows Technical Documentation
Page 154

GUI Network Related - Initial Connection to Server Failed (Error 117)

Error 134: The equivalency priority value conflicts with another priority in the table. Each equivalency priority
value must be unique in the table.

GUI Network Related - Initial Connection to Server Failed(Error 117)
Symptom
Initial Connection to server failed (Error 117).
If you are attempting to connect to a server that has two or more network interface cards (NICs), it could
indicate a Java RMI binding problem where the first NIC (the one that appears first in the output of ipconfig
utility) has a non-reachable IP address.

Solution
You may need to reorder the protocol binding for use by the network services of the SteelEye Protection Suite
server. On each SteelEye Protection Suite server, open "Network and Dial-up Connections", and on the
Advanced menu, select Advanced Settings. The List Box at the top of the dialog shows the current order of
the NIC cards. Click the arrow button to reorder them so that the reachable NIC is at the top of the list. Thisshould enable Java RMI to allow client to connect to the server. A reboot of the server is required for this totake effect.

GUI Network Related - Long Connection Delays on Windows
Platforms
SymptomLong Connection Delays on Windows Platforms.

Solution
From Sun FAQ:
“Most likely, your host’s networking setup is incorrect. RMI uses the JavaAPI networking classes, inparticular java.net.InetAddress, which will cause TCP/IP host name lookups for both host to address mapping
and address to hostname. On Windows, the lookup functions are performed by the native Windows socket
library, so the delays are not happening in RMI but in the Windows libraries. If your host is set up to use DNS,
then this could be a problem with the DNS server not knowing about the hosts involved in communication andwhat you are experiencing are DNS lookup timeouts. If this is the case, try specifying all thehostnames/addresses involved in the local file\winnt\system32\drivers\etc\hosts or \windows\hosts. The
format of a typical host file is:

IPAddress Server Name

SteelEye Protection Suite for Windows Technical Documentation
Page 155

GUI Network Related - NoRouteToHostException Message Generated During Connection Attempt

e.g.: 208.2.84.61 homer.somecompany.com
This should reduce the time it takes to make the first lookup.”
In addition, incorrect settings of the Subnet Mask and Gateway address may result in connection delays andfailures. Verify with your Network Administrator that these settings are correct.

GUI Network Related - NoRouteToHostException Message
Generated During Connection Attempt
Symptom
NoRouteToHostException Message Generated During Connection Attempt.
A socket could not be connected to a remote host because the host could not be contacted.

Solution
Typically, this indicates that some link in the network between the local and remote server is down or that the
remote server is behind a firewall.

GUI Network Related - Unknown Host Exception Message
Generated During Connection Attempt
Symptom
Unknown Host Exception Message Generated During Connection Attempt.
The LifeKeeper GUI Client and Server use Java RMI (Remote Method Invocation) technology tocommunicate. For RMI to work correctly, the client and server must use resolvable hostname or IP
addresses. When unresolvable names, WINS names, or unqualified DHCP names are used, this causes
Java to throw an UnknownHostException.
This error message may also occur under the following conditions:lServer name does not exist. Check for misspelled server name.

lMisconfigured DHCP servers may set the fully qualified domain name of RMI servers to be the domainname of the resolver domain instead of the domain in which the RMI server actually resides. In thiscase, RMI clients outside the server's DHCP domain will be unable to contact the server because of
the incorrect domain name.

l

The server is on a network that is configured to use Windows Internet Naming Service (WINS). Hosts
that are registered under WINS may not be reachable by hosts that rely solely upon DNS.

l

The RMI client and server reside on opposite sides of a firewall. If your RMI client lies outside a firewall
and the server resides inside of it, the client will not be able to make any remote calls to the server.

SteelEye Protection Suite for Windows Technical Documentation
Page 156

Solution

Solution
When using the LifeKeeper GUI, the hostname supplied by the client must be resolvable from the server andthe hostname from the server must be resolvable by the client. The LifeKeeper GUI catches this exception
and alerts the user. If the client cannot resolve the server hostname, this exception is caught and Message
115 is displayed. If the server cannot resolve the Client hostname, this exception is caught and Message 116
is displayed. Both of these messages include the part of the Java exception which specifies the unqualified
hostname that was attempted.
Included in the following sections are some procedures that may be used to test or verify that hostname
resolution is working correctly.

From Windows
1. Verify communication with the SteelEye Protection Suite server. From a prompt, ping the target using
the hostname:ping<TARGET_NAME>
For example;
ping homer
A reply listing the target’s qualified hostname and IP address should be seen.
2. Verify proper configuration.
a. Check configuration of DNS or install a DNS server on your network.
b. Check the settings for ControlPanel->Network->Protocols->TCP/IP. Verify with your Network Administrator that these settings are correct. Note that the hostname in the DNS tabshould match the name used on the local name server. This should also match the hostname
specified in the GUI error message.
c. Try editing the hosts file to include entries for the local host and the SteelEye Protection Suite
servers that it will be connected to.
On Windows 2003/2008 systems, the hosts file is:%SystemRoot%\system32\drivers\etc\HOSTS (e.g.
C:\windows\system32\drivers\etc\HOSTS)
Note: On Windows 2003/2008, if the last entry in the hosts file is not concluded with a carriagereturn/line-feed, then the hosts file will not be read at all.
For example, if my system is called HOSTCLIENT.MYDOMAIN.COM and uses the IPaddress
153.66.140.1, add the following entry to the hostsfile:
153.66.140.1 HOSTCLIENT.MYDOMAIN.COM
3. Try setting the hostname property to be used by the GUI client. To do this from a browser with the
Plug-in, open the Java Plug-In Control Panel and set the host name for the client by adding the following to “Java Run Time Parameters.”-Djava.rmi.server.hostname=<MY_HOST>

SteelEye Protection Suite for Windows Technical Documentation
Page 157

From Linux

4. Check for Microsoft network-related patches at www.microsoft.com.

From Linux
1. Verify communication with the other server by pinging the target server from Linux using its hostname
or IP address:
ping -s<TARGET_NAME>
For example:
ping -s homer
A reply listing the target’s qualified hostname should be seen.
2. Verify that localhost is resolvable by each server in the cluster using ping with its hostname or IP
address. If DNS is not implemented, edit the /etc/hosts file and add an entry for the localhost name.
This entry can list either the IP address for the local server or it can list the default entry (127.0.0.1).
3. Check that DNS is specified before NIS. DNS should be put before NIS in the host’s line of/etc/nsswitch.conf, and /etc/resolv.conf should point to a properly configured DNS server(s).
4. If DNS is not to be implemented or no other method works, edit the /etc/hosts file to add an entry forthe hostname.
5. Try setting the hostname property to be used by the GUI client. This will need to be changed for eachadministrator.
To do this from a browser with the Plug-in, open the Java Plug-In Control Panel and set thehostname for the client by adding the following to Java RunTime Parameters:-Djava.rmi.server.hostname=<MY_HOST>
To do this from the HotJava browser, append the following to the hotjava command line:-Djava.rmi.server.hostname=<MY_HOST>
For Example:-Djava.rmi.server.hostname=153.66.140.1-Djava.rmi.server.hostname= homer.somecompany.com

GUI Server Troubleshooting
Symptom
The LifeKeeper GUI uses Ports 81 and 82 on each server for its administration web server and Java remoteobject registry. If another application is using the same ports, the LifeKeeper GUI will not function properly.

SteelEye Protection Suite for Windows Technical Documentation
Page 158

Solution

Solution
These values may be changed by editing the following registry entries:
GUI_WEB_PORT=81
GUI_RMI_PORT=82
These entries are located in the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\JavaGUI\Server
Note: The port values are initialized in the GUI server when it is started. If you alter them, you will need to stopand restart the GUI server. These values must be the same across all clusters to which you connect.

Health Check Timeouts
SYMPTOM: Occasionally, SteelEye Protection Suite is installed on a system that is not performing well.
There are tell-tale signs of abnormal system behavior that SteelEye Protection Suite can detect such as thehealth check processes not starting or ending properly. The most common problem causing check process
timeouts is incorrect system memory optimization for databases or mail servers. There must be enoughmemory to start health check processes and initiate failovers at all times.
SOLUTION: The SteelEye Protection Suite Release Notes include guidelines that identify system memory
requirements for SteelEye Protection Suite. It also briefly explains how to use the Windows Performance
Monitors to verify that enough memory is available for applications such as SteelEye Protection Suite in yoursystem. To help identify this situation, there are two Resource Monitoring options available to record abnormal
behavior and three options to take corrective action when check process timeouts are occurring. All five
options can be enabled or disabled as SteelEye Protection Suite registry settings to meet specific customer
requirements and preferences:
HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\General\ResMon_
RecordTimeout
HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\General\ResMon_RecordMemory
HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\General\ResMon_ResFail
HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\General\ResMon_
RebootWaitInSec
HKEY_LOCAL_MACHINE\SOFTWARE\SteelEye\LifeKeeper\General\ResMon_
ResFailMaxWaitInMin
The first 4 options (RecordTimeout, RecordMemory, ResFail, and RebootWaitInSec) are
triggered by any SteelEye Protection Suite Quick Check or Deep Check process monitoring a protectedresource that does not complete in the expected amount of time.
ResMon_RecordTimeout – This option records any Quick Check or Deep Check process that times out.
This information is logged in <LifeKeeper Root Folder>\Out\ResMonTimeout.log file. This option
is enabled (=1) by default. To disable, set the value to 0.

SteelEye Protection Suite for Windows Technical Documentation
Page 159

Incomplete Resource Creation

ResMon_RecordMemory – This option records system memory usage and process memory usage for every
active process whenever a Quick Check or Deep Check process times out. Memory usage is logged in<LifeKeeper Root Folder>\Out\ResMonTimeout.log file. This option is enabled (=1) by
default. To disable, set the value to 0.
ResMon_ResFail – This option causes a resource hierarchy failover whenever a Quick Check or Deep
Check process times out. All dependent resources in the affected hierarchy are failed over. This option isdisabled (=0) by default. To enable, set the value to 1.
ResMon_RebootWaitInSec – This option causes a system reboot whenever a Quick Check or Deep
Check process times out. This option is disabled (=0) by default. To enable, enter any non-zero number in theregistry setting. This number will become the countdown displayed on the system console when the system
is rebooted by this feature. The reboot sequence is totally automatic and designed for unattended system
operation. Once the countdown is started, the reboot cannot be stopped.
ResMon_ResFailMaxWaitInMin – This option will monitor the SteelEye Protection Suite failover process
whenever any failover is occurring. The value of this registry setting is the number of minutes SteelEye
Protection Suite will wait for a resource hierarchy failover to complete. If the failover process cannot be
started or if the failover does not complete in the specified number of minutes, SteelEye Protection Suite willattempt to reboot the system. If the resources were not failed over, they will come in service again on thesame server that was rebooted. This option is disabled (=0) by default.
The Resource Monitoring Options apply to all protected resources and they can be changed at any time.
Changed settings take affect the next time a Quick Check or Deep Check process is started.

Incomplete Resource Creation
Description
If the resource setup process is interrupted leaving instances only partially created, you must perform manual
cleanup before attempting to install the hierarchy again. Use the LifeKeeper GUI to delete any partiallycreated resources. See Deleting a Hierarchy from All Servers for instructions. If the hierarchy list does notcontain these resources, you may need to use the ins_remove and dep_remove to clean up thepartial hierarchies.

Installation - Access is Denied
Symptom
During upgrade or re-installation, SteelEye Protection Suite generates “Access is denied” error message.

Solution
The SteelEye Protection Suite services have not all stopped. This can occur if Setup was unable to stop the
SteelEye Protection Suite services. Open a command window and enter $LKROOT\bin\lkstop to stop

SteelEye Protection Suite for Windows Technical Documentation
Page 160

IP Resource Create Issue

all the SteelEye Protection Suite services, then wait until you see “LIFEKEEPER NOW STOPPED” before
running Setup.

IP Resource Create Issue
Symptom
IP resource Pre-Extend Wizard can fail if new IP address partially matches an existing IP address.

Workaround
Currently no workaround is available. This will be addressed in a future release.

Java Mixed Signed and Unsigned Code Warning
Symptom
When loading the LifeKeeper Java GUI client applet from a remote system, the following security warning
may be displayed:Enter “Run” and the following dialog will be displayed:

SteelEye Protection Suite for Windows Technical Documentation
Page 161

Solution

Block? Enter “No” and the LifeKeeper GUI will be allowed to operate.

Solution
To reduce the number of security warnings, you have two options:
1. Check the “Always trust content from this publisher” box and select “Run”. The next time the
LifeKeeper GUI Java client is loaded, the warning message will not be displayed.
or
2. Add the following entry to your Java “deployment.properties” file to eliminate the second dialog about
blocking. The security warning will still be displayed when you load the Java client, however, the applet
will not be blocked and the Block “Yes” or “No” dialog will not be displayed. Please note this setting will
apply to all of your Java applets.
deployment.security.mixcode=HIDE_RUN
To bypass both messages, implement 1 and 2.

LANMAN Name May Be Seen Twice in Browse List
Symptom
After creating a LANMAN resource, the LANMAN name may be seen twice in the browse list.

Solution
One of these entries is an unusable Workstation record. Please disregard this entry and use the other
LANMAN Server name.

SteelEye Protection Suite for Windows Technical Documentation
Page 162

Licensing - Licensed Recovery Kit Resource Fails to Come In Service

Licensing - Licensed Recovery Kit Resource Fails to Come In
Service
Symptom
After upgrade, licensed recovery kit resource fails to come in service and the following error is logged to theApplication Event Log by SteelEye Protection Suite:“Process: lcdmachfail(3176) *ERROR* (No. 1001) resource <tag name>requires a license (for Kit <recovery kit type>) but none isinstalled."

Solution
Use the SteelEye Protection Suite licensing utility to install your recovery kit license key. See Obtaining andInstalling the License in the SteelEye Protection Suite for Windows Installation Guide for information on
installing a license.

Licensing - License Key Not Found
Symptom
After installing licensed recovery kit, the following error is logged to the Application Event Log by SteelEye
Protection Suite:“Process: Lkinit:(1832) *ERROR* (No. 20042) SPS Recovery Kit<licensed recovery kit> license key NOT FOUND”.

Solution
Use the SteelEye Protection Suite licensing utility to install your recovery kit license. See Obtaining andInstalling the License in the SteelEye Protection Suite for Windows Installation Guide for information on
installing a license.

SteelEye Protection Suite Web Client May Lock Up
Symptom
The SteelEye Protection Suite web client may lock up when used from a server machine if the "-" (reduceresource height) or "+" (increase resource height) accelerator keys are hit during the initial paint of SteelEye
Protection Suite resources for that server.

Solution

SteelEye Protection Suite for Windows Technical Documentation
Page 163

SteelEye Protection Suite Web Client May Lock Up - Multiple Changes Made to Existing Hierarchy

To recover, open Windows Task Manager and select "End Task" for the "LifeKeeper - <web browser, e.g.,
Microsoft Internet Explorer>" application. It may take up to one minute for the processes to end. Restart the
SteelEye Protection Suite web client from the Start->All Programs->SteelEye shortcut and wait for initial
screen paint to complete before using accelerator keys.

SteelEye Protection Suite Web Client May Lock Up - Multiple
Changes Made to Existing Hierarchy
Symptom
The SteelEye Protection Suite web client may lock up when used from the server machine if multiple changes
are made to an existing hierarchy (i.e. create/delete dependencies), closing and reopening the SteelEye
Protection Suite client between changes.

Solution
To recover, open Windows Task Manager and select End Task for the "LifeKeeper - <web browser, e.g.,
Microsoft Internet Explorer>" application. It may take up to one minute for the processes to end. For
hierarchy administration on the server, use the LifeKeeper GUI (Admin Only) application. Shortcut is Start>All Programs->SteelEye->LifeKeeper->LifeKeeper (Admin Only).

New Evaluation License Key Error
Symptom
When evaluating SteelEye Protection Suite for Windows, an error may occur if a new evaluation license key
is not used. The old evaluation licenses will not work on this release.

Solution
A new evaluation license key must be obtained. Restart the License Key Manager and enter the new,properly formatted license key.

Recovering From a SteelEye Protection Suite Server Failure
in a 1 x 1 Configuration
If a server in your SteelEye Protection Suite cluster experiences a failure that causes re-installation of theoperating system (and thus SteelEye Protection Suite), you will have to re-extend the resource hierarchiesfrom each server in the cluster. If a server in the cluster has a shared equivalency relationship with the reinstalled server, however, SteelEye Protection Suite will not allow you to extend the existing resource
hierarchy to the re-installed server. SteelEye Protection Suite will also not allow you to unextend the hierarchy
from the re-installed server because the hierarchy does not really exist on the server that was re-installed.

SteelEye Protection Suite for Windows Technical Documentation
Page 164

Suggested Action:

Suggested Action:
After reinstalling your operating systems and all related patches as well as SteelEye Protection Suite, begin
the following steps for recovery (Note: The examples in the Suggested Action below are using test systemnames "BENHOGAN" and "GPLAYER"):
1. On each server where the resource hierarchies are configured, use the eqv_list command to obtain alist of all the shared equivalencies.
eqv_list [-d destsys] [-s sys] [-t tag] [-e SHARED] [-fC]
This function prints strings to standard output describing equivalency relationships between
resource instances.
Example:c:\LK\Bin>eqv_list
BENHOGAN2008 LK1-BENHOGAN2K8 GPLAYER2008 LK1-BENHOGAN2K8SHARED 1 10
BENHOGAN2008 Vol.E GPLAYER2008 Vol.E SHARED 1 10
See LifeKeeper GUI below of hierarchies, resources, etc.

2. On each server where the resource hierarchies are configured, use eqv_remove to manually remove
the equivalency relationship for each resource in the hierarchy.
This function removes equivalency from the configuration database on system destsys (local
if not specified) of equivalency type, specified by the -e option, between the resources tag andothertag existing on systems sys and othersys respectively.
eqv_remove [-d destsys] [-s sys] -t tag [-S othersys]-oSteelEye Protection Suite for Windows Technical Documentation
Page 165

Suggested Action:othertag [-e SHARED]
eqv_remove -s {this system} –t {TAGNAME} –S {othersys thathas gone away} [-e SHARED]
Example:c:\LK\Bin>eqv_remove -s BENHOGAN2008 -t LK1-BENHOGAN2K8 -S
GPLAYER2008 -e SHARED
c:\LK\Bin>
3. Execute the eqv_list command again. There should be “no” list of shared equivalencies, etc.
Notice on the LifeKeeper GUI below how the target resources have been removed:

4. If there are any DataKeeper mirrored volumes configured in your cluster, clean up the LKDRInfo filefor that volume.
SteelEye Protection Suite will create an LKDRInfo.<volume> file in the folder%LKROOT%\subsys\filesys\resources\volume for each mirrored volume resource.
This file should be deleted.
C:\LK\BIN> cd %LKROOT%\subsys\filesys\resources\volume
C:\LK\subsys\filesys\resources\volume> dir LKDRInfo.E
05/23/2012 01:02 PM 39 LKDRInfo.E
C:\LK\subsys\filesys\resources\volume> del LKDRInfo.E
5. If there are any DataKeeper mirrored volumes configured in your cluster, clean up the mirror and delete
the DataKeeper job that contains that mirror.
DataKeeper mirrors and jobs must be recreated when the cluster is re-extended to thereinstalled server. Therefore, the local end of any mirrors that are configured must be deleted
and any jobs that are configured with those mirrors must be deleted.

SteelEye Protection Suite for Windows Technical Documentation
Page 166

Suggested Action:

C:\LK\subsys\filesys\resources\volume> cd %ExtMirrBase%
C:\Program Files\SteelEye\DataKeeper> emcmd .
getjobinfoforvol E
ID = e829700c-27b0-447f-b852-1a3135da31a7
Name = E Vol
Description =MirrorEndPoints = BENHOGAN2008;E;10.200.8.25;GPLAYER2008;E;10.200.8.26;A
C:\Program Files\SteelEye\DataKeeper> reg /delete
HKLM\System\CurrentControlSet\Services\ExtMirr\Parameters\Jobs\e829700c-27b0-447f-b852-1a3135da31a7
Permanently delete the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ExtMirr\Paramet
ers\Jobs\1b5e8715-a488-4030-8166-45c9232bc04e (Yes/No)? y
The operation completed successfully.
C:\Program Files\SteelEye\DataKeeper> emcmd .
getjobinfoforvol E
C:\Program Files\ SteelEye\DataKeeper> emcmd .
deletelocalmirroronly E
Status = 0
C:\Program Files\ SteelEye\DataKeeper> emcmd .
clearswitchover E
Status = 0
Repeat these steps for all mirrored volumes. The job must be deleted from the registry
directly; attempting to delete the job using “emcmd . deletejob” will fail because
DataKeeper tries to delete the job on all nodes. This will not work since one of thenodes no longer exists and the job will be left intact.
6. You are now ready to remove the old system.
a. Display all systems that were in the SteelEye Protection Suite cluster:
sys_list [-d destsys]
Example:c:\LK\Bin>sys_list
BENHOGAN2008

SteelEye Protection Suite for Windows Technical Documentation
Page 167

Suggested Action:

GPLAYER2008
b. Remove all old targets/systems.
sys_remove [-d destsys] -s sys
Example:c:\LK\Bin>sys_remove -s GPLAYER2008
Do this for all systems participating in the SteelEye Protection Suite cluster
Note: If attempting to execute this command for the local/source system, thefollowing error will be received:
c:\LK\Bin>sys_remove -s BENHOGAN2008(null)Process: sys_remove(2728)[File:sys.C Line:81]*ERROR* (No. 424) can't remove entry for local
system "BENHOGAN2008"
7. Remove communication paths.
a. Verify the comm paths that are present:
net_listb. Remove these comm paths:
net_remove
8. Write the changes.
lcdsync [-d destname]Example:c:\LK\Bin>lcdsync
This function checks to see if the SteelEye Protection Suite resource hierarchy configurationand communication path status data stored in shared memory has been modified. If it isdifferent, the data is "synchronously" written to disk. Therefore, when this program returns, thedata is guaranteed to be on disk properly.
Optional Note: To completely remove all resources, first generate a list of all resource
instances:ins_list [-d destsys] [-fC] [-R top] [-a appname] [-r typ][t tag] [-i id]
then remove these instances:

SteelEye Protection Suite for Windows Technical Documentation
Page 168

Suggested Action:

ins_remove [-d destsys] [-R roottag] [-a appname] [-rrestyp][-t tag] [-i id] [-v] [-I] [-N] [-G]9. Close the LifeKeeper GUI and reopen.

10. Extend each resource hierarchy from the server where the resource hierarchy is in service to the reinstalled server using the GUI.
a. Connect to your reinstalled server/target. Note: This may also require a re-creation of the commpaths.

SteelEye Protection Suite for Windows Technical Documentation
Page 169

Suggested Action:b. Extend resource hierarchy.

SteelEye Protection Suite for Windows Technical Documentation
Page 170

Suggested Action:c. Add/extend mirror resource.

SteelEye Protection Suite for Windows Technical Documentation
Page 171

Recovering Out-of-Service Hierarchies

Complete -- All protected resources have been recovered and are protected once again.

Recovering Out-of-Service Hierarchies
Description
As a part of the recovery following the failure of a SteelEye Protection Suite server, resource hierarchies thatare configured on the failed server but are not in service anywhere at the time of the server failure arerecovered on the highest priority alive server at the time of the failure. This is the case no matter where theout-of-service hierarchy was last in service including the failed server, the recovering server or some otherserver in the hierarchy.

Remove Hangs During Recovery Kit Uninstall
Symptom
If a recovery kit is uninstalled while there are resource hierarchies of that kit in service, the Remove hangs.
To avoid this situation, it is recommended to always take a recovery kit’s resource hierarchies Out of Service
and delete them before uninstalling the recovery kit software.

Solution
If you encounter this situation, you will most likely need to re-boot your system since there are many related
processes that hang, and clearing them all can be difficult.

SteelEye Protection Suite for Windows Technical Documentation
Page 172

Replicated Volume Switchover Failure

Replicated Volume Switchover Failure
Description
If the DELETEMIRROR command fails during switchover of a replicated volume, the following error message
will display in the Output panel:*WARNING* (No. 12104) Delete mirror action for volume R: failed withstatus 51 (command=C:/SDR/EMCmd10.10.1.2 DELETEMIRROR R: 10.10.1.1)
Refer to the table below for the Error Status number, description and recommended action. You can also use
the following command to obtain more information about the error status:
Command: net helpmsg {status}
Example:Error
Statusnet helpmsg 51

Description

Recommended Action
Check both systems for permission
differences that may exclude the Local
System Account from accessing themirrored volume.

5

Permission issues on the current SOURCE are
not allowing the mirror to be deleted.

46

Mismatched user/password combination between Use a domain account or make sure the local
systems. This will probably only occur if running user accounts you are signing on with have
DELETEMIRROR from the command prompt.
the same password.

51

Windows cannot find the network path.

Make sure all network cards in both systems
have File & Print Sharing for Microsoft
Networks checked.

Cannot access the IP Address specified.

Verify your network configuration (including
HOSTS files and DNS are all resolving theIP address consistently.

The ring 2 stack is in use

Make sure all the network cards in both
systems have Client for Microsoft Networks
checked.

53

207

Restore and Health Check Account Failures
SymptomSome recovery kits monitor protected resources by performing query operations that simulate user and/or
client activity. This provides SteelEye Protection Suite with accurate status information about a protected
application or service. It also requires that a valid user account ID and password with login privileges be

SteelEye Protection Suite for Windows Technical Documentation
Page 173

Solution

provided during resource object creation. If the user account does not have login privileges on a particularsystem, the following error message will be recorded in the Windows Application Event Log:
Error Number 1385 - "Logon failure: the user has not been granted
the requested logon type at this computer.

Solution
Have the domain administrator provide login privileges for the user account. Also, most recovery kits that
require an ID and password have a resource properties or configuration tab available for administrators tochange the account information for the resource. Right-click on the resource object and select the appropriate
properties or configuration tab. If the resource does not have an account update feature, the resource object
must be deleted and a new one created with updated account information.

SQL 2005 and SQL 2008
Symptom
When using SQL 2005 and SQL 2008, after a switchover or a failover, the variable @@servername still points
to the primary system.

Solution
You can use “select SERVERPROPERTY(‘ServerName’)” instead of using the variable@@servername. This query will return the correct name of the machine after a switchover or failover.
or
1. Execute the following commands on the new backup server:
sp_dropserver @server=’sys-A’
sp_addserver @server=’sys-B’, @local=’LOCAL’
2. Restart the service.

SteelEye Protection Suite for Windows Technical Documentation
Page 174SQL Server Reporting Services (MSSQLSERVER)SQL Server Reporting Services (MSSQLSERVER)
Symptom
When protecting SQL Server 2008 R2 services, the "SQL Server Reporting Services (MSSQLSERVER)"
may be selected as an optional protected service. However, if the time required to start this service exceeds
the default Windows service timeout, you may get Error 1053, the service may fail to start and the SteelEye
Protection Suite resource in-service operation will fail.

Solution
This problem may be related to system performance and configuration issues. The recommended action is to
not protect this service. However, if it must be protected, the following registry setting will extend the time
available for services to start. In the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control"
Registry key, add a "ServicesPipeTimeout" value as a DWORD, and set the value to 60000 (decimal, = 60
secs.).

Two-Server Cluster Issue
Symptom
In a two-server cluster, when the primary server fails or is shut down which causes the hierarchies to fail overto the backup server, and the backup server also fails or is shut down before the hierarchies are entirely failed
over to the backup server, the following behavior has been detected:
When both servers are rebooted, some of the resources in the hierarchies will be in service on one server andsome will be in service on the other server. Some of the higher-level parent resources may not be in service oneither server.

Solution
After both servers have been restarted and have completed SteelEye Protection Suite initialization, select theparent resource in a hierarchy that did not come in-service from the Hierarchy Administration interface andbring it in-service manually. Repeat this task until all hierarchies are in-service.

Unknown User Name or Bad Password
Access Denied: Unknown User Name or Bad Password

SteelEye Protection Suite for Windows Technical Documentation
Page 175

SymptomSymptom
If a SteelEye Protection Suite client tries to communicate with a server that is in the process of shutting down,
the server may abort the validation process by refusing to allow the client to log on. In that case, the client will
display a message stating “Access Denied: unknown user name or bad password. Only members of theSteelEye Protection Suite-authorized security groups can use SteelEye Protection Suite. Would you like tore-enter the authentication data?”

Solution
Click Yes to input new credentials, and then click either Cancel or re-enter the credentials and click OK.
Note: If you click No initially, the LifeKeeper GUI will disconnect from that server and will not reconnect
automatically.

Web Client Troubleshooting
Background
The web client does not display the Cluster Connect dialog.

Answer
If the web client does not display the Cluster Connect dialog, try the following:
1. Check whether the applet failed. Usually a message is printed somewhere in the browser window
specifying the state of the applet. In Internet Explorer, an icon may appear instead of the applet in
addition to some text status. Clicking this icon may bring up a description of the failure.
2. Open the Java Console.
l

For FireFox and older versions of Internet Explorer, run the Java Plug-In applet fromyour machine's Control Panel and select the option to show the console. Restart yourbrowser.

l

For recent versions of Internet Explorer, select Tools > Sun Java Console. If you
do not see the Sun Java Console menu item, select Tools > Manage Add-Ons andenable the console, after which you may need to restart your browser before the console
will appear.

l

For Mozilla, select Tools > Web Development > Sun Java Console.

If the web client is not open, reopen the URL, http://<server name>:81, to start it.
Check the console for any messages. The messages should help you resolve the problem. If the problem
appears to be network related, refer to the Network-Related Troubleshooting section.

SteelEye Protection Suite for Windows Technical Documentation
Page 176

Win2008 - IIS Resource Hierarchy Creation Error

Win2008 - IIS Resource Hierarchy Creation Error
Symptom
On a Win2008 system when creating an IIS Resource Hierarchy, you receive the following message:
No qualified sites were found...
and the create fails.
BACKGROUND / TROUBLESHOOTING:------------------------------------------------Run the following command:
C:\LK\Admin\kit\webapp\bin>enumiis query all
Look for the following error message:
ERROR: CoCreateInstance Failed! Error: -2147221164 (80040154)
ERROR: W3Service Com Object Failed to initialize

SolutionWith Win2008, the IIS 6 Management Compatibility (Role Service) is required for the SteelEye Protection
Suite IIS Kit. You should install all of this option (Metabase Compatibility, WMI Compatibility, Scripting Tools,
Management Console).

SteelEye Protection Suite for Windows Technical Documentation
Page 177IndexIndex
A
Active/Active 13
Active/Standby 14
Administration 20
Applet Troubleshooting 151
Automatic Switchback 15

B
Browser Security 83
Configuring the Browser Security Level 106

C
Collapsing Resource Hierarchy Tree 114
Communication Path 4
Component 16
Creating 27
Deleting 29
Types 5

Configuration 12
LifeKeeper Configurations 16
Steps 13

Connecting to a Cluster 109
Core Software 2
CYGWIN 152

D
Dependency
Adding 48
Removing 48

SteelEye Protection Suite for Windows Technical Documentation
Page 178

IndexDisconnecting from a Cluster 110
DNS 126

E
EditFileShareResource 128
Expanding Resource Hierarchy Tree 114

F
FailoverDisabling Automatic Failover 26
Recovery 133

FirewallTroubleshooting 153

G
Generic Application 130
GUI
Administrator GUI Tasks 20
Configuring GUI Users 108
LifeKeeper GUI Server and Client Components 104
LifeKeeper GUI User Accounts 108
Running the GUI Application on a LifeKeeper Server 107
Troubleshooting
GUI Error Messages 153
GUI Network Related
Initial Connection to Server Failed (Error 117) 155
NoRouteToHostException Message Generated During Connection Attempt 156
Unknown Host Exception Message Generated During Connection Attempt 156
GUI Server Troubleshooting 158

H
Hardware Components 16

SteelEye Protection Suite for Windows Technical Documentation
Page 179

IndexHeartbeat 6
Interval 6

Hierarchies 7
Creating 30
DNS 30File Share 33
Generic Application 34
IP Address 38
LAN Manager 36
Troubleshooting
Incomplete Resource Creation 160
Win2008 - IIS Resource Hierarchy Creation Error 177
Volume 37
Deleting 49
Extending 44
DNS 45File Share 45
Generic Application 46
IP Address 46
LAN Manager 46
Volume Resource 46
Information 8
Maintaining 133
Relationships 7
Resource States 8
Shared Equivalencies 9
StatusStatus Table 92
Viewing the Status of Resources 112
Transferring 129

SteelEye Protection Suite for Windows Technical Documentation
Page 180

IndexUnextending 47
Working With 29

I
In Service 115
Taking Volume Resources In and Out Of Service 116

Installation
Troubleshooting 160

Intelligent 15
IP 125JJava 87
Upgrade 87

L
LCD 120
Diagram of LCD Directory 121
LCD Configuration Data 122
LCD Directory Structure 120
LCD Resource Types 122
LCDI Commands 124

LCM 124
LicenseTroubleshooting
License Key Not Found 163
Licensed Recovery Kit Resource Fails to Come In Service 163
New Evaluation License Key Error 164

LifeKeeper Communications Manager 124
LifeKeeper Configuration Database 120
Diagram of LCD Directory 121

SteelEye Protection Suite for Windows Technical Documentation
Page 181

IndexLCD Configuration Data 122
LCD Directory Structure 120
LCD Resource Types 122
LCDI Commands 124
Resources Subdirectories 123

LKSUPPORT 83

M
Maintenance
Maintaining a LifeKeeper Protected System 129
Maintaining a Resource Hierarchy 133
Maintenance Tasks 125

Menus 98
Edit Menu - Resource 100
Edit Menu - Server 101
File 100
Help 103
Resource Context 98
Server Context 99
View 102

Message Bar 93

O
Offline Maintenance 129
Out of Service 116
Taking Volume Resources In and Out Of Service 116
Troubleshooting 172

Output Panel 93

SteelEye Protection Suite for Windows Technical Documentation
Page 182

IndexP
Properties 93
Resource
Editing Resource Properties 44
Viewing Resource Properties 113
Server 21
Editing Server Properties 20
Viewing Server Properties 111

Protected File Shares 128
Protected Resources 1

R
Recovering After Server Failure 164
Recovery Kits 4
Core 2
DNS 4
Generic Application 4
IP 3
LAN Manager 3
Microsoft IIS 4
Volume 3
Microsoft SQL Server 4

Replication 135
Monitoring Replicated Volume Resources 135
Performing Actions on Replicated Volumes 139
Settings 138

Requirements
IP Local Recovery 38

Rewind 145
Performing Rewind on Replicated Volume Resources 147

SteelEye Protection Suite for Windows Technical Documentation
Page 183

Index

RewindDump File 146-147
Settings 146

S
Server Failure 164
Shutdown Strategy 21
Split-Brain 140
Recovery 142

SQL
SQL 2005 and SQL 2008 174
SQL Server Reporting Services (MSSQLSERVER) 175

Status Table 92
Stopping LifeKeeper 125

T
Toolbars 94
Global 94
Resource Context 95
Server Context 96

Troubleshooting 151

U
Uninstallation 134

V
Viewing
Connected Servers 110
Message History 114
Resource Properties 113
Resource Tags and IDs 112
Server Log Files 111
Server Properties 111

SteelEye Protection Suite for Windows Technical Documentation
Page 184

IndexStatus of a Server 111
Status of Resources 112

Volume Locking 119
Volume Shadow Copy 119
VSS 119W
Web Client 105
Troubleshooting 176
LifeKeeper Web Client May Lock Up 163
LifeKeeper Web Client May Lock Up - Multiple Changes Made to Existing Hierarchy 164

SteelEye Protection Suite for Windows Technical Documentation
Page 185