Disabling Bcc For A Peer Cluster; What's Next - Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION Administration Manual

In order for the BCC Administrator user to gain access to the cluster administration files (
/admin/
) on other Linux cluster nodes in your BCC, you must add that user to the
novell/cluster
on each cluster node. For instructions, see "Adding the BCC Administrator User to the
ncsgroup
ncsgroup on Each Cluster Node" on page 49.

10.8 Disabling BCC for a Peer Cluster

Before you disable BCC for a given peer cluster, you must first disable BCC for each of the cluster
resources running on that cluster. Make sure to remove the secondary peer clusters from the cluster
resource's Assigned list before you disable BCC for the resource on the primary peer cluster. For
information, see Section 12.6, "Disabling BCC for a Cluster Resource," on page 108.
After you have disabled BCC for all resources running on that cluster, remove the secondary peer
clusters from the Assigned list of preferred nodes for that cluster, then disable BCC for the cluster.

10.9 What's Next

Enable the cluster resources in each peer cluster that you want to be able to fail over between them.
For information, see Chapter 10, "Configuring BCC for Peer Clusters," on page 85.
94 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux