LifeKeeper(c) 2.03E for Windows NT(c) Patch Readme File

The LifeKeeper 2.03 Patch E includes fixes for the following recovery kits:

IP, Volume, Lanman, SQL Server 6.5 and 7.0, Oracle 8 and 8i, Printer, File

Shares, Exchange and Web Server.

Lifekeeper(c) 2.03 Patch D is a PREREQUISITE for Patch E. Patch E DOES NOT

contain the fixes from Patch D.

We recommend installing this patch on each server AFTER you install all the

LifeKeeper products and Patch D. If installing this patch into an existing LifeKeeper

environment, transfer active hierarchies to other systems before

installing the patch.

How to Install the Patch:

NEW INSTALL

After installing all the LifeKeeper products:

1. On both servers, in the Control Panel, choose Services, and STOP the following two entries:

- LifeKeeper

- LifeKeeper External Interfaces

2. Open Windows Explorer to the folder containing the extracted files.

3. Run setup.exe from the folder.

4. In the Control Panel, choose Services, and START the following two entries:

- LifeKeeper

- LifeKeeper External Interfaces

Existing Install

1. Move the hierarchies to Server A.

2. Stop Lifekeeper on Server B using the Lifekeeper GUI or from the command prompt,

run LKSTOP.

3. Open Windows Explorer to the folder containing the extracted files.

4. Run setup.exe from the folder.

5. Start Lifekeeper by opening the Lifekeeper Hierarchy Status and Administration

window.

6. Move the hierarchies to Server B.

7. Stop Lifekeeper on Server A using the Lifekeeper GUI or from the command prompt,

run LKSTOP.

8. Open Windows Explorer to the folder containing the extracted files.

9. Run setup.exe from the folder.

10. Start Lifekeeper by opening the Lifekeeper Hierarchy Status and Administration

window.

11. Move the proper hierarchies back to Server A.

Problems fixed by this patch are listed below grouped by kit

NOTE: The fixes below reference an “MKS problem”. There is an unproved problem with the MKS toolkit used with Lifekeeper, where parameters passed between scripts, are lost. The fixes that address this problem simply log an error in the event log, and exit success. The lost parameter will not cause a “false failover” of a protected resource. If repeated error messages about this problem occur in the event log, contact NCR support.

IP KIT PATCHES:

Changed deepchk.ksh and quickchk.ksh to exit success when parameter is blank

due to MKS problem, and log an event

SQL 6.5 KIT PATCHES:

Changed deepchk.ksh and quickchk.ksh to exit success when parameter is blank

due to MKS problem, and log an event

SQL 7.0 KIT PATCHES:

1. SQL logins have access to databases they are not supposed to have access to.

Updated deepchk.ksh and aRestore7.ksh scripts.

2. SQL active/active hierarchy doesn't fail when registry keys are missing.

Corrected DeepChk.ksh will detect the missing registry entries and attempt a failover, the failover will not work correctly if the registry key for the SQL software path has also been deleted. Error 14619 will be logged, indicating that the path for MSSQL executables could not be found in the registry.

3. Lifekeeper displays MS SQLServer sa password when using the Lifekeeper command "lkstop" from a command prompt. Updated remove.ksh for MS SQL Server

4. Changed deepchk.ksh and quickchk.ksh to exit success when parameter is blank

due to MKS problem, and log an event

ORACLE KIT PATCHES:

Changed deepchk.ksh and quickchk.ksh to exit success when parameter is blank

due to MKS problem, and log an event

LANMAN PATCHES:

1. Changed deepchk.ksh and quickchk.ksh to exit success when parameter is blank

due to MKS problem, and log an event

2. Changed deepchk.ksh and quickchk.ksh to use a while loop for getops

VOLUME KIT PATCHES:

Changed deepchk.ksh and quickchk.ksh to exit success when parameter is blank

due to MKS problem, and log an event

FILESHARE KIT PATCHES:

Changed deepchk.ksh and quickchk.ksh to exit success when parameter is blank

due to MKS problem, and log an event

PRINTER KIT PATCHES:

Changed deepchk.ksh, quickchk.ksh, and restore.ksh to exit success when parameter is blank due to MKS problem and log an event

WEB SERVER KIT PATCHES:

Changed deepchk.ksh and quickchk.ksh to exit success when parameter is blank

due to MKS problem, and log an event

EXCHANGE KIT PATCHES:

1. Changed deepchk.ksh and quickchk.ksh to exit success when parameter is blank

due to MKS problem, and log an event

2. Changed quickchk.ksh to use a while loop for getops