Tanti Technology

My photo
Bangalore, karnataka, India
Multi-platform UNIX systems consultant and administrator in mutualized and virtualized environments I have 4.5+ years experience in AIX system Administration field. This site will be helpful for system administrator in their day to day activities.Your comments on posts are welcome.This blog is all about IBM AIX Unix flavour. This blog will be used by System admins who will be using AIX in their work life. It can also be used for those newbies who want to get certifications in AIX Administration. This blog will be updated frequently to help the system admins and other new learners. DISCLAIMER: Please note that blog owner takes no responsibility of any kind for any type of data loss or damage by trying any of the command/method mentioned in this blog. You may use the commands/method/scripts on your own responsibility. If you find something useful, a comment would be appreciated to let other viewers also know that the solution/method work(ed) for you.

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