Quote:
Originally Posted by
erice
In what context does SC require SVM? That seems hard to believe.
We use cluster software, VCS, to mount and umount vxfs file systems into local zones the same way we mount and umount vxfs file systems in global zones. We simply specify the mount point as a directory inside the local zone.
Firstly thanks for getting back to me, those commands have corroborated some of the assumptions i have been making.
I think the SVM package is installed anyway (by default), at this stage I dont think it's important I just wanted to verify for the benifit of my documentation.
what i have is:
Legacy database domains (on a 15K) we are migrating to branded zones, on two M5000's.
Those systems currently use VxVM. When they've been migrated to zones they'll still need the VxVM (on the global zone) to run. The containers themselves will be built on ZFS SAN. The oracle data groups are all mounted on UFS filesystems, because we all know; branded zones cant mount ZFS.
Sun cluster 3.2 using HA containers will be installed to the global zones.
What i need to know is: if a container fails over to the other global zone, what do i need to manually share with both of those servers, from a VxVM point of view, to enable that container to come back up?
I understand that SC will move the container over to the other global zone. Though, it wont be able to boot back up and mount it's filesystems if that global zone doesnt know about the others VxVM configuration, regarding the failed over container. So what do i need to do to ensure that happens?