Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
22About Veritas Storage Foundation and High Availability SolutionsChanges introduced in 6.0.34 Change the directory to /tmp/sfha603:# cd /tmp/sfha6035 Install 6.0.3:# ./installmr -require complete_path_to_603_installer_patchChanges introduced in 6.0.3This section lists the changes in 6.0.3.Changes introduced in Veritas Cluster Server 6.0.3This section lists the Veritas Cluster Server changes in 6.0.3.Db2udb Agent support extended to DB2 10.1The DB2udb Agent for VCS 6.0.3 now supports DB2 10.1.VCS support for logical domains with control domain rebootin multiple I/O domain environmentWhen an OVM for SPARC guest domain (LDom) is provided with I/O services frommore than one I/O domains (typically the primary domain and the alternate I/Odomain), guest domain continues to function even if the control domain isshutdown or rebooted, as long as the I/O services from other I/O domain areavailable.To use this feature1 Set the LDom resource attribute DomainFailurePolicy with master domainand it's failure policy to ignore (primary domain will be set with 'stop' failurepolicy by default).2 Set the LDom service group attribute SysDownPolicy toAutoDisableNoOffline.See “Configuring VCS to manage a Logical Domain using services from multipleI/O domains” on page 221.The LDom agent has added the following new attribute to support this feature.
About Veritas Storage Foundation and High Availability SolutionsChanges introduced in 6.0.323DomainFailurePolicyThis attribute specifies the list of master domains and the failure policy of masterdomains for a guest domain. The key of the attribute is the name of the masterdomain and the value for the key of the attribute is the failure policy enacted bythe master domain on the guest domain. The failure policy will be enacted by themaster domain in the event of loss of the master domain. The possible values forthe failure policy are ignore, stop, reset, and panic. For more information on thefailure policies of the master domain, refer to the ldm(1M) man page.By default, the DomainFailurePolicy attribute is set with master domain as‘primary’ and failure policy as ‘stop’.The DomainFailurePolicy attribute need to be set to a non-default value only whenthe guest domain is provided with storage and network services from more thanone I/O domain and the guest domain need to be made available even when theprimary domain is rebooted or shut down for maintenance.It is highly recommended to set the same failure policy for a master domain forall the LDom resources (guest domains) configured on a physical system. If theattribute is set to different failure policies for the same master domain for differentLDom resources, then the agent ensures that the failure policy with the highestpriority is set on the master domain. For more information on failure policypriority, see Notes for the DomainFailurePolicy attribute.You can change the attribute value dynamically when the LDom resource is online.The LDom agent ensures the changed failure policy is set on the master domainin the order of priority dynamically, without the need to bring down the LDomresource. For more information on the behavior of this attribute, see the Notesfor the DomainFailurePolicy attribute section.Type-dimension: string-associationDefault: {primary = “stop”}Example: {primary= ignore, secondary = “stop”}. In this example, primary andsecondary are the master domains from where storage and network services areexported to the guest domain.Notes for the DomainFailurePolicy attributeWhen the DomainFailurePolicy attribute is set, the LDom agent sets the masterdomain of the guest domain with the key of the attribute and the value of the keyas the failure policy of the guest domain.The LDom agent uses the following command to set the master for the guestdomain:# ldm set-domain master=master-domain guestldom
- Page 1 and 2: Veritas Storage Foundationand High
- Page 3 and 4: Symantec Corporation350 Ellis Stree
- Page 5 and 6: ■■■■■■■Hardware infor
- Page 7 and 8: ContentsTechnical Support .........
- Page 9 and 10: Contents9Chapter 4 Upgrading to 6.0
- Page 11 and 12: Chapter1About Veritas StorageFounda
- Page 13 and 14: About Veritas Storage Foundation an
- Page 15 and 16: About Veritas Storage Foundation an
- Page 17 and 18: About Veritas Storage Foundation an
- Page 19 and 20: About Veritas Storage Foundation an
- Page 21: About Veritas Storage Foundation an
- Page 25 and 26: About Veritas Storage Foundation an
- Page 27 and 28: About Veritas Storage Foundation an
- Page 29 and 30: About Veritas Storage Foundation an
- Page 31 and 32: About Veritas Storage Foundation an
- Page 33 and 34: About Veritas Storage Foundation an
- Page 35 and 36: About Veritas Storage Foundation an
- Page 37 and 38: About Veritas Storage Foundation an
- Page 39 and 40: About Veritas Storage Foundation an
- Page 41 and 42: About Veritas Storage Foundation an
- Page 43 and 44: About Veritas Storage Foundation an
- Page 45 and 46: About Veritas Storage Foundation an
- Page 47 and 48: About Veritas Storage Foundation an
- Page 49 and 50: About Veritas Storage Foundation an
- Page 51 and 52: About Veritas Storage Foundation an
- Page 53 and 54: About Veritas Storage Foundation an
- Page 55 and 56: About Veritas Storage Foundation an
- Page 57 and 58: About Veritas Storage Foundation an
- Page 59 and 60: About Veritas Storage Foundation an
- Page 61 and 62: About Veritas Storage Foundation an
- Page 63 and 64: About Veritas Storage Foundation an
- Page 65 and 66: About Veritas Storage Foundation an
- Page 67 and 68: About Veritas Storage Foundation an
- Page 69 and 70: About Veritas Storage Foundation an
- Page 71 and 72: About Veritas Storage Foundation an
22About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Changes introduced in 6.0.34 Change the directory to /tmp/sfha603:# cd /tmp/sfha6035 Install 6.0.3:# ./installmr -require complete_path_to_603_installer_patchChanges introduced in 6.0.3This section lists the changes in 6.0.3.Changes introduced in <strong>Veritas</strong> Cluster Server 6.0.3This section lists the <strong>Veritas</strong> Cluster Server changes in 6.0.3.Db2udb Agent support extended to DB2 10.1The DB2udb Agent for VCS 6.0.3 now supports DB2 10.1.VCS support for logical domains with control domain rebootin multiple I/O domain environmentWhen an OVM for SPARC guest domain (LDom) is provided with I/O services frommore than one I/O domains (typically the primary domain <strong>and</strong> the alternate I/Odomain), guest domain continues to function even if the control domain isshutdown or rebooted, as long as the I/O services from other I/O domain areavailable.To use this feature1 Set the LDom resource attribute DomainFailurePolicy with master domain<strong>and</strong> it's failure policy to ignore (primary domain will be set with 'stop' failurepolicy by default).2 Set the LDom service group attribute SysDownPolicy toAutoDisableNoOffline.See “Configuring VCS to manage a Logical Domain using services from multipleI/O domains” on page 221.The LDom agent has added the following new attribute to support this feature.
Change language