Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

142About Veritas Storage Foundation and High Availability SolutionsSoftware limitationsVVR support for replicating across Storage Foundation versionsVVR supports replication between Storage Foundation 6.0 and the prior majorreleases of Storage Foundation (5.1 and 5.1SP1). Replication between versions issupported for disk group versions 150, 160, and 170 only. Both the Primary andSecondary hosts must be using a supported disk group version.Thin reclamation requests are not redirected even when theioship policy is enabled (2755982)Reclamation requests fail from nodes that do not have local connectivity to thedisks, even when the ioship policy is enabled. Reclamation I/Os are not redirectedto another node.Veritas Operations Manager does not support disk, disk group,and volume state information related to CVM I/O shippingfeature (2781126)The Veritas Operations Manager (VOM) does not support disk, disk group, andvolume state information related to the I/O shipping feature introduced in thisrelease of Cluster Volume Manager. New states such as lfailed, lmissing orLDISABLED are introduced when I/O shipping is active because of storagedisconnectvity.Veritas Storage Foundation Cluster File System High Availabilitysoftware limitationsThis section describes the Veritas Storage Foundation Cluster File System HighAvailability software limitations in 6.0.3 and 6.0.1.cfsmntadm command does not verify the mount options(2078634)You must confirm the mount options are correct which are then passed to thecfsmntadm command. If the mount options are not correct, the mount fails andthe CFSMount resource will not come online. You can check the VCS engine logfile for any mount failure messages.Stale SCSI-3 PR keys remain on disk after stopping the clusterand deporting the disk groupWhen all nodes present in the SF cluster are removed from the cluster, the SCSI-3Persistent Reservation (PR) keys on the data disks may not get preempted. As aresult, the keys may be seen on the disks after stopping the cluster or after the
About Veritas Storage Foundation and High Availability SolutionsSoftware limitations143nodes have booted up. The residual keys do not impact data disk fencing as theywill be reused or replaced when the nodes rejoin the cluster. Alternatively, thekeys can be cleared manually by running the vxfenclearpre utility.For more information on the vxfenclearpre utility, see the Veritas StorageFoundation Administrator's Guide.Veritas Storage Foundation for Oracle RAC software limitationsThis section describes the Veritas Storage Foundation for Oracle RAC softwarelimitations in 6.0.3 and 6.0.1.Oracle Clusterware/Grid Infrastructure installation fails if thecluster name exceeds 14 charactersSetting the cluster name to a value that exceeds 14 characters during theinstallation of Oracle Clusterware/Grid Infrastructure causes unexpected clustermembership issues. As a result, the installation may fail.Workaround: Restart the Oracle Clusterware/Grid Infrastructure installationand set the cluster name to a value of maximum 14 characters.Web installation program does not support phased upgradeand native operating system upgrade mechanismsThe Web installation program does not support phased upgrade and nativeoperating system upgrade mechanisms such as Live Upgrade.Policy-managed databases not supported by CRSResourceagentThe CRSResource agent supports only admin-managed database environmentsin this release. Policy-managed databases are not supported.Health checks may fail on clusters that have more than 10nodesIf there are more than 10 nodes in a cluster, the health check may fail with thefollowing error:vxgettext ERROR V-33-1000-10038Arguments exceed the maximum limit of 10The health check script uses the vxgettext command, which does not supportmore than 10 arguments.[2142234]
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:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92: About Veritas Storage Foundation an
Page 141: About Veritas Storage Foundation an
Page 149 and 150: Chapter2Installing the products for
Page 151 and 152: Installing the products for the fir
Page 153 and 154: Installing the products for the fir
Page 155 and 156: Chapter3Installing the productsusin
Page 157 and 158: Installing the products using JumpS
Page 163 and 164: Chapter4Upgrading to 6.0.3This chap
Page 165 and 166: 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:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
AppendixAConfiguring VCS to managea
Page 223 and 224:
Configuring VCS to manage a Logical
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
show all

Veritas Storage Foundation and High Availability Solutions Release Notes

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

Delete template?

Save as template?