Example: A simple, two-node cluster

This configuration example describes a basic cluster that contains two nodes.

This example configuration provides the following:


A two-node cluster featuring an application CRG and a data CRG.

Start of changeUsing this example, Node L is currently operating as the primary node for two cluster resource groups, an application CRG and a data CRG. It also contains a peer CRG that provide continuous operations for either node. Two exit programs will be running periodically on Node L for the application CRG. The reason two exit programs may be running at the same time is if you call the Start CRG API, an exit program is started and runs continuously while the application CRG is active. If you should call the End CRG API for the application CRG, another exit program is then started. Node R is the first, and only, backup node designated in the recovery domain of each cluster resource group. Data that is associated with the data CRG and pertinent application information that is associated with the application CRG is being replicated from Node L to Node R. If Node L fails or needs to be taken down for administrative reasons, then a failover or switchover is initiated and Node R becomes the primary node for both the application and data CRGs. Node R will take over the Internet Protocol (IP) address defined for the application CRG.End of change

Note: While Node L is down, system availability is exposed because there is no backup should Node R also fail. When Node L recovers and rejoins the cluster, it is made the backup for both cluster resource groups. At that time, replication will be from Node R to Node L. If you want Node L to resume the role of primary, then an administrative switchover should be performed.