Configure automated peer recovery to enable cluster members
to automatically complete outstanding work for a failed cluster member.
After you have configured automated peer recovery, recovery processing
occurs without any intervention on your part.
Before you begin
Make sure that
you understand the infrastructure requirements
for automatic peer recovery. For more information, see the topics
about how to choose between automated and manual transaction peer
recovery and Disabling file locking.
About this task
Automated peer recovery processing is the default setting
when high availability is enabled. Follow the steps in this topic
to ensure that your system is configured correctly. If you configured
manual peer recovery and want to return to automated peer recovery,
you must reconfigure the system back to the default settings.
Procedure
- Verify that high availability is enabled, and that
the
location of the transaction recovery log is specified, as described
in Configuring transaction properties for peer recovery.
- Remove
any high availability (HA) policies with a policy
type of Static. Such policies might exist if you
previously configured the system for manual peer recovery.
- In the navigation pane of the administrative
console,
click . All the
members of a cluster are in a single core group, which by default
is the DefaultCoreGroup core group. Click the core group that contains
your cluster. The Core groups configuration panel
is displayed.
- Under Additional
Properties,
click Policies. The current
set of policies is displayed.
- Select
any policies with a Policy type of Static,
and a Match criteria that includes type
= WAS_TRANSACTIONS. Click Delete.
- Check to see if the required
One-of-N transaction HA policy
already exists. This policy has a Policy type of One
of N, and a Match criteria that includes type
= WAS_TRANSACTIONS. If this policy already exists, you do
not have to take any further action. If the policy does not already
exist, use the following steps to create it.
- Click New to create a new policy.
- Select One of N policy and
click Next.
- Provide
a name for the policy. This value is a free-form
text string that is used only as a label in the administrative console,
however to assist readability in the administrative console, use a
name that associates the policy with the required behavior, for example,
Clustered TM policy.
- Enter a description,
if required.
- Select the Failback check
box
to ensure that a failed server reclaims its recovery log when it restarts,
and click OK.
- Set
values for the Is alive timer, Quorum,
and Preferred servers only options, if required. See the contextual help for more information.
- Under Additional Properties,
click Match criteria to open an empty Match
criteria panel.
- Click New to
create a new match
criterion.
- Enter type in
the Name field
and WAS_TRANSACTIONS in the Value field.
Click OK.
- Save
your changes to the master configuration, ensuring
that you select the Synchronize changes with Nodes check
box.
- Stop and restart the cluster members
for the changes
to take effect.
Results
Automated
transaction peer recovery is configured for all
the servers in the cluster. If a server fails, another server in the
cluster will complete any outstanding work for the failed server.