SteelEye Protection Suite for Windows
v7.6
Release Notes

May 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
SteelEye Protection Suite for Windows Release Notes

1

Introduction

1

SteelEye Protection Suite Product Descriptions

1

LifeKeeper for Windows

1

DataKeeper for Windows

2

New Features of SteelEye Protection Suite for Windows Version 7
Bug Fixes

2
3

Product Requirements

4

Operating System

4

Requirements for Windows 2008

5

SteelEye Protection Suite Requirements

5

Optional Recovery Kits

6

GUI Requirements, Platforms and Browsers

7

Remote GUI Client Requirements

7

Installing and Removing SteelEye Protection Suite for Windows

8

Technical Notes

8

lkstart8

Running CHKDSK.EXE on SteelEye Protection Suite Protected Volume9

Running CHKDSK.EXE During System Boot

9

Communication Paths Over Fibre Channel

10

Using iSCSI Storage with SteelEye Protection Suite

10

IXS Processor Card in an IBM® System i™ (iSeries™) Server

11

System Load Considerations for Quickcheck and Deepcheck

11

VSS Shadow Copy

11

Restrictions and Known Issues

11

Table of ContentsiRestrictions

11

SCVMM 201211

Enterprise or DataCenter Server with Microsoft Failover Cluster Installed

12

Exchange 2007 Circular Logging and Rewind

12

FAT File System Support

12

Fault Tolerant Disk Sets

12

File Share Recovery Kit

12

LAN Manager Recovery Kit

12

Low Virtual Memory Degrades System State13

GUI interoperability

13

Discontinuing Serial Port Communication Paths

13

Console Application Management

13

Bitlocker Does Not Support DataKeeper

13

Known Issues

14Frequently Asked Questions

14

Documentation

15

Quick Start Guides

16

Training

16

Technical Support

16

Table of Contentsii

SteelEye Protection Suite for Windows
Release Notes
Version 7.6(Version 7 Update 6)

Important!!
Read This Document Before Attempting To Install Or Use This Product!
This document contains last minute information that must be considered
before, during and after installation.
To maintain the quality of our publications, we welcome your comments on their accuracy, clarity,organization and value.

Introduction
This information is provided for the person who installs, configures and/or administers the SteelEye Protection
Suite (SPS) for Windows product and contains important information such as version requirements, lastminute changes to instructions and procedures, product restrictions and known issues. It is important that you
review this document before installing and configuring the SteelEye Protection Suite software.

SteelEye Protection Suite Product Descriptions
SteelEye Protection Suite for Windows is a software bundle that integrates high availability clustering anddata replication functionality to protect mission-critical data and applications and includes DataKeeper (DK),
LifeKeeper (LK) and optional Recovery Kits.

LifeKeeper for Windows
LifeKeeper for Windows continues SIOS Technology Corp.’s tradition of providing world-class reliability for
mission critical applications. LifeKeeper for Windows leverages over a decade of experience with highavailability platforms by providing customers the ability to cluster multiple servers in order to monitor andrestore their applications. In the event of a failure, LifeKeeper recovers all network interfaces, data andapplications. Recovery occurs automatically and is transparent to clients, thus minimizing downtime and lossof business.
LifeKeeper for Windows enables continuous operations during planned downtime as well as in the event of asystem or application failure. With LifeKeeper, the amount of downtime required for common maintenancetasks and upgrades is significantly reduced or eliminated.

SteelEye Protection Suite for Windows Release Notes
Page 1

DataKeeper for Windows

DataKeeper for Windows
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.

New Features of SteelEye Protection Suite for Windows
Version 7
FeatureDescription
New in This 7.6 release
SteelEye Protection Suite's DataKeeper for Windows now supports the ability tocreate point in time copies of replicated target volumes without impacting
operations such as switchovers and failovers allowing access to data on astandby cluster node to perform tasks such as:
1. Enabling SQLServer Reporting on underutilized target systems

DataKeeper Target
Snapshot

2. Allowing backups to be run on secondary systems, offloading the IO andCPU demand from the primary system
3. Allowing offloading of Extract, Transform and Load (ETL) or other time-consuming processes
This allows your data to be used on an otherwise idle target node without
negatively impacting the performance of the source, offloading work from thesource by using the CPU and IO bandwitdh of the target server.

Microsoft SQL Server
2012 support

The SteelEye Protection Suite SQL Server Recovery Kit supports Microsoft
SQLServer 2012.

General maintenanceSee Bug Fixes below.

New in Version 7.4.3
General maintenanceBug fixes.

New in Version 7.4.2
General maintenanceBug fixes.

New in Version 7.4.1
General maintenanceBug fixes.

New in Version 7.2.1
Windows 2008 R2
SP1 Support

LifeKeeper Version 7.2.1 supports Windows 2008 R2 SP1.

SteelEye Protection Suite for Windows Release Notes
Page 2

Bug Fixes

FeatureDescription

DataKeeper 7.2.1 and
LifeKeeper Version 7.2.1 is compatible with DataKeeper Version 7.2.1 and later.
later compatibility

Documentation

A complete reference providing instructions for installing, configuring, administering and troubleshooting SteelEye LifeKeeper for Windows is now available on
the SteelEye Protection Suite for Windows Technical Documentation section of
our Documentation site.

New in Version 7.2
DataKeeper 7.2 compatibility

LifeKeeper 7.2 is compatible with DataKeeper 7.2.

Subscription-based
licensing support

LifeKeeper 7.2 supports subscription-based, time-limited licensing with an automatic license renewal option.

New in Version 7.0.2
File Server Resource
Manager support

LifeKeeper 7.0.2 and later supports Disk Quota functionality using File Server
Resource Manager on Windows Server 2008 R2. File Screening is not supported.

New in Version 7
SteelEye DataKeeper
LifeKeeper 7 and later works with DataKeeper to provide high availability for applicreplicated volume supations that use replicated volumes.
port
Microsoft Windows
LifeKeeper 7 and later works with Windows Server 2008 and Server 2008 R2 (see2008 and 2008 R2 supOperating System Requirements below).
port
Microsoft SQL Server
2008 support

The SteelEye Protection Suite SQL Server Recovery Kit supports Microsoft
SQLServer 2008 R1 and R2.

Bug Fixes
The following is a list of the latest bug fixes and enhancements.

Bug

Description

2644 Issue on lmhostid; service does not start; adapter address is ffffffff
3094 Compression of a mirrored volume can interfere with volume locking and cause volume I/O to hang3393 Crash of cluster node caused by DataKeeper
3442 Windows backup/recover program does not work properly in a DataKeeper environment

SteelEye Protection Suite for Windows Release Notes
Page 3

Product Requirements

Product Requirements
Operating System
Important: SIOS Technology Corp. recommends that users use Domain accounts that have local
administrator privileges on all servers running SteelEye Protection Suite. If local accounts are being used, theuser names and passwords must match on all servers running SteelEye Protection Suite. This
recommendation is for all editions and all platforms.
Note: All servers within a cluster should be running the same version of Windows.

Operating Systems

Product

Additional Software

Microsoft Windows:lSteelEye Protection Suite(Server Components)lServer 2008 R1,R2 and R2 SP1Standard,
Enterprise, and
DataCenter
editions.

n/aServer 2003 R1
and R2 Standard,Enterprise, Data
Center or Web
editions.

Microsoft Windows:

SteelEye Protection Suite(User Interface)lServer 2003 R1
and R2lServer 2008 R1,R2 and R2 SP1

l

Vista

l

XP

l

Windows 7

Microsoft .NET Framework 3.5 Service Pack
1 is required - download from:http://www.microsoft.com/net

MMC 3.0 - download from:http://support.microsoft.com/kb/907265

SteelEye Protection Suite for Windows Release Notes
Page 4

Requirements for Windows 2008

Product

Operating Systems

Additional Software

The operating systemversions listed above aresupported for guests
running on the following
virtual platforms:

Virtual Environmentsl

VMware vSphere
4.0 or laterlMicrosoft HyperV Server 2008 R2
or laterlCitrix XenServer
5.5 or laterl

KVM with Kernel
2.6.32 or later

32- and 64-bit versions (x86 and x64, no Itanium) of all of the listed OS platforms are supported

Requirements for Windows 2008
While installing SteelEye Protection Suite on Windows 2008, a dialog box will prompt whether the installer
should make the system configuration changes described below. If the installer is not allowed to make thesechanges, they will need to be made manually after installation is complete.
lWindows Firewalll

The Distributed Link Tracking Client must be disabled

For systems running SteelEye Protection Suite for Windows and Microsoft FTP Service 7.5 for IIS 7.0,
Windows 2008 R2 or 2008 R2 SP1 is required. SteelEye Protection Suite for Windows and Microsoft FTP
Service 7.5 for IIS 7.0 is not supported on Windows 2008 R1.
In addition, if your Windows 2008 servers are not in a domain, the Local Security policy setting "Network
Access: Let Everyone permissions apply to anonymous users" must be enabled. If the servers are in adomain, then this setting is not required.

SteelEye Protection Suite Requirements
The following table shows requirements applicable to the SteelEye Protection Suite core and recovery kits.

SteelEye Protection Suite for Windows Release Notes
Page 5

Optional Recovery Kits

Core

Requirement(s)SteelEye Pro- One license is required for every server on which SteelEye Protection Suite runs. This
tection Suite applies to both physical and virtual servers.
LicenseLAN Manager Requires the “File and Print Sharing for Microsoft Networks” component (lanRecovery Kit manserver) to be installed on the Windows server. NetBIOS must also be enabled. Otherwise, the LAN Manager resource will not come in service.
MemoryThe minimum memory requirement for a system supporting SteelEye Protection Suite for
Requirements Windows is based on the memory requirements for the operating system being used. Additional memory is required to run user applications in addition to that required for SteelEye
Protection Suite.
GUI

Ports:
SteelEye Protection Suite uses Port 82 for Remote Method Invocation (RMI)
communication between the GUI server and client.
The LifeKeeper GUI uses Port 81 for its administration web server which should be
different from any public web server. This is used by the GUI when run as a Java applet on
a remote client.
In the event of conflict with an existing application, these ports can be changed by editing
the RMI_PORT or WEB_PORT entries in the STEELEYE\LIFEKEEPER\JAVAGUI\SERVER
registry key.

Optional Recovery Kits
All optional SteelEye Protection Suite Recovery Kits require a software license key in order to function with
SteelEye Protection Suite.

Kit
Name

Versions/Requirements

Microsoft
SQL
ServerRecovery
Kit

Microsoft SQL 2000 (8.0) Standard and Enterprise Editions or Microsoft SQL 2005 all versions(Express, WorkGroup, Standard, Enterprise) and all Service Packs or Microsoft SQL Server
2008 R1 and R2 all versions (Express, WorkGroup, Standard, Enterprise and SP1/SP2).

OracleRecovery
Kit

Oracle 10g Standard Edition, Standard Edition One and Enterprise Edition, Oracle 11g Standard Edition, Standard Edition One and Enterprise Edition, Oracle 11g Release 2.

SteelEye Protection Suite for Windows Release Notes
Page 6

GUI Requirements, Platforms and Browsers

GUI Requirements, Platforms and Browsers
The LifeKeeper GUI server requires that the Java Runtime Environment (JRE) be installed on each server.
The JRE 1.5.0_06 for Windows 2003 and Windows 2008 is installed with the SteelEye Protection Suite Coresoftware. JRE 1.5.0_06 has been fully tested with the LifeKeeper GUI Server. We also support JRE 1.6
versions on the browser, however, the supplied GUI application uses JRE 1.5.0_06. We do not recommend
updating a production server to a newer version of the JRE until it has been fully tested or until you have fully
tested it with the LifeKeeper GUI Server on a machine other than your production server. The update feature
for Java can be disabled by opening the Java Control Panel or by right-clicking on the Java icon located at thebottom right of the screen and choosing Properties then the Update tab. Uncheck the Check for Updates
Automatically option. See the Java upgrade topic for instructions on upgrading Java Runtime Environment(JRE) for SteelEye Protection Suite for Windows.
SteelEye Protection Suite can be administered from a system outside the SteelEye Protection Suite cluster
by running the SteelEye Protection Suite web client. Included in the following table is a list of the supported
platforms and browsers for the SteelEye Protection Suite web client. As in the case of the server, we havetested with JRE 1.5.0_06, but we expect that the client will work equally well with future JRE updates.
Updating the client JRE only affects that machine, so it is not as critical to test for safety as when you are
updating the server JRE. We do recommend that you test updates before committing to them, and that you
prepare to roll them back if a problem occurs.

Operating System

Internet
Explorer 5.5+, 6.0

Windows 2008
Windows 2003

Internet
Explorer
7.0, 8.0

MozillaFirefox 1.5, 2MozillaFirefox 3

X
X

Windows Vista

X

X

X

X

X

X

Windows 2000

X

X

X

Windows NT

X

X

X

Windows 98

X

X

X

Windows XP

X

X

X

X

Linux

N/A

N/A

X

X

Note: Other recent platforms and browsers will likely work with the SteelEye Protection Suite web client, butthey have not been tested by SIOS Technology Corp.

Remote GUI Client Requirements
Included in the table below are the minimum system requirements for a LifeKeeper GUI client running
Windows or Linux.

SteelEye Protection Suite for Windows Release Notes
Page 7

Installing and Removing SteelEye Protection Suite for Windows

Windows

Linux

Windows 95/98, Windows NT 4.0 SP5, Windows ME, Windows XP,
Windows 2000, Windows 2003, Windows 2008

Any Linux distribution that meetsthe requirements below.

Java Plug-in1.5.0-6

Java Plug-in 1.5.0

16-Bit Color Mode

16-Bit Color Mode

Pentium 90 MHz or faster processor

Pentium 90 MHz or faster processor

45 MB free hard disk space

45 MB free hard disk space

Installing and Removing SteelEye Protection Suite forWindows
SteelEye Protection Suite for Windows uses InstallShield to provide a standard installation interface withchoices for Typical, Compact or Custom installation. See the SteelEye Protection Suite Installation Guidefor details about installing, removing or upgrading your SteelEye Protection Suite software.
IMPORTANTl

Customizations made to SteelEye Protection Suite scripts must be reapplied after upgrading to allreleases of SteelEye Protection Suite for Windows v7.

lMake sure you obtain the correct v7 licenses; the old licenses will remain on the system and can bedeleted.

l

SIOS does not support upgrading SteelEye Protection Suite from more than one major version back.
If upgrading from a version prior to LifeKeeper for Windows v6.x to SteelEye Protection Suite forWindows v7.x, uninstall the old version of LifeKeeper and reinstall SteelEye Protection Suite forWindows v7.x.

Technical Notes
lkstartThis program starts LifeKeeper on the current system if it is not currently 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.
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 also be started using the Microsoft Services MMC under Administrative Tools orfrom a command prompt using either “sc start LifeKeeper” or “net start LifeKeeper”.
Note: This program must be run from the console.

SteelEye Protection Suite for Windows Release Notes
Page 8

Running CHKDSK.EXE on SteelEye Protection Suite Protected Volume

Running CHKDSK.EXE on SteelEye Protection Suite Protected Volume
Microsoft recommends running the utility chkdsk.exe to check and correct file system or disk errors on
volumes that have not been cleanly shut down. However, depending on the extent of errors, the utility may
take a very long time to complete. It may take several hours or even days for chkdsk to completely check thevolume, or it may hang while checking the volume. Due to these reasons, SteelEye Protection Suite does not
run the chkdsk utility on protected volumes. SteelEye Protection Suite does run the Microsoft utility
chkntfs.exe to check whether a volume is dirty or not before bringing the volume in service. If a protectedvolume is found dirty, SteelEye Protection Suite will log an error to the event log.
It is recommended that administrators periodically run chkdsk on SteelEye Protection Suite protectedvolumes on the server where the volume resource(s) are in service. Administrators should take all theapplications using the volume resource(s) out-of-service prior to running chkdsk.

Running CHKDSK.EXE During System Boot
SteelEye Protection Suite protected volumes are typically not eligible for the chkdsk utility to run on them atsystem boot time because LifeKeeper and DataKeeper need to be able to lock the volumes. If a SteelEye
Protection Suite protected volume needs to be checked at boot time, the steps below can be performed on theactive node.
For Mirrored Volumes or SDRS Volumes (shared at one site, replicated to a remote site)
1. "%ExtMirrBase%\emcmd" . getconfiguration <drv> (save the number reported on the firstline of output for later use after reboot)2. "%ExtMirrBase%\emcmd" . setconfiguration <drv> 32
3. "%LKBIN%\lkstop" -f
4. sc stop ExtMirrSvc
5. sc config lifekeeper start= demand
6. sc config ExtMirrSvc start= demand
7. chkntfs /D
8. chkntfs /c <drv>
9. rebootPerform the following steps after reboot.
10. sc config lifekeeper start= auto
11. sc config ExtMirrSvc start= auto
12. sc start ExtMirrSvc
13. "%ExtMirrBase%\emcmd" . setconfiguration <drv> (number reported by emcmd
getconfiguration in step 1).
14. reboot

SteelEye Protection Suite for Windows Release Notes
Page 9

Communication Paths Over Fibre Channel

For Shared Volumes
1. "%LKBIN%\volume" -U <drv>2. "%LKBIN%\lkstop" -f
3. chkntfs /c <drv>
4. rebootPerform following steps after reboot.
5. "%LKBIN%\volume" -p <drv>
6. "%LKBIN%\lkstop" -f
7. "%LKBIN%\lkstart"
For Replicated Volumes
1. "%LKBIN%\lkstop" -f
2. chkntfs /D
3. chkntfs /c <drv>
4. rebootCommunication Paths Over Fibre Channel
When building a SteelEye Protection Suite cluster using shared storage, it is important to maintain working
communication paths between the nodes in the cluster. Communication paths should be created using TCP
communication protocols. Normally, TCP communication paths are built on Ethernet network devices.
SteelEye Protection Suite, however, can use any type of connection on which the TCP protocol can run. If ashared storage cluster is being created using a Fibre Channel SAN, it is possible (and desirable) to use theFibre Channel SAN as a SteelEye Protection Suite communication path.
QLogic provides a miniport driver and an IP driver for Windows that will allow a QLogic Fibre Channel storage
adapter to also run the TCP/IP protocol. This, in effect, allows the QLogic Fibre Channel adapter to function
both as a storage adapter and as a network adapter. Once this driver is in place, the QLogic card can be
configured, as any network card would, using standard network configuration techniques.
QLogic’s driver can be downloaded from the following web site:
http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/DefaultNewSearch.aspx

Using iSCSI Storage with SteelEye Protection SuiteiSCSI storage can be used as shared storage and protected by SteelEye Protection Suite. For shared storage
environments, the iSCSI target device must be configured so that all server initiators have access to the disk.
The vendor of the iSCSI storage device provides the interface and commands needed to configure the iSCSI
device. A dependency on the Microsoft iSCSI Initiator service (MSiSCSI) should be added to the LifeKeeper
service. This will ensure that the shared volume is available before LifeKeeper attempts to access thevolume.

SteelEye Protection Suite for Windows Release Notes
Page 10IXS Processor Card in an IBM® System i™ (iSeries™) Server

To create a dependency on MSiSCSI for the LifeKeeper service, use the registry editor “regedt32.exe” andselect the subkey representing the LifeKeeper service under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LifeKeeper. The service key has a value name
"DependOnService" with one value "EISM". Double-click the value name "DependOnService" to open
for editing. When the dialog box appears, add the service name "MSiSCSI" for Microsoft iSCSI Initiator
service on a new line and click OK.
To verify that the dependency was created, open Administrative Tools->Services MMC snap-in. Go to
LifeKeeper service and double-click to bring up the "Properties" dialog. When the dialog box appears, go to"Dependencies" page and verify that "Microsoft iSCSI Initiator" service is listed along with "LifeKeeper
External Interface" in the "depends on" field.

IXS Processor Card in an IBM® System i™ (iSeries™) Server
SteelEye Protection Suite for Windows Core is certified to run on an IXS (Integrated xSeries Server) card on
IBM System i servers with SteelEye DataKeeper. There is no support for shared storage configurations at thistime. See IBM’s website for more information on the IXS card configurations:
http://www-03.ibm.com/systems/i/advantages/integratedserver/ixa/solution_guide.html

System Load Considerations for Quickcheck and Deepcheck
SteelEye Protection Suite launches a separate thread to monitor each protected resource in the system.
These threads operate independently of one another. Typically, system load from Quickcheck andDeepcheck script execution will be randomly distributed. SteelEye Protection Suite also works todistribute resource monitoring load by skipping a Quickcheck execution whenever a Deepcheck for thesame resource is scheduled to run at the same time. However, because the check load is randomly
distributed, there will occasionally be peaks in system load from resource monitoring. The more protectedresources in the system, the larger these peaks will be and the more often they may occur. The largest peak
will occur when LifeKeeper is started and Deepcheck scripts for each active resource are first launched. If
the server can handle this first load peak in a satisfactory way, then there should not be a performance
problem later.

VSS Shadow Copy
SteelEye Protection Suite support for VSS Shadow Copy requires that shadow copies must NOT be stored
on the SteelEye Protection Suite protected volumes. However, shadow copies may be saved on another nonprotected volume. Note: SteelEye Protection Suite does not support VSS Shadow Copy on Server 2003 or
2003 R2.

Restrictions and Known Issues
Restrictions
SCVMM 2012
If using DataKeeper with SCVMM 2012, you must use SCVMM 2012 SP1.

SteelEye Protection Suite for Windows Release Notes
Page 11

Enterprise or DataCenter Server with Microsoft Failover Cluster Installed

Enterprise or DataCenter Server with Microsoft Failover Cluster Installed
SteelEye Protection Suite is not supported on Enterprise or DataCenter class servers with Microsoft Cluster
Server or Microsoft Failover Cluster features installed. It should never be the case that two “Clustering”
solutions are deployed on the same group of servers. As part of this restriction, SteelEye Protection Suite
communication paths will not function using IP addresses (169.254.xxx.xxx) that are hosted by the Microsoft
Failover Cluster Virtual Adapters (Virtual NICs).

Exchange 2007 Circular Logging and Rewind
The SteelEye Protection Suite Rewind feature is not supported if Circular Logging is enabled in Microsoft
Exchange 2007 Server. This restriction is a result of the way Exchange overwrites its log files when circularlogging is enabled, which interferes with SteelEye Protection Suite's ability to calculate a consistent rewind
point.

FAT File System Support
SteelEye Protection Suite does not support protection for volumes using the FAT or FAT32 file systems.

Fault Tolerant Disk Sets
While SteelEye Protection Suite replicated volumes are supported using Windows fault tolerant disk sets
(Software RAID), SteelEye Protection Suite shared volumes are not compatible with Windows fault tolerant
disk sets. Fault tolerant disk sets must be set up with dynamic disks and dynamic disks cannot be shared
between two systems.

File Share Recovery Kitl

The File Share Recovery Kit is supported only in an Active Domain environment, not in a Workgroupenvironment. File share permissions granted to local machine accounts, either in a workgroupenvironment or a domain environment, will not be preserved during failover because local User IDs
are valid only on the local system where they originated; other systems will not recognize them. Even if
two local User IDs are spelled the same way on two different machines, they will be treated as
two different accounts and valid only on the system where they originated. Domain accounts, on theother hand, are identifiable and usable on any system in the domain.

l

The File Share Recovery Kit will not work if more than 9999 file shares are defined on the system. Any
attempt to protect eligible file shares under SteelEye Protection Suite will fail if the total number ofuser-defined shares exceeds 9999. This restriction also applies to editing file share resources. You will
not be able to alter the list of protected shares if more than 9999 shares are defined on the system.

LAN Manager Recovery Kit
Microsoft supports LAN Manager functions only over the first IP address per network interface card (Microsoft
bug SRX#9704116-48). This prohibits using LAN Manager functions over SteelEye Protection Suite protected
IP addresses. Therefore, the only way to switch over an alias computer name using the TCP/IP protocol is toallow dynamic IP#-to-LAN Manager name mapping for your clients. The recommended solution is to use a
WINS server. You will need to make the SteelEye Protection Suite servers (and all computers accessing theprotected LAN Manager name) WINS clients of the same WINS server.

SteelEye Protection Suite for Windows Release Notes
Page 12

Low Virtual Memory Degrades System State

Low Virtual Memory Degrades System State
SteelEye Protection Suite depends on memory being available when it is needed. If your system is reportingthat it is low on virtual memory, that need must be resolved immediately.
A virtual memory shortage serious enough to degrade or delay communications and other internal system
functions will very likely cause SteelEye Protection Suite to malfunction. For instance, deepcheck of
TCP/IP communication resources may be impacted enough to cause a false failure, and thus a failover of theresource to the backup server.
If SteelEye Protection Suite communication with other servers in the cluster is degraded, it could cause amanually initiated switchover to fail. However, this will not affect SteelEye Protection Suite’s ability to failover protected resources when a server completely fails.

GUI interoperability
The LifeKeeper GUI may only be used to administer SteelEye Protection Suite on Windows servers. Notethat you can connect to and monitor a SteelEye Protection Suite for Linux cluster. However, performing
administrative tasks such as creating resources, editing properties, bringing servers in and out of service, is
not supported at this time.

Discontinuing Serial Port Communication Paths
SteelEye Protection Suite discontinued support for TTY communication paths in Version 7.2. Though SIOS
does not recommend it, if currently using TTY communication paths, this option can be re-enabled byremoving the (#) symbol on the TTYCA.EXE line in the /etc/lkinit.config file as shown below:# … /bin/TTYCA.EXE|-t 1 X X X X X X(TTY Comm Paths Disabled)… /bin/TTYCA.EXE|-t 1 X X X X X X(TTY Comm Paths Enabled)<=<=

To enable or disable the TTY communication path feature, the LifeKeeper service must be stopped andrestarted after editing lkinit.config. To stop LifeKeeper, run command {c:\lk}\bin\lkstop.exe –f (c:\lk being the LifeKeeper installation path). Make sure the GUI is closed and all processes associatedhave stopped. Restart LifeKeeper by entering {c:\lk}\bin\lkstart.exe.
The TTY technology is obsolete. TTY communication paths are not supported and should be replaced with
TCP/IP communication paths.

Console Application Management
Launching console applications from SteelEye Protection Suite is not supported on Windows Server 2008 and2008 R2. Server architecture and security improvements in Server 2008 and 2008 R2, including UAC andmemory management, prevent background processes such as SteelEye Protection Suite fromstarting console applications.

Bitlocker Does Not Support DataKeeper
According to Microsoft, Bitlocker is not supported to work with Software RAID configurations. Since
DataKeeper is essentially a software RAID 1, Microsoft does not support Bitlocker working with DataKeeper.

SteelEye Protection Suite for Windows Release Notes
Page 13Known Issues

The specific article and section can be found here:
http://technet.microsoft.com/en-us/library/ee449438#BKMK_R2disks

Known Issues
For additional known issues, see the Troubleshooting section of SteelEye Protection Suite for Windows
Technical Documentation.

Frequently Asked Questions
Can I change my SteelEye Protection Suite configuration database setting including resource values
without reinstalling SteelEye Protection Suite or rebuilding my resources?
Yes. Use the lk_chg_value.ksh command.
Can I upgrade my existing SteelEye Protection Suite hierarchies from a previous version of
SteelEye Protection Suite for Windows to v7?
You may upgrade your existing SteelEye Protection Suite for Windows software while preserving yourresource hierarchies. Please refer to the Upgrading SteelEye Protection Suite topic for the correct upgrade
procedure. Note: SIOS does not support upgrading SteelEye Protection Suite from more than one major
version back. If upgrading from a version prior to LifeKeeper for Windows v6.x to SteelEye Protection Suite forWindows v7.x, uninstall the old version of LifeKeeper and reinstall SteelEye Protection Suite for Windows
v7.x.
Does SteelEye Protection Suite operate in a cluster with Microsoft Cluster Services (Windows 2003)
or Windows Server Failover Cluster (Windows 2008)?
No. SteelEye Protection Suite does not support any Cluster Server APIs. Instead, all MSCS nodes may be
upgraded to SteelEye Protection Suite.
Does SteelEye Protection Suite require that all servers in the cluster be identically configured?
No. As long as all servers are powerful enough to run any application that may run on them as the result of a
failover operation and meet all other SteelEye Protection Suite requirements, a cluster can be built. SteelEye
Protection Suite does not require identical hardware, but the software should be the same and configured withthe same service pack levels.
Does SteelEye Protection Suite for Windows support 64-bit environments?
Yes. SteelEye Protection Suite for Windows supports both 32-bit and 64-bit platforms.
How do I change permissions on SteelEye Protection Suite protected File Share resources?
The EditFileShareResource utility can be used to update a file share resource with all current file sharesand permissions on the associated volume(s). This can be useful in environments where there are a large
number of file shares, and file shares have been added or deleted since the resource was created or
permissions have been modified. Using the utility can prevent the need to delete and re-create the file shareresource. The EditFileShareResource utility is located under %LKROOT%\bin directory.
To invoke the utility, on the command line enter:

SteelEye Protection Suite for Windows Release Notes
Page 14Documentation

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 volumes that are associated with the file sharehierarchy. 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 definedon the file share.

Documentation
A complete reference providing instructions for installing, configuring, administering and troubleshooting
SteelEye Protection Suite for Windows is available in the SteelEye Protection Suite for Windows TechnicalDocumentation. The following sections cover every aspect of SteelEye Protection Suite for Windows:

SectionDescription

Introduction

Provides an introduction to the SteelEye Protection Suite for Windows product, including
an overview of its components.

Installation

Provides useful information for planning and setting up your SteelEye Protection Suiteenvironment, installing and licensing SteelEye Protection Suite and configuring the
LifeKeeper GUI to run on a remote system.

Configuration

Contains detailed information and instructions for configuring the SteelEye Protection
Suite software on each server in your cluster.

Administration

Discusses server-level tasks such as editing server properties, creating resources andcreating or deleting comm paths and resource-level tasks such as editing, extending ordeleting resources.

Man Pages

Provides reference manual pages for the SteelEye Protection Suite product.

User's Guide

Contains detailed information on the LifeKeeper GUI, including the many tasks that canbe performed within the LifeKeeper GUI. Also includes information on Data Replication
along with many more Advanced Topics.

DataKeeper

Provides an overview of how DataKeeper replication works and contains complete information on configuring and administering DataKeeper. Topics include network considerations, common configuration issues and requirements necessary to successfully
install and configure DataKeeper.

Troubleshooting

Describes known issues and suggests solutions to problems that may be encounteredduring installation, configuration or use of SteelEye Protection Suite for Windows.

Recovery Kits

Contains planning and installation instructions as well as administration, configuration
and user information for the Optional Recovery Kits (SQL Server and Oracle) that allow
LifeKeeper to manage and control specific applications.

Also available is the SteelEye Disaster Recovery Solution configuration information which provides theinformation necessary to properly configure a hybrid shared/replicated storage cluster where two nodes share

SteelEye Protection Suite for Windows Release Notes
Page 15

Quick Start Guides

a common storage array while at the same time replicate to an additional node across the WAN for disasterrecovery purposes.

Quick Start Guides
To get started using SteelEye Protection Suite for Windows, refer to the SteelEye Protection Suite forWindows Quick Start Guide and the DataKeeper Quick Start Guide.

Training
SteelEye Protection Suite training is available through SIOS Technology Corp. or through your SteelEye
Protection Suite provider. Contact your sales representative for more information.

Technical Support
As a SIOS Technology Corp. customer with a valid Support contract, you are entitled to access the SIOS
Technology Corp. Support Self-Service Portal.
The SIOS Technology Corp. Support Self-Service Portal offers you the following capabilities:l

Search our Solution Knowledge Base to find solutions to problems and answers to questionsl

Always on 24/7 service with the SIOS Technology Corp. Support team to:l

Log a Case to report new incidents.

lView Cases to see all of your open and closed incidents.

l

Review Top Solutions providing information on the most popular problem resolutions
being viewed by our customers.

Contact SIOS Technology Corp. Support at support@us.sios.com to set up and activate your Self-Service
Portal account.
You can also contact SIOS Technology Corp. Support at:
1-877-457-5113 (Toll Free)
1-803-808-4270 (International)
Email: support@us.sios.com

SteelEye Protection Suite for Windows Release Notes
Page 16