Manage manual peer recovery of the transaction service

After you configure manual peer recovery, you trigger a recovery process by using the administrative console; peer recovery can no longer take place automatically. This requirement applies to transaction peer recovery processing only; standard recovery processing of server recovery logs, driven when the server starts, still occurs automatically.

Before you initiate the peer recovery process, verify that the problem server actually failed and cannot restart. To ensure data integrity, initiate a manual peer recovery process only for servers that are not running.

Overview

You usually direct a peer recovery process if an application server becomes unavailable for some reason, for example, a machine failure. The choice of peer server, within the cluster, is arbitrary.

Procedure

1. In the administrative console click Servers > Core groups > Core group settings .

2. Click the core group that contains the failed server. The Core groups configuration panel is displayed.

3. Under Additional Properties, click Policies.

4. Click the static policy that is associated with the failed server. The Configuration settings for this policy are displayed.

5. Under Additional Properties, click Static group servers. The General Properties panel is displayed.

6. During normal running, the static group servers list must contain only the server that is associated with the policy. However, if you determine that the server failed, you can add a second server to perform the peer recovery processing. From the Core group servers list, select the server on which you want to initiate the peer recovery process. Ensure that you select an application server, rather than a system server such as the node agent or domain manager. Click Add >> to add the server to the static group servers list. Do not add more than one server.

7. Save your changes to the master configuration, ensuring that you select the Synchronize changes with Nodes check box. This step causes a recovery process for the failed server to begin on the peer server.

8. When recovery processing is complete, reverse the configuration changes that you made before restarting the failed server. Return to the Static group servers list, select the peer server that you added previously and click Remove <<. Click OK.

9. Save your changes to the master configuration, ensuring that you select the Synchronize changes with Nodes check box.

Results

What to do next

Related concepts

Related tasks