Veritas Storage Foundation™ and High Availability Solutions ...

More documents

Recommendations

Info

24Storage Foundation and High Availability Solutions support for Solaris ZonesConfiguring VCS in zonesFirstReview the prerequisites.See “Prerequisites for configuring VCS in zones” on page 24.SecondDecide on the location of the zone root, which is either on local storageor shared storage.See “Deciding on the zone root location” on page 25.ThirdInstall the application in the zone.See “About installing applications in a zone” on page 28.FourthCreate the application service group and configure its resources.See “Configuring the service group for the application” on page 29.Prerequisites for configuring VCS in zonesReview the following prerequisites for configuring VCS in zones:■■VCS supports CFS, UFS, and VxFS mounts for the zone root.File system mounts must meet one of the following two conditions:■■Use a loopback file system. All mounts that the application uses must bepart 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 systemcontaining 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. Anexample is /export/home/oradata, which the mount directory in thenon-global zone maps to. The MountPoint attribute of the Mount resourcefor the application is set to /export/home/oradata. Confirm that/export/home/oradata maps to /oradata with the command zonecfg -zzone_name info. You can also look into the zone configuration file/etc/zones/zone_name.xml. The Zone resource depends on the Mountresource.Use a direct mount file system. All file system mount points that theapplication uses that run in a zone must be set relative to the zone’s root.For example, if the Oracle application uses /oradata, and you create thezone with the zonepath as /z_ora, then the mount must be/z_ora/root/oradata. The MountPoint attribute of the Mount resource mustbe set to this path. The Mount resource depends on the Zone resource.Note: The Mount agent does not support mounting VxFS file systemsdirectly inside non-global zones.
Storage Foundation and High Availability Solutions support for Solaris ZonesConfiguring VCS in zones25Using custom agents in zonesIf you use custom agents, review the following information for their use in zones:■■■If you use custom agents to monitor the applications that run in zones, makesure that the agents use script-based entry points. VCS does not supportrunning C++ entry points inside a zone.If you want the custom agent to monitor an application in the zone, for thecustom agent type, set the following values for the ContainerOpts attribute:RunInContainer = 1 and the PassCInfo = 0.If you don't want the custom agent to monitor an application in the zone, forthe custom agent type, set the following values for the ContainerOpts attribute:RunInContainer = 0 and the PassCInfo = 0.■ Two main use cases exist where you might want to use a RunInContainer = 0and PassCInfo = 1, descriptions of these follow.Deciding on the zone root location■■The first is the Zone agent's use of these values. The Zone agent's entrypoints cannot run inside of the non-global zone but the agent itself managesthe zone. RunInContainer requires a value of 0 because the agent must runin the global zone. PassCInfo has a value of 1 because the Zone agentrequires the name of the container from the ContainerInfo service groupattribute.The second case is how the IP agent uses RunInContainer and PassCInfo.The IP agent's entry points must run outside of the non-global zone becausea shared-IP zone may cause the networking stack to not completely run inthe non-global zone. You cannot perform an ifconfig command and thenplumb the IP from inside of a non-global zone. When you run the ifconfigcommand in the global zone with the zone option - it plumbs the IP andmakes it available to the zone that you specify. The need for the container'sname comes from the use of this command, even though it cannot run inthe container. This is applicable to all networking agents.Each zone has its own section of the file system hierarchy in the zone rootdirectory. Processes that run in the zone can access files only within the zoneroot.You can set the zone root in the following two ways:■■Zone root on local storageIn this configuration, you must configure and install a zone on each node inthe cluster.Zone root on shared storage
Page 1 and 2: Veritas Storage Foundationand High
Page 4 and 5: Technical SupportContacting Technic
Page 6 and 7: Support agreement resourcesIf you w
Page 8 and 9: 8ContentsModifying the service grou
Page 10 and 11: 10ContentsInstalling and configurin
Page 12 and 13: 12ContentsSupported deployment mode
Page 14 and 15: 14Overview of Veritas Storage Found
Page 18 and 19: 18Storage Foundation and High Avail
Page 74 and 75:
74Storage Foundation and High Avail
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
100Storage Foundation and High Avai
Page 102 and 103:
102Storage Foundation and High Avai
Page 104 and 105:
104Veritas Cluster Server support f
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
110Veritas Cluster Server: Configur
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158:
show all

Veritas Storage Foundation™ and High Availability Solutions ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?