Novell BUSINESS CONTINUITY CLUSTERING 1.2 - ADMINISTRATION Administration Manual page 130

Console Command
cluster disable [resource]
cluster enable [resource]
cluster migrate [source/resource]
[destination/nodename]
130 BCC 1.2: Administration Guide for OES 2 SP1 Linux
Description
Disables BCC for the specified cluster resource. The
resource you specify must belong to a cluster that
has already been enabled for BCC. If no resource is
specified, the entire cluster is disabled for BCC.
IMPORTANT: Before you disable BCC for a given
peer cluster, you must first disable BCC for each of
the cluster resources running on that cluster.
Before you disable BCC for a given cluster resource,
make sure to remove the secondary peer clusters
from its Assigned list. For information, see
Section 11.6, "Disabling BCC for a Cluster Resource,"
on page 104.
After you have disabled BCC for all resources running
on the cluster, remove the secondary peer clusters
from the Assigned list of preferred nodes, then
disable BCC for the cluster.
If you disable BCC for a cluster by using the
console command, BCC is
cluster disable
automatically disabled for those cluster resources
that have been enabled for BCC. If you re-enable
BCC for the cluster, you must re-enable BCC for each
individual cluster resource that you want to be
enabled for business continuity.
This can be a time-consuming process if you have
many cluster resources that are enabled for business
continuity. For this reason, you should use caution
when disabling BCC for an entire cluster.
Enables BCC for the specified resource. The
resource you specify must belong to a cluster that
has already been enabled for BCC. If no resource is
specified, the entire cluster is enabled for BCC.
When enabling a resource for business continuity,
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 business
continuity cluster 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 migrates
all BCC-enabled resources. Specifying
name brings the resource online at the most preferred
node.
* for the node