Veritas Storage Foundation™ and High Availability Solutions ...

Veritas Storage Foundation™ and High Availability Solutions ... Veritas Storage Foundation™ and High Availability Solutions ...

sfdoccentral.symantec.com
from sfdoccentral.symantec.com More from this publisher
12.07.2015 Views

22Storage Foundation and High Availability Solutions support for Solaris ZonesAbout VCS support for zonesWhere /zones/zone-test is the zone root of the local zone.Bringing a Mount resource online in the zoneThe Mount resource is brought online in the global zone by default(RunInContainer = 0). If you want to bring a mount resource online inside thenon-global zone, perform the following:■■Export the block device to the zone through zone configuration. Ensure thatthe raw volume is used appropriately to prevent the possibility of datacorruption.Modify the ContainerInfo attribute for the service group and set values for theName, Type, and Enabled keys.# hagrp -modify service_group ContainerInfo Name zone_name\Type Zone Enabled 1■■Override the ContainerOpts attribute at the resource level.Set the value of the RunInContainer key to 1, for example:# hares -override Mountres ContainerOpts# hares -modify Mountres ContainerOpts\RunInContainer 1 PassCInfo 0For information on overriding resource type static attributes, refer to the VeritasCluster Server Administrator's Guide.Selecting the proper attribute values for a Mount resource forNFS mountsFor NFS mounts, you must mount in the non-global zone.■■Modify the ContainerInfo attribute for the service group and set values forName, Type and Enabled keys.Override the ContainerOpts attribute at the resource level.■ Set the value of the RunInContainer key to 1.Set the RIC value to 1. When you set RIC=1, specify the value of the MountPointattribute relative to the zone root, for example:BlockDevice = abc:/fs1MountPoint = /mnt1The file system is mounted on /zone root/mnt1.

Storage Foundation and High Availability Solutions support for Solaris ZonesConfiguring VCS in zones23About networking agentsEnable the attribute ExclusiveIPZone for resources of type IP and NIC when theseresources are configured to manage the IP and the NIC inside an exclusive-IPzone. This attribute is disabled by default. The IP agent and the NIC agent assumesthe native zone (shared-IP).VCS brings resources online in the global zone by default.If you want to bring these resources online inside the exclusive-IP zone, performthe following tasks:■Make sure that the resource is in a service group that has valid ContainerInfoattribute value configured.■ Set the value of the ExclusiveIPZone attribute to 1.Note: The exclusive-IP zone supports the IP and NIC networking agents. For moreinformation about these agents, see the Veritas Cluster Server Bundled AgentsReference Guide.About the Zone agentThe Zone agent monitors zones, brings them online, and takes them offline. Formore information about the agent, see the Veritas Cluster Server Bundled AgentsReference Guide.Use hazonesetup utility to create user account with group administrativeprivileges. The DeleteVCSZoneUser attribute of zone resource controls removingthe user account when the zone resource is taken offline. For more information,see the Veritas Cluster Server Bundled Agents Reference Guide.About configuring failovers among physical and virtual serversYou can configure VCS to fail over from a physical system to a virtual system andvice versa. A physical to virtual failover gives an N + N architecture in an N + 1environment. For example, several physical servers with applications can failover to containers on another physical server.See “Configuring for physical to virtual and virtual to physical failovers—a typicalsetup” on page 38.Configuring VCS in zonesConfiguring VCS in zones involves the following tasks:

<strong>Storage</strong> Foundation <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong> support for Solaris ZonesConfiguring VCS in zones23About networking agentsEnable the attribute ExclusiveIPZone for resources of type IP <strong>and</strong> NIC when theseresources are configured to manage the IP <strong>and</strong> the NIC inside an exclusive-IPzone. This attribute is disabled by default. The IP agent <strong>and</strong> the NIC agent assumesthe native zone (shared-IP).VCS brings resources online in the global zone by default.If you want to bring these resources online inside the exclusive-IP zone, performthe following tasks:■Make sure that the resource is in a service group that has valid ContainerInfoattribute value configured.■ Set the value of the ExclusiveIPZone attribute to 1.Note: The exclusive-IP zone supports the IP <strong>and</strong> NIC networking agents. For moreinformation about these agents, see the <strong>Veritas</strong> Cluster Server Bundled AgentsReference Guide.About the Zone agentThe Zone agent monitors zones, brings them online, <strong>and</strong> takes them offline. Formore information about the agent, see the <strong>Veritas</strong> Cluster Server Bundled AgentsReference Guide.Use hazonesetup utility to create user account with group administrativeprivileges. The DeleteVCSZoneUser attribute of zone resource controls removingthe user account when the zone resource is taken offline. For more information,see the <strong>Veritas</strong> Cluster Server Bundled Agents Reference Guide.About configuring failovers among physical <strong>and</strong> virtual serversYou can configure VCS to fail over from a physical system to a virtual system <strong>and</strong>vice versa. A physical to virtual failover gives an N + N architecture in an N + 1environment. For example, several physical servers with applications can failover to containers on another physical server.See “Configuring for physical to virtual <strong>and</strong> virtual to physical failovers—a typicalsetup” on page 38.Configuring VCS in zonesConfiguring VCS in zones involves the following tasks:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!