This section describes how HACMP for Linux handles failures and ensures that the application keeps running.
The following scenarios are considered:
•Node Failure
•Network Failure
•Network Interface Failure
•Preventing Cluster Partitioning.
Node Failure:
If the application is configured to normally run on Node1 and Node1 fails, the resource group with the application falls over, or moves, to Node2.
At a high level, on Node2, HACMP detects that Node1, the default owner of the resource group, has failed and moves the resource group to Node2. This operation is called a resource group takeover. The application is kept highly available and the end users continue to access it.
If Node2 rejoins the cluster, based on the resource group policy HACMP performs the resource group fallback. The resource group moves back to Node1 (for example, if that is the selected fallback policy for the resource group).
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment