Tanti Technology

My photo
Bangalore, karnataka, India
Sandeep Kumar | Founder, Tanti Technologies At Tanti Technologies, I share practical knowledge, hands-on tutorials, and real-world solutions across Python, SQL, Docker, Kubernetes, CI/CD, AWS, Azure, Machine Learning, Generative AI, and Agentic AI. My mission is to simplify complex technologies and provide actionable insights that help developers, engineers, and businesses learn faster, build better, automate smarter, and innovate with confidence. 🚀 Learn • Build • Automate • Innovate Follow Tanti Technologies for practical technology insights and next-generation AI solutions.

Monday, 4 July 2011

HACMP CAN BE CONFIGURED IN 3 WAYS.

HACMP CAN BE CONFIGURED IN 3 WAYS.


1. Rotating

2. Cascading

3. Mutual Failover

The cascading and rotating resource groups are the “classic”, pre-HA 5.1 types. The new “custom” type

of resource group has been introduced in HA 5.1 onwards.

Cascading resource group:

Upon node failure, a cascading resource group falls over to the available node with the next priority in

the node priority list.

Upon node reintegration into the cluster, a cascading resource group falls back to its home node by

default.

Cascading without fallback

Thisoption, this means whenever a primary node fails, the package will failover to the next available

node in the list and when the primary node comes online then the package will not fallback

automatically. We need to move package to its home node at a convenient time.

Rotating resource group:

This is almost similar to Cascading without fallback, whenever package failover to the standby nodes it

will never fallback to the primary node automatically, we need to move it manually at our convenience.



Mutual takeover:

Mutual takeover option, which means both the nodes in this type are active-active mode. Whenever fail

over happens the package on the failed node will move to the other active node and will run with

already existing package. Once the failed node comes online we can move the package manually to that

node.

No comments:

Post a Comment