To convert a business continuity cluster from BCC 1.1 SP2 for NetWare 6.5 SP8 to BCC 1.2.2 for OES 2 SP3, you must convert all of the nodes in every peer cluster from NetWare 6.5 SP8 to OES 2 SP3. Consider the following caveats as you convert the clusters to Linux:
Clusters containing both NetWare and Linux servers are supported in a BCC only as a temporary means to convert a cluster from NetWare to Linux.
In a mixed-mode state, the script conversion between NetWare and Linux is done only between nodes in the same cluster. The scripts are not permanently converted until the cluster conversion is finalized.
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 migrate or fail over only NSS pool/volume resources that were originally created on NetWare between the peer clusters in a mixed BCC, until the conversion is finalized.
Scripts have different size limits on NetWare and OES 2 Linux. In a mixed-node cluster, the scripts for NetWare resources that are cluster migrated to OES 2 Linux nodes are restricted to the NetWare script-size limits (924 bytes) until the final cluster convert command is issued. For information, see Comparing Script Length Limits for NetWare and Linux
in the OES 2 SP3: Novell Cluster Services Conversion Guide.
No new cluster resources should be created on NetWare nodes or Linux nodes during the cluster conversion process until the BCC/cluster conversion is complete, except where you are instructed to do so in cluster conversion documentation. For information about converting cluster resources from NetWare to Linux, see the OES 2 SP3: Novell Cluster Services Conversion Guide.
On one cluster at a time, do the following:
Convert NetWare cluster nodes to Linux by following the instructions in the OES 2 SP3: Novell Cluster Services NetWare to Linux Conversion Guide.
IMPORTANT:Do not perform the step to finalize the cluster conversion until after all of the nodes in every peer cluster in the business continuity cluster have been converted to Linux, and the BCC drivers for Identity Manager have been re-created.
Add a Read/Write replica of the cluster’s eDirectory partition to the new Linux nodes.
Stop the Identity Manager drivers, then remove the old NetWare Identity Manager node from the cluster.
Install Identity Manager 3.6.1 on one Linux node in each cluster.
Configure the BCC Administrator user and group for the Linux cluster.
On Linux, the BCC Administrator user must be Linux-enabled with Linux User Management. The user must also be added to the Novell Cluster Services administration group (such as ncsgroup) on each cluster node. Follow the steps outlined in Section 4.3, Configuring a BCC Administrator User and Group to do the following:
Create the bccgroup and add the BCC Administrator to it.
LUM-enable the bccgroup and add all the Linux nodes in the cluster to it.
Assign trustee rights for the BCC Administrator user to the cluster objects.
Add the BCC Administrator user to the ncsgroup on each cluster node.
(Conditional) If you LUM-enabled the Linux/UNIX Workstation object for a server after BCC is running, restart BCC on that server before continuing to the next node in the cluster.