Cluster Server Installation Guide for Solaris x64 5.0 - Storage ...
Cluster Server Installation Guide for Solaris x64 5.0 - Storage ... Cluster Server Installation Guide for Solaris x64 5.0 - Storage ...
188 Advanced topics related to installing VCSMinimal downtime upgradeset-addrset-addrset-addr2 link2 192.1.6.23 link1 192.1.7.33 link2 192.1.8.3#disable LLT broadcastsset-bcasthb 0set-arp0Minimal downtime upgradeSupported upgradesUse a minimal downtime upgrade to upgrade VCS. This procedure minimizesdowntime for the cluster that you want to upgrade. In situations where you canfail over all your service groups to running nodes, downtime equals the timethat it takes to offline and online the service groups. In situations where youhave a service group that you cannot fail over to a running node during upgrade,downtime for that service group equals the time that it takes to perform anupgrade and reboot the node.Use this procedure to upgrade from VCS 4.0 or 4.1.Prerequisites for a minimal downtime upgradeBefore you start the upgrade, confirm that you have licenses for all the nodesthat you plan to upgrade.Planning for the minimal downtime upgrade■■Plan out the movement of the service groups from node to node in order tominimize the downtime for any particular service group.Some rough guidelines are:■■Minimal downtime upgrade limitationsSplit the cluster in half. If the cluster has an odd number of nodes,calculate (n+1)/2, and start the upgrade with the even number of nodes.Split the cluster so that your high priority service groups remain onlineduring the upgrade of the first subcluster.The following limitations primarily describe not tampering with configurationsor service groups during the minimum downtime upgrade.■While you perform the upgrades, do not choose any configuration options.
Advanced topics related to installing VCSMinimal downtime upgrade189■■■■■While you perform the upgrades, do not start any modules.When you start the installer, only select VCS.While you perform the upgrades, do not add or remove service groups to anyof the nodes.Depending on your configuration, you may find that you cannot upgrademultiple nodes at the same time. You may only be able to upgrade one nodeat a time.For very large clusters, you might have to repeat these steps multiple timesto upgrade your cluster.Minimal downtime upgrade exampleIn this example, you have four nodes: node01, node02, node03, and node04. Youalso have four service groups: sg1, sg2, sg3, and sg4. Each service group isrunning on one node.■■■■node01 runs sg2.node02 runs sg1.node03 runs sg4.node04 runs sg3.In your system list, you have each service group failing over to one other node.■■■■sg1 can fail over between node01 and node02.sg2 can fail over between node01 and node03.sg3 can fail over between node01 and node04.sg4 can fail over between node03 and node04.Figure A-2Four nodes, four service groups, and their failover pathssg4node01node02node03node04sg1sg2sg3
- Page 138 and 139: 138 Verifying the VCS installationV
- Page 140 and 141: 140 Verifying the VCS installationV
- Page 142 and 143: 142 Verifying the VCS installationA
- Page 144 and 145: 144 Upgrading to VCS 5.0Upgrading V
- Page 146 and 147: 146 Upgrading to VCS 5.0Upgrading V
- Page 148 and 149: 148 Upgrading to VCS 5.0Upgrading V
- Page 150 and 151: 150 Upgrading to VCS 5.0Upgrading V
- Page 152 and 153: 152 Upgrading to VCS 5.0Upgrading t
- Page 154 and 155: 154 Upgrading to VCS 5.0
- Page 156 and 157: 156 Adding and removing cluster nod
- Page 158 and 159: 158 Adding and removing cluster nod
- Page 160 and 161: 160 Adding and removing cluster nod
- Page 162 and 163: 162 Adding and removing cluster nod
- Page 164 and 165: 164 Adding and removing cluster nod
- Page 166 and 167: 166 Installing VCS on a single node
- Page 168 and 169: 168 Installing VCS on a single node
- Page 170 and 171: 170 Installing VCS on a single node
- Page 172 and 173: 172 Installing VCS on a single node
- Page 174 and 175: 174 Installing VCS on a single node
- Page 176 and 177: 176 Installing VCS on a single node
- Page 178 and 179: 178 Advanced topics related to inst
- Page 180 and 181: 180 Advanced topics related to inst
- Page 182 and 183: 182 Advanced topics related to inst
- Page 184 and 185: 184 Advanced topics related to inst
- Page 186 and 187: 186 Advanced topics related to inst
- Page 190 and 191: 190 Advanced topics related to inst
- Page 192 and 193: 192 Advanced topics related to inst
- Page 194 and 195: 194 Configuring the Symantec Licens
- Page 196 and 197: 196 Configuring the Symantec Licens
- Page 198 and 199: 198 Configuring the Symantec Licens
- Page 200 and 201: 200 IndexDdata disksfor I/O fencing
- Page 202 and 203: 202 IndexrequirementsEthernet contr
- Page 204: 204 Index
188 Advanced topics related to installing VCSMinimal downtime upgradeset-addrset-addrset-addr2 link2 192.1.6.23 link1 192.1.7.33 link2 192.1.8.3#disable LLT broadcastsset-bcasthb 0set-arp0Minimal downtime upgradeSupported upgradesUse a minimal downtime upgrade to upgrade VCS. This procedure minimizesdowntime <strong>for</strong> the cluster that you want to upgrade. In situations where you canfail over all your service groups to running nodes, downtime equals the timethat it takes to offline and online the service groups. In situations where youhave a service group that you cannot fail over to a running node during upgrade,downtime <strong>for</strong> that service group equals the time that it takes to per<strong>for</strong>m anupgrade and reboot the node.Use this procedure to upgrade from VCS 4.0 or 4.1.Prerequisites <strong>for</strong> a minimal downtime upgradeBe<strong>for</strong>e you start the upgrade, confirm that you have licenses <strong>for</strong> all the nodesthat you plan to upgrade.Planning <strong>for</strong> the minimal downtime upgrade■■Plan out the movement of the service groups from node to node in order tominimize the downtime <strong>for</strong> any particular service group.Some rough guidelines are:■■Minimal downtime upgrade limitationsSplit the cluster in half. If the cluster has an odd number of nodes,calculate (n+1)/2, and start the upgrade with the even number of nodes.Split the cluster so that your high priority service groups remain onlineduring the upgrade of the first subcluster.The following limitations primarily describe not tampering with configurationsor service groups during the minimum downtime upgrade.■While you per<strong>for</strong>m the upgrades, do not choose any configuration options.
Change language