IBM


6.3.1 State change of high availability group members

Here is an example for the one of N policy: There are two servers (A and B) in a group, only server A is a preferred server. HAManager activates the services (Transaction Manager or messaging engine) in server A, right after it joins the group. Later, server B starts and joins the group. Server B stays in idle state until server A fails. At that time, HAManager activates the services in server B until server A restarts. If the failback flag in the policy is set to true, when server A starts, HAManager deactivates the services in server B and activates them in server A again. If the failback flag is set to false, HAManager leaves server B as the active member.

Figure 6-12 shows the state changes for the group members.

Figure 6-12 High availability group life cycle


Redbooks ibm.com/redbooks

Next