Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

190Upgrading to 6.0.3Upgrading to 6.0.3■Use the CPI to automatically switch service groupsThe downtime is the time that it normally takes for the service group'sfailover.7 After switching failover service group, installer detects if there are onlineparallel service groups on the node to be upgraded. If there are online parallelservice groups, installer will ask user to use CPI to automatically offlineparallel service groups.8 The installer stops relevant processes, uninstalls old kernel packages, andinstalls the new packages. When prompted, enable replication or global clustercapabilities, if required, and register the software.9 The installer performs the upgrade configuration and re-starts processes.If some processes fail to start, you may need to reboot the nodes and manuallycheck the cluster's status.Note: The Oracle service group is offline as the AutoStart attribute is set to0 to prevent the service group from starting automatically. The service groupis started later in the process.10 In case of SFRAC, refer to the “Performing post-upgrade Tasks” section torelink Oracle RAC libraries with SF Oracle RAC from 6.0.1 Installation andConfiguration guide.11 Bring the Oracle database service group online.■If VCS manages the Oracle database:# hagrp -online oracle_group -sys node_name■If VCS does not manage the Oracle database:# srvctl start database -d db_name12 Manually mount the VxFS and CFS file systems that are not managed by VCS.13 Start all applications that VCS does not manage. Use native applicationcommands to start the applications.14 If the boot disk is encapsulated, reboot the first sub-cluster's system.15 Before you proceed to phase 2, complete step 1 to 14 on the second subcluster.16 ■ If VCS manages the Oracle database, reset the AutoStart value to 1 toenable VCS to bring the database service group online when VCS starts:
Upgrading to 6.0.3Upgrading to 6.0.3191# haconf -makerw# hagrp -modify oracle_group AutoStart 1# haconf -dump -makero■If VCS does not manage the Oracle database, change the managementpolicy for the database to automatic:$ srvctl modify database -d db-name -y AUTOMATICPerforming a rolling upgrade on non-kernel packages for SFRAC: phase 2In this phase installer installs all non-kernel packages on all the nodes in clusterand restarts VCS cluster.To perform the rolling upgrade on non-kernel packages: phase 21 When phase 1 of the rolling upgrade completes, begin phase 2 of the upgrade.Phase 2 of the upgrade includes downtime for the VCS engine (HAD), whichdoes not include application downtime. Type y to continue.2 Reboot the nodes if the installer requires.3 The installer determines the remaining packages to upgrade. Press Enter tocontinue.4 The installer stops Veritas Cluster Server (VCS) processes but the applicationscontinue to run. Type y to continue.The installer performs prechecks, uninstalls old packages, and installs thenew packages. It performs post-installation tasks, and the configuration forthe upgrade.5 Type y or n to help Symantec improve the automated installation.6 If you have network connection to the Internet, the installer checks forupdates.7 A prompt message appears to ask if the user would like to read the summaryfile. You can choose y if you want to read the install summary file.8 Verify the cluster's status:# hastatus -sum9 If you want to upgrade CP server systems that use VCS or SFHA to 6.0.3, makesure that you upgraded all application clusters to version 6.0.3. Then, upgradeVCS or SFHA on the CP server systems.For instructions to upgrade VCS or SFHA on the CP server systems, see theVCS or SFHA installation guide.
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:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140: 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 189: 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 221 and 222: AppendixAConfiguring VCS to managea
Page 223 and 224: Configuring VCS to manage a Logical
Page 241 and 242:
Configuring VCS to manage a Logical
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?