Novell BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 - ADMINISTRATION Manual page 48

BCC Console Commands
CLUSTER CREDENTIALS {cluster}
CLUSTER DISABLE {resource}
CLUSTER ENABLE {resource}
CLUSTER MIGRATE {source/resource}
{destination/node name}
48 Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
Description
Lets you change the administrator username and
password that this cluster will use to connect to the
specified peer cluster. The cluster you specify must
be a member of a cluster that has already been
enabled for Business Continuity Clustering.
Disables Business Continuity Clustering for the
specified resource. The resource you specify must be
a member of a cluster that has already been enabled
for Business Continuity Clustering. If no resource is
specified, the entire cluster is disabled for Business
Continuity Clustering.
If you disable BCC for a cluster using the Cluster
Disable console command, BCC will also be disabled
for those cluster resources that have been BCC-
enabled. If you re-enable BCC for the cluster, you
must re-enable each individual cluster resource that
you want to be BCC-enabled.
This can be a time-consuming process if you have
many BCC-enabled cluster resources. For this
reason, you should use caution when disabling BCC
for an entire cluster.
Enables Business Continuity Clustering for the
specified resource. The resource you specify must be
a member of a cluster that has already been enabled
for Business Continuity Clustering. If no resource is
specified, the entire cluster is enabled for Business
Continuity Clustering.
When BCC-enabling a resource, previous versions of
the CLI would not set the peer clusters where the
resource was assigned to run. The only way to set
peer clusters for a resource was through iManager.
The new version of the cluster CLI automatically sets
all the clusters in the BCC on a resource. Assigning a
resource to specific clusters still must be done
through iManager.
Migrates the specified resource from the specified
source cluster to the specified target (destination)
cluster. Specifying * for the resource name will
migrate all BCC-enabled resources. Specifying * for
the node name will bring the resource online at the
most preferred node.