Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
184Upgrading to 6.0.3Upgrading to 6.0.3About rolling upgradesYou can use rolling upgrades to upgrade one product from a release to the next.Rolling upgrades require less downtime.Rolling upgrades take two discrete phases. In the first, you upgrade the kernelpackages with exception of VCS packages and agent packages. In the second, youupgrade the non-kernel packages, which are VCS packages and agents packages.You can perform a rolling upgrade for the following products:■■■■■■Veritas Cluster ServerStorage Foundation and High AvailabilityStorage Foundation Cluster File System and High AvailabilityStorage Foundation for Oracle RACSymantec VirtualStoreStorage Foundation for Sybase CEYou can perform a rolling upgrade from 6.0.1 to 6.0.3.Prerequisites for a rolling upgradesMeet the following prerequisites before performing a rolling upgrade:■■■■■■Make sure that the product you want to upgrade supports rolling upgrade.Split up your cluster into sub-clusters for the purpose of upgrade. A sub-clustercan include one or more nodes. This division helps to keep service groupsrunning during the upgrade.Make sure you are logged in as superuser and have the media mounted.VCS must be running before performing the rolling upgrade.For SF Oracle RAC, stop Oracle Clusterware before upgrading Kernel packageson any node, which is not managed by VCS.Make sure you have downloaded the latest software required for the upgrade.See “Downloading required software to upgrade to 6.0.3 ” on page 163.Limitation: During VCS and agents upgrade, you must bring down the applicationHigh Availability (HA) for several minutes. This does not affect the applicationrunning on the cluster. You can restore the application's high availability afterVCS and the agent packages are upgraded.
Upgrading to 6.0.3Upgrading to 6.0.3185Performing a rolling upgrade using the installerYou can use rolling upgrades to upgrade one product from a release to the nextwith minimal application downtime.Performing a rolling upgrade on kernel packages for VCS, SFHA,SFSYBASECE, SVS and SFCFSHA: phase 1Note that in the following instructions a sub-cluster can represent one or morenodes in a full cluster, but is represented by nodeA.To perform the rolling upgrade on kernel packages: phase 11 Stop all the applications that access volumes which are not under VCS controlin the sub-cluster to be upgraded.2 Unmount all the file systems managed by SF which are not under VCS controlin the sub-cluster to be upgraded.3 On the first sub-cluster, start the installer for the rolling upgrade with the-rollingupgrade_phase1 option.# ./installmr -rollingupgrade_phase1 nodeA4 Note that if the boot-disk is encapsulated, then you do not need to performan unencapsulation for upgrades.5 The installer checks system communications, release compatibility, versioninformation, and lists the cluster name, ID, and cluster nodes. Type y tocontinue.6 The installer inventories the running service groups and determines the nodeor nodes to upgrade in phase 1 of the rolling upgrade. Type y to continue. Ifyou choose to specify the nodes, type n and enter the names of the nodes.7 The installer performs further prechecks on the nodes in the cluster and maypresent warnings. You can type y to continue or quit the installer and addressthe precheck's warnings.8 After the installer shows the package list, it detects if there are online failoverservice groups on the nodes to be upgraded. If there are online failover servicegroups, the installer prompts you to do one of the following:■■Manually switch service groupsUse the CPI to automatically switch service groupsThe downtime is the time that it normally takes for the service group'sfailover.
- Page 133 and 134: About Veritas Storage Foundation an
- Page 135 and 136: About Veritas Storage Foundation an
- Page 137 and 138: About Veritas Storage Foundation an
- Page 139 and 140: About Veritas Storage Foundation an
- Page 141 and 142: About Veritas Storage Foundation an
- Page 143 and 144: About Veritas Storage Foundation an
- Page 145 and 146: About Veritas Storage Foundation an
- Page 147 and 148: 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 159 and 160: Installing the products using JumpS
- Page 161 and 162: 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 167 and 168: Upgrading to 6.0.3Upgrading to 6.0.
- Page 169 and 170: Upgrading to 6.0.3Upgrading to 6.0.
- Page 171 and 172: Upgrading to 6.0.3Upgrading to 6.0.
- Page 173 and 174: Upgrading to 6.0.3Upgrading to 6.0.
- Page 175 and 176: Upgrading to 6.0.3Upgrading to 6.0.
- Page 177 and 178: Upgrading to 6.0.3Upgrading to 6.0.
- Page 179 and 180: Upgrading to 6.0.3Upgrading to 6.0.
- Page 181 and 182: Upgrading to 6.0.3Upgrading to 6.0.
- Page 183: Upgrading to 6.0.3Upgrading to 6.0.
- 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
184Upgrading to 6.0.3Upgrading to 6.0.3About rolling upgradesYou can use rolling upgrades to upgrade one product from a release to the next.Rolling upgrades require less downtime.Rolling upgrades take two discrete phases. In the first, you upgrade the kernelpackages with exception of VCS packages <strong>and</strong> agent packages. In the second, youupgrade the non-kernel packages, which are VCS packages <strong>and</strong> agents packages.You can perform a rolling upgrade for the following products:■■■■■■<strong>Veritas</strong> Cluster Server<strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong><strong>Storage</strong> <strong>Foundation</strong> Cluster File System <strong>and</strong> <strong>High</strong> <strong>Availability</strong><strong>Storage</strong> <strong>Foundation</strong> for Oracle RACSymantec VirtualStore<strong>Storage</strong> <strong>Foundation</strong> for Sybase CEYou can perform a rolling upgrade from 6.0.1 to 6.0.3.Prerequisites for a rolling upgradesMeet the following prerequisites before performing a rolling upgrade:■■■■■■Make sure that the product you want to upgrade supports rolling upgrade.Split up your cluster into sub-clusters for the purpose of upgrade. A sub-clustercan include one or more nodes. This division helps to keep service groupsrunning during the upgrade.Make sure you are logged in as superuser <strong>and</strong> have the media mounted.VCS must be running before performing the rolling upgrade.For SF Oracle RAC, stop Oracle Clusterware before upgrading Kernel packageson any node, which is not managed by VCS.Make sure you have downloaded the latest software required for the upgrade.See “Downloading required software to upgrade to 6.0.3 ” on page 163.Limitation: During VCS <strong>and</strong> agents upgrade, you must bring down the application<strong>High</strong> <strong>Availability</strong> (HA) for several minutes. This does not affect the applicationrunning on the cluster. You can restore the application's high availability afterVCS <strong>and</strong> the agent packages are upgraded.
Change language