Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
240Configuring VCS to manage a Logical Domain using services from multiple I/O domainsConfiguring VCS to manage a Logical Domain using services from multiple I/O domainsScenarioControl domainAlternate I/O domain VCS behaviorState of eachnetwork servicegroupOnlineOffline/FAULTOnlineOnlineNo fail overNo fail overOnlineOffline/FAULTNo fail overOffline/FAULTOffline/FAULTFail overDomain stateUpUpNo fail overUpdownNo fail overDownUpFail over *DowndownFail over *** VCS behavior would be “No fail over” with service group in auto-disabled stateif the LDom resource attribute DomainFailurePolicy for the control domain is setto “ignore” and the LDom service group attribute SysDownPolicy is set to“AutoDisableNoOffline”.** VCS behavior would be “No fail over” with service group in auto-disabled stateif the LDom resource attribute DomainFailurePolicy for the control and other I/Odomain is set to “ignore” and the LDom service group attribute SysDownPolicyis set to “AutoDisableNoOffline”Recommendations while configuring VCS and Oracle VM Server forSPARC with multiple I/O domains■■■Online and offline operations for service groups in the StorageSG attributeTo manually bring online or take offline service groups that are configured inthe StorageSG attribute do not use the AlternateIO resource or its servicegroupInstead, use service groups configured in the StorageSG attribute.Freeze the service group for the AlternateIO resourceFreeze the AlternateIO service group before you bring online or take offlineservice groups configured in the StorageSG attribute of the AlternateIOresource. If you do not freeze the service group, the behavior of the LogicalDomain is unknown as it is dependent on the AlternateIO service group.Configuring preonline trigger for storage service groupsYou must configure preonline trigger in the following scenario:
Configuring VCS to manage a Logical Domain using services from multiple I/O domainsConfiguring VCS to manage a Logical Domain using services from multiple I/O domains241When the service groups configured in the StorageSG attribute of theAlternateIO resource are of fail over type, and if you accidentally bring storageservice groups online on another physical system in the cluster.It is possible to bring the storage service groups online on another physicalsystem because resources configured to monitor back-end storage servicesare present in different service groups on each physical system. Thus, VCScannot prevent resources coming online on multiple systems. This may causedata corruption.Note: Perform this procedure for storage service groups on each node.To configure preonline trigger for each service group listed in the StorageSGattribute■Run the following commands:# hagrp -modify stg-sg TriggerPath bin/AlternateIO/StorageSG# hagrp -modify stg-sg TriggersEnabled PREONLINEwhere stg-sg is the name of the storage service group■Set connection time out period for virtual disksWhen a disk device is not available, I/O services from the guest domain to thevirtual disks are blocked.Symantec recommends to set a connection time out period for each virtualdisk so that applications times out after the set period instead of waitingindefinitely. Run the following command:# ldm add-vdisk timeout=seconds disk_name \volume_name@service_name ldom■Fail over of LDom service group when all the I/O domains are down. When theattribute SysDownPolicy is set to AutoDisableNoOffline for a service group,the service group state would be changed to OFFLINE|AutoDisabled when thesystem on which the service group online goes down. Before auto-enablingthe service group and online the service group on any other nodes, it ismandatory to ensure that guest domain is stopped on the system (controldomain) that is down. This is particularly important when failure-policy ofthe master-domains is set to ignore.Consider the following scenario: The DomainFailurePolicy of the LDom resourceis set to {primary=”stop”} by default.If the guest domain need to be made available even when primary domain isrebooted or shut down for maintenance.
- Page 189 and 190: Upgrading to 6.0.3Upgrading to 6.0.
- Page 191 and 192: Upgrading to 6.0.3Upgrading to 6.0.
- Page 193 and 194: Upgrading to 6.0.3Verifying softwar
- Page 195 and 196: Chapter5Uninstalling version 6.0.3T
- Page 197 and 198: Uninstalling version 6.0.3Rolling b
- Page 199 and 200: Uninstalling version 6.0.3Rolling b
- Page 201 and 202: Uninstalling version 6.0.3Rolling b
- Page 203 and 204: Uninstalling version 6.0.3Rolling b
- Page 205 and 206: Uninstalling version 6.0.3Rolling b
- Page 207 and 208: Uninstalling version 6.0.3Rolling b
- Page 209 and 210: Uninstalling version 6.0.3Rolling b
- Page 211 and 212: Uninstalling version 6.0.3Rolling b
- Page 213 and 214: Uninstalling version 6.0.3Rolling b
- Page 215 and 216: Uninstalling version 6.0.3Rolling b
- Page 217 and 218: Uninstalling version 6.0.3Rolling b
- Page 219 and 220: Uninstalling version 6.0.3Rolling b
- Page 221 and 222: AppendixAConfiguring VCS to managea
- Page 223 and 224: Configuring VCS to manage a Logical
- Page 225 and 226: Configuring VCS to manage a Logical
- Page 227 and 228: Configuring VCS to manage a Logical
- Page 229 and 230: Configuring VCS to manage a Logical
- Page 231 and 232: Configuring VCS to manage a Logical
- Page 233 and 234: Configuring VCS to manage a Logical
- Page 235 and 236: Configuring VCS to manage a Logical
- Page 237 and 238: Configuring VCS to manage a Logical
- Page 239: Configuring VCS to manage a Logical
- Page 243 and 244: Configuring VCS to manage a Logical
- Page 245 and 246: Configuring VCS to manage a Logical
Configuring VCS to manage a Logical Domain using services from multiple I/O domainsConfiguring VCS to manage a Logical Domain using services from multiple I/O domains241When the service groups configured in the <strong>Storage</strong>SG attribute of theAlternateIO resource are of fail over type, <strong>and</strong> if you accidentally bring storageservice groups online on another physical system in the cluster.It is possible to bring the storage service groups online on another physicalsystem because resources configured to monitor back-end storage servicesare present in different service groups on each physical system. Thus, VCScannot prevent resources coming online on multiple systems. This may causedata corruption.Note: Perform this procedure for storage service groups on each node.To configure preonline trigger for each service group listed in the <strong>Storage</strong>SGattribute■Run the following comm<strong>and</strong>s:# hagrp -modify stg-sg TriggerPath bin/AlternateIO/<strong>Storage</strong>SG# hagrp -modify stg-sg TriggersEnabled PREONLINEwhere stg-sg is the name of the storage service group■Set connection time out period for virtual disksWhen a disk device is not available, I/O services from the guest domain to thevirtual disks are blocked.Symantec recommends to set a connection time out period for each virtualdisk so that applications times out after the set period instead of waitingindefinitely. Run the following comm<strong>and</strong>:# ldm add-vdisk timeout=seconds disk_name \volume_name@service_name ldom■Fail over of LDom service group when all the I/O domains are down. When theattribute SysDownPolicy is set to AutoDisableNoOffline for a service group,the service group state would be changed to OFFLINE|AutoDisabled when thesystem on which the service group online goes down. Before auto-enablingthe service group <strong>and</strong> online the service group on any other nodes, it ism<strong>and</strong>atory to ensure that guest domain is stopped on the system (controldomain) that is down. This is particularly important when failure-policy ofthe master-domains is set to ignore.Consider the following scenario: The DomainFailurePolicy of the LDom resourceis set to {primary=”stop”} by default.If the guest domain need to be made available even when primary domain isrebooted or shut down for maintenance.
Change language