Search <book_title>...

Cluster Server 7.3.1 Configuration and Upgrade Guide - Solaris

Last Published: 2019-04-17

Product(s): InfoScale & Storage Foundation (7.3.1)

Platform: Solaris

Performing a rolling upgrade using the product installer

Before you start the rolling upgrade, make sure that Cluster Server (VCS) is running on all the nodes of the cluster.

To perform a rolling upgrade

Phase 1 of rolling upgrade begins on the first subcluster. Complete the preparatory steps on the first subcluster.
```
# umount mount_point
```
Log in as superuser and mount the VCS 7.3.1 installation media.
From root, start the installer.
```
# ./installer
```
From the menu, select Upgrade a Product and from the sub menu, select Rolling Upgrade.
The installer suggests system names for the upgrade. Press Enter to upgrade the suggested systems, or enter the name of any one system in the cluster on which you want to perform a rolling upgrade and then press Enter.
The installer checks system communications, release compatibility, version information, and lists the cluster name, ID, and cluster nodes. Type y to continue.
The installer inventories the running service groups and determines the node or nodes to upgrade in phase 1 of the rolling upgrade. Type y to continue. If you choose to specify the nodes, type n and enter the names of the nodes.
The installer performs further prechecks on the nodes in the cluster and may present warnings. You can type y to continue or quit the installer and address the precheck's warnings.
Review the end-user license agreement, and type y if you agree to its terms.
If the boot disk is encapsulated and mirrored, you can create a backup boot disk.
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.
After the installer detects the online service groups, the installer prompts the user to do one of the following:
- Manually switch service groups
- Use the CPI to automatically switch service groups
The downtime is the time that it normally takes for the service group's failover.
Note:
It is recommended that you manually switch the service groups. Automatic switching of service groups does not resolve dependency issues if any dependent resource is not under VCS control.
The installer prompts you to stop the applicable processes. Type y to continue.
The installer evacuates all service groups to the node or nodes that are not upgraded at this time. The installer stops parallel service groups on the nodes that are to be upgraded.
The installer stops relevant processes, uninstalls old kernel packages, and installs the new packages. The installer asks if you want to update your licenses to the current version. Select Yes or No. Veritas recommends that you update your licenses to fully use the new features in the current release.
If the cluster has configured Coordination Point Server based fencing, then during upgrade, installer may ask the user to provide the new HTTPS Coordination Point Server.
The installer performs the upgrade configuration and starts the processes. If the boot disk is encapsulated before the upgrade, installer prompts the user to reboot the node after performing the upgrade configuration.
Complete the preparatory steps on the nodes that you have not yet upgraded.
Unmount all VxFS file systems not under VCS control on all the nodes.
```
# umount mount_point
```
The installer begins phase 1 of the upgrade on the remaining node or nodes. Type y to continue the rolling upgrade. If the installer was invoked on the upgraded (rebooted) nodes, you must invoke the installer again.
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.
The installer determines the remaining packages to upgrade. Press Enter to continue.
The installer displays the following question before the installer stops the product processes. If the cluster was configured in secure mode and version is prior to 6.2 before the upgrade, these questions are displayed.
- Do you want to grant read access to everyone? [y,n,q,?]
  - To grant read access to all authenticated users, type y.
  - To grant usergroup specific permissions, type n.
- Do you want to provide any usergroups that you would like to grant read access?[y,n,q,?]
  - To specify usergroups and grant them read access, type y
  - To grant read access only to root users, type n. The installer grants read access read access to the root users.
- Enter the usergroup names separated by spaces that you would like to grant read access. If you would like to grant read access to a usergroup on a specific node, enter like 'usrgrp1@node1', and if you would like to grant read access to usergroup on any cluster node, enter like 'usrgrp1'. If some usergroups are not created yet, create the usergroups after configuration if needed. [b]
The installer stops Cluster Server (VCS) processes but the applications continue to run. Type y to continue.
The installer performs prestop, uninstalls old packages, and installs the new packages. It performs post-installation tasks, and the configuration for the upgrade.
If you have network connection to the Internet, the installer checks for updates.
If updates are discovered, you can apply them now.
A prompt message appears to ask if the user wants to read the summary file. You can choose y if you want to read the install summary file.