This Readme identifies known issues for Novell Business Continuity Clustering (BCC) 1.2.2 for your Novell Open Enterprise Server (OES) 2 Support Pack 3 (SP3) for Linux servers that are running Novell Cluster Services 1.8.8.
Novell Business Continuity Clustering 1.2.2 is available through Novell Customer Care or from sales offices. It is not available on the Novell Downloads Web site. An ISO file is available for 32-bit or 64-bit OES 2 SP3 Linux architectures.
In addition, you must download the following products:
Identity Manager 3.6.1 Bundle Edition (available in 32-bit and 64-bit versions)
The credential that you need in order to use Identity Manager drivers beyond the evaluation period is found in the BCC license.
Apply all maintenance patches for Identity Manager on the IDM node in each of the peer clusters before installing or upgrading BCC 1.2.2. The IDM 3.6.1 Engine Patch 3 Build 3.6.14 or later version is required.
When you upgrade from OES 2 SP2 to OES 2 SP3, you must also apply the IDM 3.6.1 OES 2 SP3 Compatibility Patch 1 (TID #5090210) to the IDM node in each of the peer clusters before you upgrade the operating system to OES 2 SP3 on any of the nodes in the peer clusters.
Novell Open Enterprise Server 2 SP3
Apply the latest OES 2 SP3 maintenance patches on all nodes in every peer cluster before you install or upgrade BCC on any of the nodes.
The Clusters plug-in and other storage-related plug-ins for iManager 2.7.4 that are delivered with the OES 2 SP3 Linux release. Apply the latest OES 2 SP3 patches for these plug-ins.
This section identifies known issues for BCC 1.2.2 for OES 3 SP3 Linux.
In the BCC 1.2.2 for Linux release, multiple-tree configurations of business continuity clusters are not supported. All peer clusters must reside in the same tree.
If a given BCC-enabled resource is disabled for BCC from multiple peer clusters, and is then BCC-enabled from one or more peer clusters, the resource can come online as primary in multiple clusters.
If a resource is seen as primary in a peer cluster where you know it should actually be seen as secondary, execute the cluster resetresources command to force it to reset the status to its proper state.
IMPORTANT:This command changes the state of all resources on this peer cluster to offline and secondary.
This Readme lists all known issues for BCC 1.2.2 for OES 2 SP3. For information about installing and managing BCC, see the BCC 1.2.2 Administration Guide for OES 2 SP3.
The latest documentation for BCC is available on the Business Continuity Clustering documentation Web site.
For information about installing and managing Identity Manager 3.6.1, see the Identity Manager 3.6.1 documentation Web site.
For information about Novell iManager 2.7.4, see the iManager 2.7.x documentation Web site.
For information about OES 2 SP3 Linux, see the OES 2 SP3 documentation Web site.
For information about Novell Cluster Services 1.8.8 for Linux, see the Clustering (High Availability) documentation Web site for OES 2 SP3.
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 © 2009–2011 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.