ActiveActive Configuration The activeactive configuratio n balances resources

Active/Active Configuration The active/active configuratio n balances resources across both nodes in the cluster to achieve optimum performanc e.

The active/active configuration contains two nodes that are providing resources to cluster clients. This configuration provides optimum performance because it balances resources across both nodes in the cluster. Each node controls a different resource group. The active/active configuration can also provide static load balancing, which refers to a failback policy. If one node fails, the other node will temporarily take on all of the groups. When the failed node comes back online, the group fails back to the original node, allowing performance to return to normal. In general, this configuration is the one most often used in server clusters. l Depending on the resources and the capacity of the nodes, performance may suffer when a failover occurs and a single node must run all of the resources. l In this slide, Node A is the primary owner of Group 1, and Node B is the primary owner of Group 2. If Node B goes offline, Group 2 will fail over to Node A. When Node B goes back online, Group 2 will fail back to Node B. Performance is restored when the failed node comes back online and the group fails back to its original node. l

Considerations for Choosing this Configuration Choose this configuration when you need to provide multiple resources simultaneously from a single cluster, provided that you can accept reduced performance during a failover. l Choose the active/active configuration if your needs meet the following: – You require multiple groups for applications and services. – You want failover capability for the applications and services. – You want all the groups to fail back to their preferred owners when the failed node returns online to redistribute the load. – The applications and services support a cluster l

Availability l This configuration provides high performance until failover. When a single node runs all of the resources, performance will degrade.

Failover Policy l Configure all of the groups to fail over, and then to fail back when the original node owner is back online.