Updating, Upgrading and Versioning

Versioning Scheme

BeeGFS uses a versioning scheme based on major version and minor version (e.g. 6.0). Both are incrementally updated with the minor version number defining maintenance updates within a major release series. Maintenance updates typically contain improvements, but can also contain new features.

Note that release 6.0 was the first release of BeeGFS using the versioning scheme described above. Before that, BeeGFS used a date-based versioning scheme (YYYY.MM) to define major release series and an incremental versioning scheme (r1, r2, r3, …) to define maintenance updates within a major release series.

Updating within the same major release series

BeeGFS v7

The same minor release must be running on all nodes and it is not possible to mix different minor releases. To upgrade to version 7.2, see here:

BeeGFS v6 and v2015.03

Within the same major release series, all client and server minor releases can be mixed. For example, a BeeGFS system could have the storage and metadata services from version 6.1, and the management and client services from version 6.0 or also different minor releases of the same service type running on different hosts.

To update to the lastest BeeGFS maintenance update within your current major release series, simply use the standard update mechanism of your Linux distribution, e.g. yum update “beegfs*” on RHEL. The update can be performed while the services are running, but to make the new version effective later, you will have to restart the updated service.

Different BeeGFS major releases usually use incompatible network protocols for the new features, so when you upgrade to a new major release, BeeGFS clients and servers need to be updated at the same time. However, different BeeGFS client modules can be loaded on the same hosts if you need to mount different BeeGFS major releases on the same hosts (e.g. while you are transitioning to a new storage system). Upgrading to a new major release involves an explicit switch to a new package repository, so you don’t need to worry that an automatic package update could ever upgrade some services to a new major release unintentional.

Upgrading to a new major release series

See below for upgrade notes and instructions for previous major release versions:

  • To upgrade from version 6.x to version 7.x, see here:
  • To upgrade from version 2015.03 to version 6.x, see here:
  • To upgrade from version 2014.01 to version 2015.03, see here:
  • To upgrade from version 2012.10 to version 2014.01, see here [Plain Text].
  • To upgrade from version 2011.04 to version 2012.10, see here [Plain Text].
  • To upgrade from version 2009.08 to version 2011.04, see here [Plain Text].