This Readme identifies known issues for Novell Business Continuity Clustering (BCC) 2.0 for your Novell Open Enterprise Server (OES) 11 Support Pack 1 (SP1) servers that are running Novell Cluster Services (NCS) 2.1.
Business Continuity Clustering 2.0 supports up to four peer clusters that are running OES 11 SP1 and Novell Cluster Services 2.1.
The BCC 2.0 operating environment requires the versions of Novell, SUSE, and NetIQ products listed in Table 1, with the latest patches applied.
Table 1 BCC 2.0 Operating Environment
|
Supported Product |
For documentation, see: |
|---|---|
|
eDirectory 8.8 Support Pack 7 This product is included with OES 11 SP1. |
eDirectory 8.8 SP7 documentation Web site on NetIQ.com |
|
Novell Open Enterprise Server 11 Support Pack 1 |
OES 11 SP1 documentation Web site on Novell.com |
|
SUSE Linux Enterprise Server 11 Service Pack 2 A SLES 11 SP2 entitlement is included with your OES 11 SP1 purchase. |
SLES 11 SP2 documentation Web site on SUSE.com |
|
Novell Cluster Services 2.1 This product is included with OES 11 SP1. |
OES 11 SP1: Novell Cluster Services 2.1 for Linux Administration Guide For information about clustering OES 11 SP1 services and storage, see the product documentation on the OES 11 SP1 documentation Web site on Novell.com. |
|
iManager 2.7.6 This product is included with OES 11 SP1. |
iManager 2.7.6 documentation Web site on NetIQ.com |
|
Clusters plug-in for iManager This product is included with OES 11 SP1. |
|
|
Identity Manager 4.0.2 Bundle Edition (64-bit) The credential to activate the Bundle Edition is included in the BCC 2.0 license. |
Identity Manager 4.0.2 documentation Web site on NetIQ.com |
Novell Business Continuity Clustering 2.0 is available through Novell Downloads. An ISO file is available for 64-bit architectures.
In addition, you must download the following products:
Identity Manager 4.0.2 Bundle Edition for OES 11 SP1 (64-bit version)
The credential that you need to use Identity Manager drivers beyond the evaluation period is found in the BCC license.
You must apply all maintenance patches for Identity Manager 4.0.2 on the Identity Manager node in each of the peer clusters before you install or upgrade BCC on any of the nodes in any peer cluster. Patches are available on Novell Patch Finder.
Novell Open Enterprise Server 11 SP1
Apply the latest OES 11 SP1 maintenance patches on all nodes in every peer cluster before you install or upgrade BCC on any of the nodes. Patches are available through the OES 11 SP1 patch channel and SLES 11 SP2 patch channel.
This section identifies known issues for BCC 2.0 on OES 11 SP1 clusters running NCS 2.1.
When a BCC-enabled pool cluster resource is brought online in a peer cluster other than where it was originally created, you cannot add a new volume on the pool. The volume is created on the disk, but the Volume object fails to be added to Novell eDirectory with Error 613: Error adding volume to NDS.
We recommend that you create only one volume per pool cluster resource. If you need to add a volume on a BCC-enabled pool cluster resource, you must BCC-migrate the resource back to the peer cluster where the pool was originally created.
In some disaster situations, it is possible that the pool cluster resource has been permanently relocated to the current peer cluster. To cluster-enable the pool in its current cluster, see Permanently Relocating a Cluster Resource to a Peer Cluster
in the BCC 2.0 Administration Guide for OES 11 SP1.
In the BCC 2.0 release, multiple-tree configurations of business continuity clusters are not supported. All peer clusters must reside in the same tree.
BCC 2.0 does not support mixed peer clusters of NetWare and Linux. A cluster in mixed-mode that contains both NetWare and Linux servers is supported in a BCC peer cluster only as a temporary means to convert a cluster from NetWare to Linux. The cluster is considered a NetWare cluster, and only NetWare nodes are enabled for BCC. Resources running on Linux nodes in the mixed cluster cannot fail over to a peer cluster.
Before you begin the conversion of a BCC from NetWare to Linux, ensure that you understand the sequence of tasks and the limitations of working in mixed-mode in a BCC. For information, see Converting BCC Clusters from NetWare to Linux
in the BCC 2.0 Administration Guide for OES 11 SP1.
This Readme lists all known issues for BCC 2.0 for OES 11 SP1. For information about installing and managing BCC, see the BCC 2.0 Administration Guide for OES 11 SP1.
The latest documentation for BCC is available on the Business Continuity Clustering documentation Web site.
For information about installing and managing Identity Manager 4.0.2, see the Identity Manager 4.0.2 documentation Web site.
For information about iManager 2.7.6, see the iManager documentation Web site.
For information about OES 11 SP1 services, see the OES 11 SP1 documentation Web site.
For information about Novell Cluster Services 2.1 for Linux, see the OES 11 SP1: Novell Cluster Services 2.1 Administration Guide for Linux.
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. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2013 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.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.