After enabling a resource for business continuity, it is possible to disable it. You might want to disable BCC for a cluster resource in any of the following cases:
You accidentally enabled the resource for business continuity.
You no longer want the cluster resource to be able to fail over between peer clusters.
You plan to delete the cluster resource.
You plan to remove the peer cluster from the business continuity cluster. In this case, you must disable BCC for each cluster resource before you disable BCC for the cluster.
IMPORTANT:If you disable Business Continuity Clustering for a cluster by using either iManager or the cluster disable console command, the cluster resources in that cluster that have been enabled for business continuity are automatically disabled for business continuity. If you re-enable Business Continuity Clustering for the cluster, you must again re-enable each of its cluster resources 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 Business Continuity Clustering for an entire cluster.
Before you disable BCC for a BCC-enabled resource, remove the secondary peer clusters from the resource’s assigned list, then disable BCC only from the primary cluster, either by using iManager or command line. Do not attempt to disable BCC on the same resource from multiple peer clusters.
To disable BCC for a cluster resource:
Log in to iManager as the BCC Administrator user.
In, click > , then click the cluster name.
Select the check box next to the desired cluster resource from the list of Cluster objects.
On thetab, remove the secondary peer clusters from the list, then disable BCC for the resource on the primary peer cluster.
From thelist, select the nodes that reside in the secondary peer clusters, then click the arrow button to move the selected servers to the list.
The primary peer cluster and the node where the resource is running cannot be moved from thelist to the list.
Clickto save the node assignment changes.
On thepage, click the tab, deselect the check box, then click .
Wait for Identity Manager to synchronize the changes.
This could take from 30 seconds to one minute, depending on your configuration.
Delete the Cluster Resource object on the clusters where you no longer want the resource to run.