8 Click the Auto-Failover link just under the tabs.
9 Select the Enable Automatic Failover of Business Continuity Cluster Resources check box,
then click Apply.
10 Continue with
failover policy.
Auto-failover is not completely enabled until you create an auto-failover policy.
B.2 Creating an Auto-Failover Policy
By default, no auto-failover policy exists for BCC. You must create an auto-failover policy for each
cluster in your BCC where you want auto-failover enabled. This is required to automatically fail
over resources from one cluster to another.
1 In iManager, under Cluster Membership Monitoring Settings, select a cluster and click the Edit
link.
2 Under Membership Threshold, select the Enable check box, select either Percent Fail or Nodes
Fail, and specify either the percentage of failed nodes or the number of failed nodes.
The node failure number or percentage you specify must be met for the selected cluster before
resources automatically fail over to another cluster.
IMPORTANT: Do not use a membership condition of total node failure (either 100 percent or
the total number of nodes); the condition cannot be satisfied because the cluster will not be up
to report this state.
If a cluster has been totally downed, you must bring up the master node in the downed cluster,
then run the
migrating the BCC-enabled resources to peer clusters.
3 Under Communication Timeout, select the Enable check box and specify the number of
minutes that must elapse without any communication between clusters before resources
automatically fail over to another cluster.
4 Click OK to finish editing the policy.
5 Click the Apply button to save your settings.
B.3 Refining the Auto-Failover Policy
You can further refine auto-failover policies to give you more control over if or when an auto-
failover occurs. To do this, click the Advanced button to display additional fields for specifying
auto-failover criteria and adding monitoring information.
The policy for automatic failover is configured by creating rules. Each row in the Failover Policy
Configuration table represents a rule that applies to a single cluster, or to all clusters in the business
continuity cluster. Each rule contains a set of conditions. Each condition tests one of the following
criteria:
The value of an indication reported by a monitor
The amount of time the connection to a cluster has been down
If the connection to a cluster is up
138 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux
Section B.2, "Creating an Auto-Failover Policy," on page 138
cluster resetresources
command on that node before you begin manually
to create a
Need help?
Do you have a question about the BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION and is the answer not in the manual?
Questions and answers