You can use the product installer to upgrade VCS online. The supported upgrade paths are same as those for the installer.
To upgrade VCS online using the product installer
# ./installer
The installer starts the product installation program with a copyright message. It then specifies where it creates the logs.
Note the directory name and path where the logs get stored.
Even if you specify a single node from the cluster, the installer asks whether you want to perform online upgrade of VCS on the entire cluster, keeping your applications online. After you enter the system name, the installer performs some verification checks and asks the following question:
Online upgrade supports application zero downtime. Would you like to perform online upgrade on the whole cluster? [y,n,q](y)
Note: |
You can either exit the installer with the option q or cancel the upgrade using n and select any other cluster to upgrade in this step. |
The installer runs some verification checks on the nodes and subsequently asks if you agree with the terms of the End User License Agreement.
Do you want to grant read access to everyone? [y,n,q,?]
Do you want to provide any usergroups that you would like to grant read access?[y,n,q,?]
Enter the usergroup names separated by spaces that you want to grant read access. If you want to grant read access to a usergroup on a specific node, enter like 'usrgrp1@node1', and if you want 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]
It stops the VCS processes, uninstalls RPMs, reinstalls or upgrades RPMs, again configures VCS, and starts the processes.