Novell BUSINESS CONTINUITY CLUSTERING 1.0 -... User manual

Novell
www.novell.com
novdocx (ENU) 10 August 2006
Novell Business Continuity Cluster Services 1.0 Administration Guide
Business Continuity Clustering
1.0
May 22, 2006
ADMINISTRATION GUIDE

novdocx (ENU) 10 August 2006
Legal Notices
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
You may not use, export, or re-export this product in violation of any applicable laws or regulations including,
without limitation, U.S. export regulations or the laws of the country in which you reside.
Copyright © 2005 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903; 5,633,931;
5,652,854; 5,671,414; 5,677,851; 5,692,129; 5,701,459; 5,717,912; 5,758,069; 5,758,344; 5,781,724; 5,781,733;
5,784,560; 5,787,439; 5,818,936; 5,828,882; 5,832,274; 5,832,275; 5,832,483; 5,832,487; 5,859,978; 5,870,561;
5,870,739; 5,873,079; 5,878,415; 5,884,304; 5,893,118; 5,903,650; 5,903,720; 5,905,860; 5,910,803; 5,913,025;
5,913,209; 5,915,253; 5,925,108; 5,933,503; 5,933,826; 5,946,002; 5,946,467; 5,956,718; 5,956,745; 5,964,872;
5,974,474; 5,983,223; 5,983,234; 5,987,471; 5,991,810; 6,002,398; 6,014,667; 6,016,499; 6,023,586; 6,029,247;
6,052,724; 6,061,726; 6,061,740; 6,061,743; 6,065,017; 6,081,774; 6,081,814; 6,094,672; 6,098,090; 6,105,062;
6,105,069; 6,105,132; 6,115,039; 6,119,122; 6,144,959; 6,151,688; 6,157,925; 6,167,393; 6,173,289; 6,216,123;
6,219,652; 6,233,859; 6,247,149; 6,269,391; 6,286,010; 6,308,181; 6,314,520; 6,324,670; 6,338,112; 6,345,266;
6,353,898; 6,424,976; 6,466,944; 6,477,583; 6,477,648; 6,484,186; 6,496,865; 6,510,450; 6,516,325; 6,519,610;
6,532,451; 6,532,491; 6,539,381; 6,560,615; 6,567,873; 6,578,035; 6,591,397; 6,609,158; 6,615,350; 6,629,105;
6,629,132; 6,647,408; 6,651,242 & RE37,178. Patents Pending.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
October 25, 2005
To access the online documentation for this and other Novell products, and to get updates, see www.novell.com/
documentation.

novdocx (ENU) 10 August 2006
Novell Trademarks
ConsoleOne is a registered trademark of Novell, Inc. in the United States and other countries.
DirXML is a registered trademark of Novell, Inc. in the United States and other countries.
eDirectory is a trademark of Novell, Inc.
Hot Fix is a trademark of Novell, Inc.
iChain is a registered trademark of Novell, Inc. in the United States and other countries.
NetWare is a registered trademark of Novell, Inc. in the United States and other countries.
NetWare Core Protocol and NCP are trademarks of Novell, Inc.
Netware Loadable Module and NLM are trademarks of Novell, Inc.
Novell is a registered trademark of Novell, Inc. in the United States and other countries.
Novell Authorized Reseller is a service mark of Novell, Inc.
Novell Client is a trademark of Novell, Inc.
Novell Cluster Services is a trademark of Novell, Inc.
Novell Directory Services and NDS are registered trademarks of Novell, Inc. in the United States and other countries.
Novell Storage Services is a trademark of Novell, Inc.
ZENworks is a registered trademark of Novell, Inc. in the United States and other countries.
Third-Party Materials
All third-party trademarks are the property of their respective owners.

novdocx (ENU) 10 August 2006

Contents 5
Contents
novdocx (ENU) 10 August 2006
About This Guide 7
1Overview 9
1.1 Disaster Recovery Implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Disaster Recovery Implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2.1 Stretch Clusters vs. Cluster of Clusters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2.2 Novell Business Continuity Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2.3 Usage Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2 Installation and Setup 17
2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2 Installing the DirXML 1.1a Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3 Installing the DirXML 1.1a Management Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.3.1 Installing the DirXML Management Utilities on a NetWare Server . . . . . . . . . . . . . . 19
2.3.2 Installing the DirXML Management Utilities on a Windows Server . . . . . . . . . . . . . . 21
2.4 Installing DirXML 2.01 (Identity Manager 2.01) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.5 Copying User Objects Using DirXML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.6 Installing Novell Business Continuity Cluster Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.6.1 Business Continuity Cluster Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.6.2 Running the Business Continuity Cluster Installation Program . . . . . . . . . . . . . . . . . 23
2.6.3 Business Continuity Cluster Component Locations . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.7 Installing Perl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.8 Configuring File System Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.8.1 Configuring NSS Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.8.2 LUN Masking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.9 Setting Up Novell Business Continuity Cluster Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.9.1 Ensuring that Clusters and Trees are Resolvable. . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.9.2 Configuring Business Continuity-Specific DirXML Drivers . . . . . . . . . . . . . . . . . . . . 29
2.9.3 Configuring Clusters for Business Continuity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
2.9.4 Configuring Cluster Resources for Business Continuity . . . . . . . . . . . . . . . . . . . . . . 36
2.10 Managing Novell Business Continuity Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.10.1 Migrating a Cluster Resource to Another Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.10.2 Changing Cluster Peer Credentials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.10.3 Viewing the Current Status of a Business Continuity Cluster . . . . . . . . . . . . . . . . . . 41
2.10.4 Generating a Cluster Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.10.5 Disabling Business Continuity Cluster Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.10.6 Business Continuity Cluster Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.11 Business Continuity Cluster Failure Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.11.1 San-based Mirroring Failure Types and Responses . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.11.2 Host-based Mirroring Failure Types and Responses . . . . . . . . . . . . . . . . . . . . . . . . 45
3 Virtual IP Addresses 47
3.1 Virtual IP Address Definitions and Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.1.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.1.2 Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.2 Virtual IP Address Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.2.1 High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

6Novell Business Continuity Cluster Services 1.0 Administration Guide
novdocx (ENU) 10 August 2006
3.2.2 Unlimited Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.3 Other Added Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.3.1 Support for Host Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.3.2 Source Address Selection for Outbound Connections . . . . . . . . . . . . . . . . . . . . . . . . 51
3.4 Reducing the Consumption of Additional IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.5 Configuring Virtual IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.5.1 Displaying Bound Virtual IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

About This Guide
novdocx (ENU) 10 August 2006
7
About This Guide
This guide describes how to install, configure, and manage Novell® Business Continuity Clustering.
The guide is intended for cluster administrators and is divided into the following sections:
Chapter 1, “Overview,” on page 9
Chapter 2, “Installation and Setup,” on page 17
Chapter 3, “Virtual IP Addresses,” on page 47
Documentation Conventions
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items
in a cross-reference path.
A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as UNIX*, should use forward slashes as required by your software.

8Novell Business Continuity Cluster Services 1.0 Administration Guide
novdocx (ENU) 10 August 2006

Overview
1
novdocx (ENU) 10 August 2006
9
1
Overview
As corporations grow more international, fueled in part by the reach of the World Wide Web, the
requirement for service availability has increased. Novell® Cluster Services™ offers corporations
the ability to maintain 24x7x365 data and application services to their users while still being able to
perform maintenance and upgrades on their systems.
In the past few years, natural disasters (ice storms, earthquakes, tornadoes, and fires) have caused
unplanned outages of entire data centers. In addition, US federal agencies have realized the
disastrous effects that terrorist attacks could have on the US economy when corporations lose their
data and the ability to perform critical business practices. This has resulted in initial
recommendations for corporations to build mirrored or replicated data centers that are
geographically separated by 300 km or more (minimum acceptable being 200 km).
Many companies have built and deployed geographically mirrored data centers. The problem is that
setting up and maintaining the two or more centers is a very manual process that takes a great deal of
planning and synchronizing. Even configuration changes have to be carefully planned and
replicated. One mistake and the redundant site is no longer able to effectively take over in the event
of a disaster.
1.1 Disaster Recovery Implications
The implications of disaster recovery are directly tied to your data. Is your data mission critical? In
many instances, critical systems and data drive the business. If these services stop, the business
stops. When calculating the cost of downtime, some things to consider are
File transfers and file storage
Calendaring and collaboration
Web hosting
Critical databases
Productivity
Reputation
Continuous availability of critical business systems is no longer a luxury, it is a competitive business
requirement.The Gartner Group estimates that 40% of enterprises that experience a disaster will go
out of business in five years and only 15% of enterprises have a full-fledged business continuity plan
that goes beyond core technology and infrastructure.
1.2 Disaster Recovery Implementations
There are two main Novell Cluster Services implementations that you can use to achieve your
desired level of disaster recovery. These include a stretch cluster and a cluster of clusters. The
Novell Business Continuity Cluster product automates some of the configuration and processes used
in a cluster of clusters.

10 Novell Business Continuity Cluster Services 1.0 Administration Guide
novdocx (ENU) 10 August 2006
1.2.1 Stretch Clusters vs. Cluster of Clusters
Stretch Clusters
A stretch cluster consists of one cluster in which the nodes in the cluster are located in
geographically separate areas. All nodes in the cluster must be in the same eDirectory™ tree. In this
architecture, the data is mirrored between two data centers that are geographically separated. All the
machines in both data centers are part of one cluster, so that if a disaster occurs in one data center,
the other automatically takes over.
Figure 1-1 Stretch Cluster
Cluster of Clusters
A cluster of clusters consists of two or more clusters in which each cluster is located in a
geographically separate area. A cluster of clusters provides the ability to fail over selected or all
cluster resources from one cluster to another cluster. Typically, replication of data blocks between
Server 6 Server 7Server 5 Server 8
Fibre Channel
Switch
Building A Building B
Server 2 Server 3Server 1 Server 4
Fibre Channel
Switch
Fibre Channel
Disk Array
Disk blocks
WAN
Cluster
Heartbeat
8-node cluster stretched
between two sites
Site 2
SAN
Site 1
Ethernet Switch Ethernet Switch
Fibre Channel
Disk Array

Overview 11
novdocx (ENU) 10 August 2006
SANs is performed by SAN hardware, but it can be done by host-based mirroring for synchronous
replication over short distances.
Figure 1-2 Cluster of Clusters
Server
2B
Server
3B
Server
1B
Server
4B
Fibre Channel
Switch
Fibre Channel
Disk Arrays
Building A Building B
Server
2A
Ethernet Switch
Server
3A
Server
1A
Server
4A
Fibre Channel
Switch
Fibre Channel
Disk Arrays
Disk blocks
Ethernet Switch
WAN
eDirectory
DirXML
Two independent clusters at
geographically separate sites
Cluster Site 2
SAN
Cluster Site 1

12 Novell Business Continuity Cluster Services 1.0 Administration Guide
novdocx (ENU) 10 August 2006
Implementation Comparison
Table 1-1 Disaster Recovery Implementation Comparison
Stretch Cluster Cluster of Clusters
Advantages It automatically fails over.
It is easier to manage than
separate clusters.
The chance of LUNs at both
locations becoming primary is
minimized.
eDirectory partitions don't need
to span the cluster.
Each cluster can be in a
separate eDirectory tree.
IP addresses for each cluster
can be on different IP subnets.
It accommodates more than two
sites and cluster resources can
fail over to separate clusters
(multiple-site fan-out failover
support).
SBD partitions are not mirrored
between sites.
Disadvantages Failure of site interconnect can
result in LUNs becoming primary
at both locations (split brain
problem) if host-based mirroring
is used.
An SBD partition must be
mirrored between sites.
It accommodates only two sites.
All IP addresses must reside in
the same subnet.
The eDirectory partition must
span the cluster.
Resource configurations must be
kept in sync manually.

Overview 13
novdocx (ENU) 10 August 2006
1.2.2 Novell Business Continuity Clusters
Novell Business Continuity Clusters is a cluster of clusters similar to what is described above,
except that the cluster configuration, maintenance, and synchronization have been automated by
adding specialized software.
Novell Business Continuity Clustering software is an integrated set of tools to automate the setup
and maintenance of a Business Continuity infrastructure. Unlike competitive solutions that attempt
to build stretch clusters, Novell Business Continuity Clustering utilizes a cluster of clusters. Each
site has its own independent cluster(s), and the clusters in each of the geographically separate sites
are each treated as "nodes" in a larger cluster, allowing a whole site to fan-out failover to other
multiple sites. Although this can currently be done manually with a cluster of clusters, Novell
Business Continuity Clustering automates the system using eDirectory and policy-based
management of the resources and storage systems.
Novell Business Continuity Clustering software
Integrates with SAN hardware devices to automate the failover process.
Utilizes Novell's DirXML® technology to automatically synchronize and transfer cluster-
related eDirectory objects from one cluster to another.
Provides the capability to fail over as few as one cluster resource, or as many as all cluster
resources.
Includes a test mode that lets you do site failover testing as a standard practice.
Other Considerations Host-based mirroring is required
to mirror the SBD partition
between sites.
Link variations can cause false
failovers.
You could consider partitioning
the eDirectory tree to place the
cluster container in a partition
separate from the rest of the
tree.
The cluster heartbeat must be
increased to accommodate link
latency between sites.
You can set this as high as 30
seconds, monitor cluster
heartbeat statistics, and then
tune down as needed.
Because all IP addresses in the
cluster must be on the same
subnet, you must ensure that
your routers handle gratuitous
ARP.
Contact your router vendor or
consult your router
documentation for more
information.
Storage arrays must be
controllable by scripts that run on
NetWare.
Stretch Cluster Cluster of Clusters

14 Novell Business Continuity Cluster Services 1.0 Administration Guide
novdocx (ENU) 10 August 2006
Provdes scripting capability for enhanced control and customization.
Provides simplified business coninuity cluster configuration and management using the
browser-based iManager management tool.
1.2.3 Usage Scenarios
There are several Business Continuity Clustering usage scenarios that can be used to achieve the
desired level of disaster recovery. Three possible scenarios include:
A simple two-site Business Continuity Cluster
A multiple-site Business Continuity Cluster
A low-cost Business Continuity Cluster
Two-Site Business Continuity Cluster Solution
The two-site solution can be used in one of two ways:
A primary site in which all services are normally active, and a secondary site which is
effectively idle, with the data mirrored at it and the applications/services ready to load if
needed.
Two active sites each supporting different applications/services. Either site can take over for
the other site at any time.

Overview 15
novdocx (ENU) 10 August 2006
The first option is typically used when the purpose of the secondary site is primarily testing by the
IT department. The second option is typically used in a company that has more than one large site of
operations.
Figure 1-3 Two Site Business Continuity Cluster
Multiple-Site Business Continuity Cluster Solution
This is a large Business Continuity Cluster solution capable of supporting up to 32 nodes per site
and more than two sites. Services and applications can do fan-out failover between sites. Replication
of data blocks is typically done by SAN vendors, but can be done by host-based mirroring for
Server
2B
Server
3B
Server
1B
Server
4B
Fibre Channel
Switch
Fibre Channel
Disk Arrays
Building A Building B
Server
2A
Ethernet Switch
Server
3A
Server
1A
Server
4A
Fibre Channel
Switch
Fibre Channel
Disk Arrays
Disk blocks
Ethernet Switch
WAN
eDirectory
DirXML
Two independent clusters at
geographically separate sites
Cluster Site 2
SAN
Cluster Site 1

16 Novell Business Continuity Cluster Services 1.0 Administration Guide
novdocx (ENU) 10 August 2006
synchronous replication over short distances. The illustration below depicts a four-site business
continuity cluster.
Figure 1-4 Multiple Site Business Continuity Cluster
Using Novell’s Portal Services, iChain®, and ZENworks® products, all services, applications, and
data can be rendered through the internet, allowing for loss of service at one site but still providing
full access to the services and data by virtue of the ubiquity of the internet. Data and services
continue to be available from the other mirrored sites. Moving applications and services to the
Internet frees corporations from the restrictions of traditional LAN-based applications. Traditional
LAN applications require a LAN infrastructure that must be replicated at each site, and might
require relocation of employees to allow the business to continue. Internet-based applications allow
employees to work from any place that offers an internet connection, including homes and hotels.
Low Cost Business Continuity Cluster Solution
The low cost business continuity cluster solution is similar to the previous two solutions, but
replaces Fibre Channel arrays with iSCSI arrays. Data block mirroring can be accomplished using
iSCSI-based block replication. In this case, snapshot technology can allow for asynchronous
replication over long distances. However, the lower cost solution does not necessarily have the
performance associated with higher-end Fibre Channel storage arrays.
Server
2D
Server
3D
Server
1D
Server
4D
Fibre Channel
Switch
Fibre Channel
Disk Arrays
Building D
Ethernet Switch
Server
2C
Server
3C
Server
1C
Server
4C
Fibre Channel
Switch
Fibre Channel
Disk Arrays
Building C
Ethernet Switch
Server
2B
Server
3B
Server
1B
Server
4B
Fibre Channel
Switch
Fibre Channel
Disk Arrays
Building A Building B
Server
2A
Ethernet Switch
Server
3A
Server
1A
Server
4A
Fibre Channel
Switch Disk blocks
Ethernet Switch
WAN
eDirectory
DirXML
Four independent clusters in
geographically separate sites
Cluster Sites 2
,
3
,
and 4
SAN
Cluster Site 1
Fibre Channel
Disk Arrays

Installation and Setup
2
novdocx (ENU) 10 August 2006
17
2
Installation and Setup
This section covers the following information to help you install, set up, and configure Novell®
Business Continuity Clustering for your specific needs:
“Requirements” on page 17
“Installing the DirXML 1.1a Engine” on page 18
“Installing the DirXML 1.1a Management Utilities” on page 19
“Copying User Objects Using DirXML” on page 22
“Installing Novell Business Continuity Cluster Software” on page 22
“Installing Perl” on page 25
“Configuring File System Mirroring” on page 25
“Setting Up Novell Business Continuity Cluster Software” on page 29
“Managing Novell Business Continuity Clustering” on page 39
“Business Continuity Cluster Failure Types” on page 43
2.1 Requirements
The following requirements must be met prior to installing Novell Business Continuity Cluster
software.
NetWare® 6.5 Support Pack 2 or later installed and running on all servers that will be part of a
business continuity cluster.
See the NetWare 6.5 Overview and Installation Guide for information on installing and
configuring NetWare 6.5.
Two to four clusters with Novell Cluster Services™ 1.7 (the version that ships with NetWare
6.5 Support Pack 1) or later installed and running on each node in the cluster.
Each cluster must have a unique name, even if the clusters reside in different Novell
eDirectory™ trees, and clusters must not have the same name as any of the eDirectory trees in
the business continuity cluster.
See the Novell Cluster Services 1.7 Administration Guide for information on installing and
configuring Novell Cluster Services.
NOTE: The hardware requirements for Novell Business Continuity Cluster software are the
same as for Novell Cluster Services. For more information, see Hardware Requirements and
Shared Disk System Requirementsin the Novell Cluster Services 1.7 Administration Guide.
NOTE: Some SAN vendors require you to purchase or license their CLI (Command Line
Interface) separately. The CLI for the SAN might not initially be included with your hardware.
The following software modules upgraded on all servers that will be part of the business
continuity cluster:
DSLOADER.NLM--See TID # 2973090 (http://support.novell.com/cgi-bin/search/
searchtid.cgi?/2973090.htm) to download this NLM. It is included with the eDirectory patch.

18 Novell Business Continuity Cluster Services 1.0 Administration Guide
novdocx (ENU) 10 August 2006
LIBC.NLM--See TID # 2973643 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/
2973643.htm) to download this NLM.
WINSOCK Suite--See TID # 2971768 (http://support.novell.com/cgi-bin/search/
searchtid.cgi?/2971768.htm) to download this suite. This patch is not needed if you have
installed OES NetWare or NetWare 6.5 SP 3.
DirXML 1.1a Patch--See TID # 2966617 (http://support.novell.com/cgi-bin/search/
searchtid.cgi?/2966617.htm) to download this patch. This patch is not needed for IDM 2.0.x.
For real time mirroring, link speeds should be 1 GB or better, the distance between sites should
be less than 200 kilometers, and the links should be dedicated.
Many factors should be considered for distances greater than 200 kilometers, some of which
include:
The distance between sites
The amount of data being transferred
The bandwidth of the link
Whether or not snapshot technology is being used
2.2 Installing the DirXML 1.1a Engine
DirXML® 1.1a or later must be installed on one node in each cluster. DirXML 1.1a is part of the
DirXML Starter Pack that is included with NetWare 6.5. The node where DirXML is installed must
have an eDirectory replica with at least read/write access to all eDirectory objects that will be
synchronized between clusters. This does not apply to all eDirectory objects in the tree.
NOTE: Filtered eDirectory replicas are not supported with this version of Business Continuity
Cluster software. Full replicas are required.
IMPORTANT: The eDirectory replica must have at least read/write access to the following
containers.
The container where the DirXML drivers are located.
The container where the cluster object resides.
The parent container of the container where the server objects reside.
The container where the cluster pool and volume objects will be placed when they are
synchronized to this cluster.
If the eDirectory replica does not have read/write access to the containers listed above,
synchronization will not work properly.
IMPORTANT: If you downloaded NetWare 6.5, DirXML 1.1a might not be included with the
download. You may have to download it separately.
Instructions for installing the DirXML Starter Pack are provided here. For additional information on
installing and configuring DirXML, see the DirXML 1.1a Administration Guide (http://
www.novell.com/documentation/dirxml11a/dirxml/data/a2iii88.html).
To install the DirXML Starter Pack:
1At the NetWare 6.5 server, insert the DirXML CD into the CD drive.

Installation and Setup 19
novdocx (ENU) 10 August 2006
2At the GUI server console, click Novell > Install and then click Add.
If the GUI server console isn't running, launch it by entering STARTX at the console.
3In the Path to Install From field, browse to and select nw\product.ni on the DirXML CD and
then click OK twice.
4On the DirXML Product Installation page, click Next.
5Read the license agreement; if you agree to the terms, click I Accept.
6On the Components page, mark DirXML Engine and Drivers, then click Next.
7On the Schema Extension page, enter the following information and then click Next:
User Name: Specify the context of a user who has rights to extend the schema, for
example, CN=admin.O=hq.
User Password: Specify the password for the admin or equivalent user you specified.
8Select the DirXML Driver for eDirectory, even if you only have one eDirectory tree (your
clusters are in the same eDirectory tree). Click Next.
NOTE: This screen lists all DirXML drivers. Those that cannot be installed on NetWare are
disabled. Drivers that aren't licensed in this bundle, but that can run on NetWare, are labeled
Evaluation. Evaluation drivers require a separate purchase and activation within 90 days of
their installation.
NOTE: The DirXML 1.1a driver for eDirectory must be installed on one node in each cluster.
Business Continuity Cluster software will not function correctly if the driver is installed on a
NetWare server that is not a cluster node.
9Read the Summary page, then click Finish.
The file copy might take a few minutes.
10 After the Installation Complete dialog box is displayed, click Close.
2.3 Installing the DirXML 1.1a Management
Utilities
The DirXML management utilities add the necessary roles and iManager functionality for the
Business Continuity Cluster software. The management utilities can be installed on either a NetWare
6.5 server or a Windows server. Where you install the management utilities depends on where you
access and run iManager. If you choose to install the management utilities on a NetWare server, you
might want to consider a server that is not part of a cluster, but is in the same eDirectory tree as the
cluster. This is because DirXML cannot be failed over from one cluster server to another.
IMPORTANT: Do not install DirXML 2.x management utilities with the DirXML 1.1a engine. If
you do, the DirXML Driver for eDirectory will be converted to version 2.x, and the DirXML 1.1a
engine will no longer be able to get the driver information.
2.3.1 Installing the DirXML Management Utilities on a NetWare
Server
1At the NetWare 6.5 server where iManager is installed, insert the DirXML CD into the CD
drive.

20 Novell Business Continuity Cluster Services 1.0 Administration Guide
novdocx (ENU) 10 August 2006
2From the GUI server console, click Novell > Install > Add.
If the GUI server console isn't running, launch it by entering STARTX at the console.
3In the Path to Install From field, browse to and select DirXML_STRTR_PCK\nw\product.ni on
the DirXML CD, then click OK.
4On the DirXML Product Installation page, click Next.
5Read the license agreement; if you agree to the terms, click I Accept.
6On the Components page, mark the following items, then click Next.
DirXML Preconfigured Drivers
Novell iManager Plug-ins for DirXML
7Verify that all the preconfigured driver files are selected, then click Next.
8Read the Summary page, then click Finish.
If you are presented with an LDAP warning message, verify that no conflicts exist, then click
OK.
Plug-ins and preconfigured drivers are copied to the Tomcat directory (typically,
sys:tomcat\4\webapps\nps\portal\modules\plugins and
sys:tomcat\4\webapps\nps\DirXML.Drivers) for use during iManager and driver configuration.
The file copy might take a few minutes.
9At the message directing you to restart your Web services, click OK.
10 After the Installation Complete dialog box is displayed, click Close.
11 Restart your Web services using the following sequence:
11a To stop Tomcat, at the System Console prompt, type tc4stop, then press Enter.
Verify that this service is stopped by going to the Logger screen and finding the message
Bootstrap exited successfully.
11b To restart Tomcat, at the System Console prompt, type tomcat4, then press Enter.
Verify that this service is started by going to the Logger screen and finding the message
Jk running....
12 (Conditional) If you are using Assigned Access or Collection Owner Access, make DirXML
roles available by using the iManager Configuration Wizard as explained in the steps that
follow.
12a Launch iManager by going to http://serveripaddress/nps/iManager.html.
IMPORTANT: This URL is case sensitive.
12b Click the Configure button , then click RBS Configuration > Configure iManager.
12c Select either Create a New Collection or Upgrade Collections, then click Next.
NOTE: Fewer collections will improve iManager performance.
12d Select the collections to be updated, then click Next.
12e Select DirXML Utilities and assign a Scope.
TIP: Assign the Scope high enough in the tree to allow access to all DirXML objects
including the server object representing the server where DirXML is installed,