To upgrade from Business Continuity Clustering 1.0 (NetWare only) to Business Continuity Clustering 1.1 for Linux, you must first upgrade all nodes in Business Continuity Clustering 1.0 clusters to Business Continuity Clustering 1.1 for NetWare. To do this, follow the instructions in Section 3.1, Upgrading Business Continuity Clustering from 1.0 to 1.1 for NetWare.
IMPORTANT:All cluster nodes in every cluster in your BCC must be upgraded to Business Continuity Clustering 1.1 for NetWare before converting clusters to Novell Cluster Services for Linux.
Before you begin converting the NetWare clusters to Linux, see Section 2.1, Requirements for more information on what is required for Business Continuity Clustering 1.1 for Linux.
After all nodes have been upgraded to Business Continuity Clustering 1.1 for NetWare, you can begin to convert them to Linux. On one cluster, upgrade NetWare cluster nodes to Linux by following the instructions in Converting a NetWare Cluster to Linux
in the OES Novell Cluster Services 1.8.2 Administration Guide for Linux.
Clusters containing NetWare and Linux servers are supported in a BCC only as a temporary means to convert a cluster from NetWare to Linux. Part of the temporary conversion state includes a restriction that only one mixed cluster can exist in your BCC. For example, Cluster A can have both NetWare and Linux nodes, but Cluster B cannot. All nodes in Cluster B must be either NetWare or Linux.
You must re-create the BCC-specific Identity Manager drivers after converting to Linux. See Section 2.4.1, Configuring Identity Manager Drivers for the Business Continuity Cluster.
Normally, when converting a NetWare cluster to Linux, you need to run the cluster convert command after the entire cluster has been converted to Linux. When converting a BCC to Linux, do not run the cluster convert command until all clusters in the BCC have been upgraded and converted to Linux. See Finalizing the Cluster Conversion
in the Novell Cluster Services 1.8.2 for Linux Administration Guide.
The same restrictions that apply to migrating or failing over resources between nodes within a mixed cluster also apply to migrating or failing over resources between clusters in a mixed BCC. You can only migrate or fail over NSS pool/volume resources between clusters in a mixed BCC.