Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
238Configuring 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 domainsFigure A-8shows the dependency of LDom service group on the AlternateIOservice group.Configuration notes:■■■Configure the service group as a fail over type service group.The SystemList attribute in the LDom service group must contain only hostnames of the control domains from each physical system in the cluster.The LDom service group must have online local hard dependency with theAlternateIO service group.If the guest domain needs to be made available even when the primary domain isrebooted or shut down for planned maintenance.To make the guest domain available1 Set the LDom resource attribute DomainFailurePolicy to { primary=ignore,alternate1=stop } for all the LDom resources in the cluster which are criticaland needs to be available during primary/control domain maintenance. Thissetting ensure that guest domain will not be brought down whenprimary/control domain is taken down for planned maintenance.# hares -modify DomainFailurePolicy ldmres primary ignore \alternate1 stop2 Set the LDom service group attribute SysDownPolicy to AutoDisableNoOfflineThis setting ensures that VCS will not fail-over the service group even whenthe primary/control domain where the service group is online is taken down.# hagrp -modify ldmsg SysDownPolicy AutoDisableNoOffline
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 domains2393 The service group will be auto-disabled in the cluster when the control domainis taken down for maintenance. Once the control domain is brought onlineagain, clear the auto disabled system by executing the following command:# hagrp -autoenable ldmsg -sys primary14 Once the maintenance for the control domain is completed, set theDomainFailurePolicy attribute to it’s original values (default: {primary =stop}). Also reset the service group attribute SysDownPolicy:# hares -modify ldmres DomainFailurePolicy primary stop# hagrp -modify ldmsg SysDownPolicy -delete AutoDisableNoOfflineSample configuration for LDom service groupThe LDom service group must have online local hard dependency with theAlternateIO service group.group ldmsg (SystemList = { primary1 = 0, primary2 = 1 }AutoStartList = { primary1, primary2 }SysDownPolicy = { AutoDisableNoOffline })LDom ldmres (LDomName = ldg1DominFailurePolicy={ primary=ignore, alternate1="stop"})Failover scenariosScenarioControl domainAlternate I/O domainVCS behaviorState of eachstorage servicegroupOnlineOffline/FAULTOnlineOnlineNo fail overNo fail overOnlineOffline/FAULTNo fail overOffline/FAULTOffline/FAULTFail over
- Page 187 and 188: Upgrading to 6.0.3Upgrading to 6.0.
- 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: Configuring VCS to manage a Logical
- Page 241 and 242: 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 domains2393 The service group will be auto-disabled in the cluster when the control domainis taken down for maintenance. Once the control domain is brought onlineagain, clear the auto disabled system by executing the following comm<strong>and</strong>:# hagrp -autoenable ldmsg -sys primary14 Once the maintenance for the control domain is completed, set theDomainFailurePolicy attribute to it’s original values (default: {primary =stop}). Also reset the service group attribute SysDownPolicy:# hares -modify ldmres DomainFailurePolicy primary stop# hagrp -modify ldmsg SysDownPolicy -delete AutoDisableNoOfflineSample configuration for LDom service groupThe LDom service group must have online local hard dependency with theAlternateIO service group.group ldmsg (SystemList = { primary1 = 0, primary2 = 1 }AutoStartList = { primary1, primary2 }SysDownPolicy = { AutoDisableNoOffline })LDom ldmres (LDomName = ldg1DominFailurePolicy={ primary=ignore, alternate1="stop"})Failover scenariosScenarioControl domainAlternate I/O domainVCS behaviorState of eachstorage servicegroupOnlineOffline/FAULTOnlineOnlineNo fail overNo fail overOnlineOffline/FAULTNo fail overOffline/FAULTOffline/FAULTFail over
Change language