All nodes hosting applications configured in zones must be running the same version of the operating system.
VCS supports UFS and VxFS mounts for the zone root; VCS does not support CFS mounts for the zone root.
The autoboot property for the zone must be set to false.
Mounts must meet one of the following two conditions:
Use a loop-back file system. In this case, all mounts used by the application must be part of the zone configuration and must be configured in the service group. For example, you can create a zone, z-ora, and define the file system containing the application's data to have the mount point as /oradata. When you create the zone, you can define a path in the global zone, for example /export/home/oradata, that the mount directory in the non-global zone maps to. The MountPoint attribute of the Mount resource for the application is set to /export/home/oradata.
Use a direct mount file system. In this condition, all file system mount points used by the application running in a zone must be set relative to the zone's root. For example, if the Oracle application uses /oradata, and you create the zone with the zonepath as /z_ora, then the mount must be /z_ora/root/oradata. The MountPoint attribute of the Mount resource must be set to this path.
Using custom agents in non-global zones
If you use custom agents to monitor applications running in zones, make sure the agents use script-based entry points. VCS does not support running C++ entry points inside a non-global zone.
If the custom agent monitors an application running in a zone, add the resource type to the APP_TYPES environment variable.
If the custom agent monitors an application running in the global zone, add the resource type to the SYS_TYPES environment variable.
