Solaris Cluster and Zones

Read http://blogs.sun.com/Maddy/entry/making_sense_of_zones_in for details,

Summary to remember,

FAILOVER ZONE/HA ZONE:
- zone failover from one cluster node to the other
- application running inside the zone has to switch with the zone
- application monitoring has to be done by SMF inside the zone, Sun Cluster agents are not monitoring the applications (more appropriate for legacy applications with no proven cluster agents)
- It supports branded zones (Solaris 8, Solaris 9 and lx branded zones (Linux branded)) apart from native zone (Solaris 10)
- Read more - http://docs.sun.com/app/docs/doc/819-2664/6n4uhp5gq?a=view
- Example - http://www.sun.com/bigadmin/content/submitted/ha_containers_zfs.jsp

ZONE NODE:
- zones to be treated like physical nodes to be part of Resource Groups
- It is best for applications which are supported with containers and have a Sun Cluster agent
- application running inside the zone can failover to other zone or physical node
- It supports only native zone as a zone node
- it is more useful,
o applications which are scalable and have to hosted exclusively in zones
o application running in a combination of physical nodes and zones
- Read more - http://docs.sun.com/app/docs/doc/819-2969/gcbkf?a=view

ZONE CLUSTER:
- introduces a new brand of zone called "cluster”
- A single physical cluster can be partitioned and many virtual clusters can be created for hosting different applications/isolate the application and data
- Still have a specific usage for Deploying Oracle RAC in Zone Clusters.
- clzonecluster is the utility for configurations
- Read more - http://docs.sun.com/app/docs/doc/820-4677/ghcoa?a=view