The rolling upgrade feature allows you to upgrade the version of VxVM running in a cluster without shutting down the entire cluster. To install the new version of VxVM running on a cluster, make one node leave the cluster, upgrade it, and then join it back into the cluster. This operation is repeated for each node in the cluster.

Each Veritas Volume Manager release starting with Release 3.1 has a cluster protocol version number associated with it. The cluster protocol version is not the same as the release number or the disk group version number. The cluster protocol version is stored in the /etc/vx/volboot file. During a new installation of VxVM, the vxdctl init command creates the volboot file and sets the cluster protocol version to the highest supported version.

Each new Veritas Volume Manager release supports a minimum and maximum cluster protocol version. Each protocol version supports a fixed set of features and communication protocols. When a new release of VxVM adds new features or communication protocols, a new version number is assigned. If the new release of VxVM does not include new features or communication protocols, but only includes bug fixes or minor changes, the cluster protocol version remains unchanged. The maximum version number corresponds to the latest release of VxVM. The cluster protocol version generally does not need to be upgraded manually.

This version of Veritas Volume Manager (VxVM) does not support the rolling upgrade feature.