About rolling upgrade

Last published : Sep 28, 2026
The rolling upgrade process minimizes the downtime of a cluster during an upgrade to the amount of time that it takes to fail over a service group. It has two main phases where the installer upgrades kernel packages in phase 1 and VCS agent related packages in phase 2.
Note: You need to perform a rolling upgrade on a completely configured cluster.
The following is an overview of the flow for a rolling upgrade:
1. The installer performs prechecks on the cluster.
2. Application downtime occurs during the first phase as the installer moves service groups to free nodes for the upgrade. The only downtime that is incurred is the normal time required for the service group to failover. The downtime is limited to the applications that are failed over and not the entire cluster.
3. The installer performs the second phase of the upgrade on all of the nodes in the cluster. The second phase of the upgrade includes downtime of the Cluster Server (VCS) engine HAD, but does not include application downtime.
The following graphic illustrates an example of the installer performing a rolling upgrade for three service groups on a two node cluster.
Figure: Example of the installer performing a rolling upgrade
prod_sfhaExample of the installer performing a rolling upgrade
The following limitations apply to rolling upgrades:
  • Rolling upgrades are not compatible with phased upgrades. Do not mix rolling upgrades and phased upgrades.
  • You can perform a rolling upgrade from 7.4.1 or later versions.
  • The rolling upgrade procedures support only minor operating system upgrades.
  • The rolling upgrade procedure requires the product to be started before and after upgrade. If the current release does not support your current operating system version and the installed old release version does not support the operating system version that the current release supports, then rolling upgrade is not supported.