Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

134About Veritas Storage Foundation and High Availability SolutionsSoftware limitationsCreating point-in-time copies during database structural changes is notsupported (2496178)SFDB tools do not support creating point-in-time copies while structural changesto the database are in progress, such as adding or dropping tablespaces and addingor dropping data files.However, once a point-in-time copy is taken, you can create a clone at any time,regardless of the status of the database.Veritas Cluster Server software limitationsThis section describes the Veritas Cluster Server software limitations in 6.0.3 and6.0.1.Limitations related to bundled agentsVolumes in a disk group start automatically irrespective of the value of theStartVolumes attribute in VCSVolumes in a disk group are started automatically when the disk group is imported,irrespective of the value of the StartVolumes attribute in VCS. This behavior isobserved if the value of the system-level attribute autostartvolumes in VeritasVolume Manager is set to On.Workaround: If you do not want the volumes in a disk group to start automaticallyafter the import of a disk group, set the autostartvolumes attribute to Off at thesystem level.Programs using networked services may stop responding if the host isdisconnectedPrograms using networked services (for example, NIS, NFS, RPC, or a TCP socketconnection to a remote host) can stop responding if the host is disconnected fromthe network. If such a program is used as an agent entry point, a networkdisconnect can cause the entry point to stop responding and possibly time out.For example, if the host is configured to use NIS maps as a client, basic commandssuch as ps -ef can hang if there is network disconnect.Symantec recommends creating users locally. To reflect local users, configure:/etc/nsswitch.confVolume agent clean may forcibly stop volume resourcesWhen the attribute FaultOnMonitorTimeouts calls the Volume agent clean entrypoint after a monitor time-out, the vxvol -f stop command is also issued. Thiscommand forcibly stops all volumes, even if they are still mounted.
About Veritas Storage Foundation and High Availability SolutionsSoftware limitations135False concurrency violation when using PidFiles to monitor applicationresourcesThe PID files created by an application contain the PIDs for the processes thatare monitored by Application agent. These files may continue to exist even aftera node running the application crashes. On restarting the node, the operatingsystem may assign the PIDs listed in the PID files to other processes running onthe node.Thus, if the Application agent monitors the resource using the PidFiles attributeonly, the agent may discover the processes running and report a false concurrencyviolation. This could result in some processes being stopped that are not underVCS control.Online for LDom resource fails [2517350]Online of LDom resource fails when the boot disk configured in the guest domainthat is a part of the virtual disk multi-pathing group (mpgroup) and also theprimary path to the virtual disk is not available.This is due to the limitations in Oracle VM Server that do not allow retrying ofother device paths that exist for the virtual disks, which are part of a virtual diskmulti-pathing group, when booting a guest domain.Workaround: None.Zone agent registered to IMF for Directory Online eventThe Directory Online event monitors the Zone root directory. If the parentdirectory of the Zone root directory is deleted or moved to another location, AMFdoes not provide notification to the Zone agent. In the next cycle of the zonemonitor, it detects the change and reports the state of the resource as offline.LDom resource calls clean entry point when primary domain is gracefullyshut downLDom agent sets failure policy of the guest domain to stop when primary domainstops. Thus when primary domain is shut down, guest domain is stopped.Moreover, when primary domain is shutdown, ldmd daemon is stopped abruptlyand LDom configuration cannot be read. These operations are not under VCScontrol and VCS may call clean entry point.Workaround: No workaround.Application agent limitations■ProPCV fails to prevent execution of script-based processes configured underMonitorProcesses.
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: About Veritas Storage Foundation an
Page 133: 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 185 and 186:
Upgrading to 6.0.3Upgrading to 6.0.
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
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?