Deleting And Re-Creating The Bcc Identity Manager Drivers; Finalizing The Bcc Cluster Conversion; What's Next; Chapter 9, "Configuring Bcc For Peer Clusters," On - Novell BUSINESS CONTINUITY CLUSTERING 1.2 - ADMINISTRATION Administration Manual

5b LUM-enable the bccgroup and add all the Linux nodes in the cluster to it.
5c Assign trustee rights for the BCC Administrator user to the cluster objects.
5d Add the BCC Administrator user to the ncsgroup on each cluster node.
6 (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.
7.4 Deleting and Re-Creating the BCC Identity
Manager Drivers
After all of the nodes in every peer cluster has been successfully converted to Linux, you must re-
create the BCC-specific Identity Manager drivers before finalizing the conversion. For information
about re-creating the drivers, see
on page 67.

7.5 Finalizing the BCC Cluster Conversion

Normally, when converting a NetWare cluster to Linux, you need to run the
command after every node in the cluster has been converted to Linux in order to finalize the
conversion. When converting a business continuity cluster from NetWare to Linux, do not run the
command after you convert the nodes in a given peer cluster. You must wait
cluster convert
until all of the nodes in every peer cluster in the business continuity cluster has been upgraded to the
latest NetWare version and converted to Linux, and you have re-created the BCC drivers. Then you
can run the
cluster convert
conversion. See "Finalizing the Cluster
1.8.6 for Linux Administration

7.6 What's Next

After the BCC is upgraded, continue with
page 81.
Chapter 8, "Configuring the Identity Manager Drivers for BCC,"
command one cluster at a time to finalize the BCC cluster
Conversion" in the
Guide.

Chapter 9, "Configuring BCC for Peer Clusters," on

cluster convert
OES 2 SP1: Novell Cluster Services
Converting BCC Clusters from NetWare to Linux 65