Novell BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 - ADMINISTRATION, Руководство пользователя, Страница: 89 / 98

Setting Up Auto-Failover 89
no
vd
ocx (
e
n)
1
1
Decemb
er
2
007
2 Select the cluster that you want the rule to apply to, or select All to apply the policy to all
clusters.
3
Under Conditions , choose the type of condition and the appropriate values. To add multiple
conditions to the rule, click the Add button below the condition.
You can use the default setting of Monitor if you don't want to apply the cluster up or cluster
down criteria to this policy. You can also specify or change the percent or number of nodes
criteria that are used to determine if an auto failover can occur.
4 Click Apply to save your settings.
For rules with monitor conditions automatically created using the Cluster Membership Monitoring
Settings table, you can add a condition that tests if the connection to the peer cluster is up. Adding
this condition changes the behavior of the rule. With this rule a graceful automatic failover of
resources can happen when the connection to the peer cluster is up.
You can also specify or change the percent or number of nodes criteria that is used to determine if an
automatic failover can occur. Do not however use a membership condition of total node failure
(either one-hundred percent or the total number of nodes) because the condition can't be satisfied,
since the cluster won't be up to report this state. Also, adding a connection down condition to a rule
with a condition that tests cluster membership is not recommended. It is highly unlikely that cluster
membership information for a specific cluster will be reported to peer clusters when the connection
to that specific cluster is down. For these reasons, you should create a separate rule with a
connection down condition.
B.4 Adding or Editing Monitor Configurations
Clicking the Advanced button will also display an additional section on this page called Health
Monitor Configuration. Monitors are an important part of the automatic failover feature, and are
separate processes that perform a specialized task to analyze the health of a specific cluster or all
clusters in the BCC. These monitors report an indication of health to BCC. BCC in turn uses the
reported information to analyze the failover policy to determine if resources should be migrated
from a specific cluster. BCC 1.1 ships with two monitors (nodecnt and node pnt) that report an
indication of health that represents either the percentage or number of nodes that are not a member
of a specific cluster.
If configured using the Cluster Membership Monitoring Settings table, the fields under Health
Monitor Configuration should already contain information for the health monitor (nodepnt or
nodecnt) included with BCC 1.1. Although default values have already been set, you can customize
some of the monitor settings for the cluster membership monitors. If you have created your own
custom monitor, you can click
New to add configuration settings to your monitor.
1 Under Monitor Name in the Health Monitor Configuration section, select a monitor and click
Edit .
2 Under Clusters , select the cluster or clusters that you want this monitor to apply to.
3 Enter the maximum health indication that the monitor will report.
This value is used when creating a failover policy to validate the rules. This is the maximum
value that can be used for the threshold type when you create a failover policy. For example, if
you specified percent fail membership monitoring, the maximum values would be 100 (for 100
percent) for the nodepnt monitor. If you specified nodes fail membership monitoring, the
maximum value for the nodecnt monitor is the maximum number of nodes permitted in a
cluster, which is 32. If you created your own custom monitor, the values could be different.