Before you start the rolling upgrade, make sure that Veritas Cluster Server (VCS) is running.
Note: |
Before performing a rolling upgrade from version 5.1SP1RP3 to version 6.0, install patch VRTSvxfen-5.1SP1RP3P2. For downloading the patch, search VRTSvxfen-5.1SP1RP3P2 in Patch Lookup on the SORT website. |
To perform a rolling upgrade
# ./installer
If you choose to create a backup boot disk, type y. Provide a backup name for the boot disk group or accept the default name. The installer then creates a backup copy of the boot disk group.
See Re-joining the backup boot disk group into the current disk group.
See Reverting to the backup boot disk group after an unsuccessful upgrade.
The installer lists the RPMs to upgrade on the selected node or nodes.
The installer fails over failover service groups to the node or nodes that are not upgraded at this time. The downtime is the time that it normally takes for the service group's failover. The installer stops parallel service groups on the nodes that are to be upgraded.
It performs the configuration for the upgrade and re-starts processes.
In case of failure in the startup of some of the processes, you may need to reboot the nodes and manually check the cluster's status.
If the installer reboots nodes, restart the installer.
The installer repeats step 6 through step 11.
For clusters with larger number of nodes, this process may repeat several times. Service groups come down and are brought up to accommodate the upgrade.
If the boot disk is encapsulated, you need to reboot nodes when phase 1 completes.
The installer performs prechecks, uninstalls old RPMs, and installs the new RPMs. It performs post-installation tasks, and the configuration for the upgrade.
If updates are discovered, you can apply them now.
For instructions to upgrade VCS or SFHA on the CP server systems, refer to the appropriate installation guide.