Novell BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 -... User manual

Novell
www.novell.com
novdocx (en) 11 December 2007
Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
Business Continuity Clustering
for NetWare®
1.1
February 15, 2008
ADMINISTRATION GUIDE

novdocx (en) 11 December 2007
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.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Copyright © 2007-2008 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.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).

novdocx (en) 11 December 2007
Novell Trademarks
For Novell Trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.

novdocx (en) 11 December 2007

Contents 5
Contents
novdocx (en) 11 December 2007
About This Guide 9
1Overview 11
1.1 Disaster Recovery Implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Disaster Recovery Implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2.1 Stretch Clusters vs. Cluster of Clusters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.2 Novell Business Continuity Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2.3 Usage Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2 Installation and Setup 19
2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.1.1 NetWare 6.5 SP 5 or SP 6 (OES 1 SP2 or SP3 NetWare) . . . . . . . . . . . . . . . . . . . . 19
2.1.2 Novell eDirectory 8.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.1.3 Novell Cluster Services 1.8.2 for NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.1.4 OpenSLP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.1.5 OpenWBEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1.6 BASH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1.7 LIBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1.8 autoexec.ncf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1.9 Shared Disk Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1.10 Link Speeds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2 Installing Identity Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3 Installing Novell Business Continuity Cluster Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.1 Business Continuity Cluster Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.2 Running the Business Continuity Cluster Installation Program . . . . . . . . . . . . . . . . . 23
2.3.3 Business Continuity Cluster Component Locations . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4 Configuring File System Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4.1 Configuring NSS Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.2 Configuring SAN-Based Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.4.3 LUN Masking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.5 Setting Up Novell Business Continuity Cluster Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.5.1 Configuring Business-Continuity-Specific IDM Drivers . . . . . . . . . . . . . . . . . . . . . . . 29
2.5.2 Configuring Clusters for Business Continuity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.5.3 Configuring Cluster Resources for Business Continuity . . . . . . . . . . . . . . . . . . . . . . 41
2.6 Managing a Novell Business Continuity Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.6.1 Migrating a Cluster Resource to Another Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.6.2 Changing Cluster Peer Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.6.3 Viewing the Current Status of a Business Continuity Cluster . . . . . . . . . . . . . . . . . . 46
2.6.4 Generating a Cluster Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.6.5 Disabling Business Continuity Cluster Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.6.6 Business Continuity Cluster Console Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.7 Business Continuity Cluster Failure Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.7.1 SAN-based Mirroring Failure Types and Responses . . . . . . . . . . . . . . . . . . . . . . . . 50
2.7.2 Host-Based Mirroring Failure Types and Responses . . . . . . . . . . . . . . . . . . . . . . . . 51
3 Upgrading BCC 53
3.1 Upgrading BCC 1.0 to BCC 1.1 for NetWare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.1.1 Upgrading NetWare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

6Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
novdocx (en) 11 December 2007
3.1.2 Installing or Upgrading IDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.1.3 Installing BCC 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.1.4 Resetting BCC Administrative User Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.1.5 Authorizing the BCC Administrative User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.1.6 Verifying SAN Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.1.7 Deleting and Re-Creating BCC IDM Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.2 Upgrading BCC 1.0 to BCC 1.1 for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4 Troubleshooting BCC 1.1 57
4.1 Cluster Connection States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.2 Driver Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.3 Excluded Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.4 Security Equivalent User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.5 Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.6 Clusters Can’t Communicate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.7 BCC Startup Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.7.1 Using BCC Startup Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.8 Problems With BCC Installation on NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.9 IDM Drivers for Cluster Synchronization Do Not Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.10 IDM Drivers Do Not Synchronize Objects from One Cluster to Another. . . . . . . . . . . . . . . . . . 63
4.11 Tracing IDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.12 Peer Cluster Communication Not Working. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.13 Administration of Peer Clusters Not Functional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.14 Resource Does Not Migrate to Another Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.15 Resource Cannot Be Brought Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.16 Dumping Syslog on NetWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.17 Slow Failovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.18 Resource Script Search and Replace Functions Do Not Work . . . . . . . . . . . . . . . . . . . . . . . . 66
4.19 Virtual NCP Server IP Addresses Won’t Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.20 IP Address, Virtual Server DN, or Pool Name Does Not Appear on the iManager Cluster
Configuration Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.21 Blank Error String iManager Error Appears While Bringing a Resource Online . . . . . . . . . . . . 68
4.22 Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.23 Mapping Drives in Login Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.24 Mapping Drives to Home Directories Using the %HOME_DIRECTORY Variable . . . . . . . . . . 69
4.25 BCC Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5 Virtual IP Addresses 73
5.1 Virtual IP Address Definitions and Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.1.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.1.2 Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.2 Virtual IP Address Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.2.1 High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.2.2 Unlimited Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.3 Other Added Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.3.1 Support for Host Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.3.2 Source Address Selection for Outbound Connections . . . . . . . . . . . . . . . . . . . . . . . . 77
5.4 Reducing the Consumption of Additional IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.5 Configuring Virtual IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5.5.1 Displaying Bound Virtual IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Contents 7
novdocx (en) 11 December 2007
A Implementing a Multiple-Tree BCC 81
A.1 Copying User Objects Using IDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
A.2 Configuring User Object Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
A.3 Creating SSL Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
A.4 Synchronizing IDM Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
A.5 Preventing IDM Synchronization Loops. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
A.6 Migrating Resources to Another Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
B Setting Up Auto-Failover 87
B.1 Enabling Auto-Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
B.2 Creating an Auto-Failover Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
B.3 Refining the Auto-Failover Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
B.4 Adding or Editing Monitor Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
C Security Considerations 91
C.1 Security Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
C.2 Security Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
C.2.1 BCC Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
C.2.2 Security Information for Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
C.3 Other Security Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
D Documentation Updates 97
D.1 February 15, 2008 (Updates). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
D.1.1 Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
D.1.2 Troubleshooting BCC 1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

8Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
novdocx (en) 11 December 2007

About This Guide
novdocx (en) 11 December 2007
9
About This Guide
This guide describes how to install, configure, and manage Novell®Business Continuity Clustering
for NetWare®. The guide is divided into the following sections:
Chapter 1, “Overview,” on page 11
Chapter 2, “Installation and Setup,” on page 19
Chapter 3, “Upgrading BCC,” on page 53
Chapter 4, “Troubleshooting BCC 1.1,” on page 57
Chapter 5, “Virtual IP Addresses,” on page 73
Appendix A, “Implementing a Multiple-Tree BCC,” on page 81
Appendix B, “Setting Up Auto-Failover,” on page 87
Appendix C, “Security Considerations,” on page 91
Audience
This guide is intended for intended for anyone involved in installing, configuring, and managing
Novell Cluster Services.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
Documentation Updates
The latest version of this Novell Business Continuity Clustering for NetWare Administration Guide
is available on the BCC 1.1 Documentation Web site (http://www.novell.com/documentation/
bcc11/index.html).
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.

10 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
novdocx (en) 11 December 2007

Overview
1
novdocx (en) 11 December 2007
11
1
Overview
As corporations become 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, hurricanes, 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 (The minimum acceptable distance 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
E-mail, 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.
Section 1.2.1, “Stretch Clusters vs. Cluster of Clusters,” on page 12
Section 1.2.2, “Novell Business Continuity Clusters,” on page 15

12 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
novdocx (en) 11 December 2007
Section 1.2.3, “Usage Scenarios,” on page 16
1.2.1 Stretch Clusters vs. Cluster of Clusters
“Stretch Clusters” on page 12
“Cluster of Clusters” on page 12
“Implementation Comparison” on page 14
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 cluster
resources or all cluster resources from one cluster to another cluster. Typically, replication of data
blocks between SANs is performed by SAN hardware, but it can be done by host-based mirroring
for synchronous replication over short distances.
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 13
novdocx (en) 11 December 2007
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

14 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
novdocx (en) 11 December 2007
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 15
novdocx (en) 11 December 2007
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 clusters, and the clusters in each of the geographically separate sites are
each treated as "nodes" in a larger cluster, allowing a whole site to do 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 provides the following advantages:
Integrates with SAN hardware devices to automate the failover process using standards based
mechanisms such as SMI-S.
Utilizes Novell Identity Manager 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.
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.
Depending on the platform used,
storage arrays must be
controllable by scripts that run on
NetWare®or Linux if the SANs
are not SMI-S compliant.
Stretch Cluster Cluster of Clusters

16 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
novdocx (en) 11 December 2007
Includes intelligent failover that lets you do site failover testing as a standard practice.
Provdes scripting capability for enhanced control and customization.
Provides simplified business continuity cluster configuration and management using the
browser-based iManager management tool.
Runs on Linux and NetWare.
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 Two-Site Business Continuity Cluster Solution
A Multiple-Site Business Continuity Cluster Solution
A Low-Cost Business Continuity Cluster Solution
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 and services ready to load if
needed.
Two active sites each supporting different applications and services. Either site can take over
for the other site at any time.
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.

Overview 17
novdocx (en) 11 December 2007
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
synchronous replication over short distances. The illustration below depicts a four-site business
continuity cluster.
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

18 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
novdocx (en) 11 December 2007
Figure 1-4 Multiple-Site Business Continuity Cluster
Using the Novell 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 either
with iSCSI-based block replication, or host-based mirroring. In either 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 (en) 11 December 2007
19
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:
Section 2.1, “Requirements,” on page 19
Section 2.2, “Installing Identity Manager,” on page 21
Section 2.3, “Installing Novell Business Continuity Cluster Software,” on page 23
Section 2.4, “Configuring File System Mirroring,” on page 25
Section 2.5, “Setting Up Novell Business Continuity Cluster Software,” on page 29
Section 2.6, “Managing a Novell Business Continuity Cluster,” on page 43
Section 2.7, “Business Continuity Cluster Failure Types,” on page 49
2.1 Requirements
The requirements in this section must be met prior to installing Novell Business Continuity Cluster
software.
Section 2.1.1, “NetWare 6.5 SP 5 or SP 6 (OES 1 SP2 or SP3 NetWare),” on page 19
Section 2.1.2, “Novell eDirectory 8.8,” on page 20
Section 2.1.3, “Novell Cluster Services 1.8.2 for NetWare,” on page 20
Section 2.1.4, “OpenSLP,” on page 20
Section 2.1.5, “OpenWBEM,” on page 21
Section 2.1.6, “BASH,” on page 21
Section 2.1.7, “LIBC,” on page 21
Section 2.1.8, “autoexec.ncf File,” on page 21
Section 2.1.9, “Shared Disk Systems,” on page 21
Section 2.1.10, “Link Speeds,” on page 21
2.1.1 NetWare 6.5 SP 5 or SP 6 (OES 1 SP2 or SP3 NetWare)
NetWare®6.5 Support Pack 5 or 6 (same as OES 1 Support Pack 2 or 3 Netware) must be installed
and running on all servers that will be part of a business continuity cluster.
The requires the NetWare 6.5 post Support Pack 5 Update. See TID # 2974185 (http://
support.novell.com/cgi-bin/search/searchtid.cgi?/2974185.htm). If you have installed NetWare 6.5
Support Pack 6, the Support Pack 5 Update is not required.
See the OES NetWare Installation Guide for information on installing and configuring NetWare 6.5.

20 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
novdocx (en) 11 December 2007
2.1.2 Novell eDirectory 8.8
eDirectory 8.8 is supported with Business Continuity Clustering 1.1 Support Pack 1. See the
eDirectory 8.8 documentation (http://www.novell.com/documentation/edir88/index.html) for more
information.
2.1.3 Novell Cluster Services 1.8.2 for NetWare
Two to four clusters with Novell Cluster Services™ 1.8.2 (the version that ships with NetWare 6.5
Support Pack 5) 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 OES Novell Cluster Services 1.8.2 Administration Guide for NetWare for information on
installing and configuring Novell Cluster Services.
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 Requirements” in the OES Novell Cluster Services 1.8.2 Administration Guide for
NetWare.
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.
Also, some SAN hardware may not be SMI-S compliant and can’t be managed using SMI-S
commands.
The recommended configuration is to have each cluster be in the same eDirectory tree. You can have
a business continuity cluster with clusters in separate eDirectory trees. See Appendix A,
“Implementing a Multiple-Tree BCC,” on page 81 for more information.
You must have the nwcs18pt3 or later cluster patch. See TID # 2974985 (http://support.novell.com/
cgi-bin/search/searchtid.cgi?/2974985.htm). This patch can only be applied to NetWare 6.5 Support
Pack 5. If you have upgraded to NetWare 6.5 Support Pack 6, this patch is not required.
The recommended configuration of a business continuity cluster is to have each Novell Cluster
Services cluster be in the same eDirectory tree. You can have a business continuity cluster with
clusters in separate eDirectory trees. See Appendix A, “Implementing a Multiple-Tree BCC,” on
page 81 for more information.
In order to add or change cluster peer credentials, you must access iManager on a server that is in the
same eDirectory tree as the cluster you are adding or changing peer credentials for.
2.1.4 OpenSLP
You must have SLP (Server Location Protocol) set up and configured properly. See Configuring
OpenSLP for eDirectory (http://www.novell.com/documentation/edir873/edir873/data/
aksbdp5.html#aksbdp5) in the Novell eDirectory 8.7.3 Administration Guide.