Use this page to define a policy for a high availability group. A policy is defined at the core group level. It only applies to matching high availability groups contained within this core group
To view this administrative console page, click
, or select an existing core group, and then click pollicy_name.Specifies the name of the policy. This name must be unique within the scope of a core group.
Specifies the policy type that was selected when this policy was created. This is a read-only field. If you want to change the policy type, you must delete this policy and then create it again specifying a different policy type. If this is an IBM® provided policy, do not delete it. Instead create a new policy and specify more of the attributes contained in the name of the high availability group as the match criterion for this new policy. The policy with the greatest number of matches to attributes in a group's name is the policy that is associated with that group.
Specifies a description of this policy. For example, the clustered TM policy provided with the product has "TM One-Of-N Policy" as its description.
Specifies, in seconds, the interval of time at which the high availability manager will check the health of the active group members that are governed by this policy. If a group member has failed, the server on which the group member resides is restarted.
Data type | Integer
|
Default | 0 (zero) |
Specifies whether work items assigned to the failing server are moved to the server that is designated as the most preferred server for the group if a failure occurs. This field only applies for M of N and One of N policies.
Specifies whether group members are only activated on servers that are on the list of preferred servers for this group. This field only applies for M of N and One of N policies.
Specify how many of the high availability group members are to be activated. This field only applies for the M of N policy.
Specifies whether quorum checking is enabled for a group governed by this policy. Quorum is a mechanism that can be used to protect resources that are shared across members of the group in the event of a failure.
When enabled, any group using this policy will not achieve quorum until a majority of the members are running. For example, if there are n members in the group, (n/2) + 1 servers must be online in order to achieve quorum. No group members will be activated until quorum has been achieved.
The quorum mechanism is designed to work in conjunction with a hardware control facility that allows application servers to be shut down if a failure causes the group to be partitioned.
Custom properties | Click to specify custom properties for the policy. |
Match criteria | Click to set up a match criterion for the policy. |
Preferred servers | Click to set up a list of servers that are given preference when group members are activated. |
Static group servers | Click to set up a list of the specific servers that are activated. |