Can we configure VCS 5.1 HA so that disk groups , file systems related one application in a Solaris 10 Non global zone can be failed over to non global one in 2nd node with out effecting the other application running in same non global zone?

[Ravent]

Can any one provide any help with this question?

Can we configure VCS 5.1 HA so that  disk groups , file systems related one application in a Solaris 10 Non global zone can be failed over to non global zone in 2nd node with out effecting the other application running in same non global zone?

[Gaurav_S]

Hello,

Let me understand this clearly, so lets say you have 2 nodes A & B , which runs service groups SG1 & SG2 respectively... SG1 has local zone Z1 which runs application A1 & node 2 runs SG2 which has local zone Z2 with application A2 .. Now you want to failover diskgroup/filesystems of Z1 to go to node B without affecting application A2 & zone Z2 ?

-- you want to failover resources however you don't want to failover zone itself ? or you are saying that zone should also move to node B ?

-- In your question you are asking "without affecting application running in same non,local zone ", can you elaborate on this one ? what are you refering to "same" ? is that the zone on source machine or on target machine ?

-- lastly, what is SF/VCS version you are using ? are you planning for installation or you are facing some issues which you want to solve ?

Gaurav

[mikebounds · Accepted solution]

Yes, you can do this - I have done this for several customers.  You can configure Zone in a Parallel service group (or you can leave zone resource out of VCS completely, but configuring in a zone, means VCS can restart zone if it goes down).

Then configure your application in a separate failover service group that is dependent on the zone parallel service group.  You may have to localise some attributes so for example for direct mounts you would have:

   Mount MountPointX (
  FsckOpt = "-y"
  BlockDevice = "/dev/vx/dsk/DiskGroupY/VolumeX"
  MountPoint @NodeA = "/export/zones/ZoneA/root/MountPointX"
  MountPoint @NodeB = "/export/zones/ZoneB/root/MountPointX"
  FSType = vxfs
)  

Mike

[Anoop_Kumar1]

I believe advised configuation by Mike should work. You need to monitor application in local zone using containername attribute.

Regards,

~Anoop

[mikebounds]

Anoop, using containername attribute is how you would do this in 5.0, Ravent is using 5.1, so needs to use ContainerInfo Service group attribute.

Mike