Skip to content

Cluster upgrade options

This section looks at the options for upgrading a cluster deployment.


When upgrading a cluster, the upgrade method used will differ depending on the version you are on and upgrading to.

PAM Server versioning is based upon an A.B.C structure, where A is the major release version, B is the feature release version and C is the patch release version.

When an upgrade is started Osirium PAM will determine which upgrade method is used.

PAM release versioning

Full cluster upgrade

The full cluster upgrade method is used when you are upgrading to a new major release or feature release, signified by the first and second numbers of the release version.

As major and feature releases require updates to the underlying database to be applied, a full cluster upgrade requires all nodes within the cluster to be upgraded at the same time.

For instructions on how to perform a Full cluster upgrade click here.

Patch release upgrade

From PAM Server v7.5.3 onwards the patch release upgrade method is used when upgrading to a release when only the third number has changed.

With this option each individual node in the PAM Custer can be upgraded from version A.B.x to a A.B.y independently of the other nodes. This means nodes can be upgraded at different times/dates and multiple patch versions can co-exist and function within the cluster. For example, some could be v7.5.2 and others on v7.5.3.

The main benefit of this option is that its is much quicker than a full cluster upgrade, significantly reducing downtime.

This upgrade option is only available when:

  • Only the patch version has changed.
  • All PAM Servers in the cluster are v7.5.2 or above.
  • All PAM Servers in the cluster are on the same major release version and feature release version.

For instructions on how to perform a Patch cluster upgrade click here.