Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1 - README 9-21-2010 Installation Manual

Also see for BUSINESS CONTINUITY CLUSTERING 1.1 SP1: Administration guide

Contents

Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1 - README 9-21-2010 Installation Manual Manual pdf 5 page image

Novell Business Continuity Clustering 1.1 SP1 Readme 5The same restrictions that apply to migrating or failing over resources between nodes within a singlecluster also apply to migrating or failing over resources between clusters in a mixed BCC. You canonly migrate or fail over NSS pool/volume resources between clusters in a mixed BCC. SeeConverting a NetWare Cluster to Linux (http://www.novell.com/documentation/oes/cluster_admin_lx/data/bu1b1x8.html) in the OES Novell Cluster Services 1.8.2 AdministrationGuide for Linux3.7 Do Not Mix IDM VersionsDo not install IDM 3.x management utilities with the IDM 2.x engine. If you do, the IDM Driver foreDirectory will be converted to version 3.x, and the IDM 2.x engine will no longer be able to get thedriver information.4 Known Issues Section 4.1, “Existing Clusters Could Have Conflicting VOLIDs,” on page 5 Section 4.2, “Refresh of iManager Views Delayed,” on page 5 Section 4.3, “NSS Pool Failover Times,” on page 6 Section 4.4, “Migrating Volume Trustee Assignments,” on page 6 Section 4.5, “Renamed BCC Volume Names Don't Replicate to Other Trees,” on page 6 Section 4.6, “Using iManager to Set Credentials on Linux Not Functional,” on page 6 Section 4.7, “Problems Saving SAN Management Scripts,” on page 7 Section 4.8, “Resource Goes Offline After Migration,” on page 7 Section 4.9, “Cluster and Peer Clusters Don’t Appear in Connections List After Upgrade,” onpage 7 Section 4.10, “Creating a New Cluster Resource Requires IDM Cluster Node to Be Up,” onpage 7 Section 4.11, “Disabling BCC for a Cluster Disables BCC for Cluster Resources,” on page 7 Section 4.12, “Cluster Restart Command Not Functional on NetWare,” on page 74.1 Existing Clusters Could Have Conflicting VOLIDsWhen existing clusters are configured and enabled within the same business continuity cluster, thevolume IDs (VOLIDs) for the existing shared volumes might also share the same VOLIDs. Tocorrect this problem, manually edit the load script for each volume that has been enabled forbusiness continuity and change the VOLIDs to unique values for each volume in the businesscontinuity cluster.4.2 Refresh of iManager Views DelayedWhen you enable a cluster resource for business continuity, that resource might take up to 30seconds to appear as enabled for business continuity in iManager. After Business ContinuityClustering refreshes its status information, the resource will appear as enabled.

/ 8

Related manuals for Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1