BeeGFS Upgrade Notes: from Version 7.0rc-X Release Candidates
=============================================================

Uprgading from v7.0 release candidates to v7.0 final are supported.
However, if the installation was upgraded from a previous version (v6 and older)
to a v7.0rc, problems are to be expected.
Please note, direct upgrades from v6 (and older) to v7.0 final are possible without
problems.


BeeGFS Upgrade Notes: Version 6.0 to 7.0
========================================

This document contains the relevant changes for users who are upgrading from the
v6 release series to the v7 release series.

* On-Disk Format:
  The BeeGFS 7.x release servers are backwards compatible with the 6.x release 
  series storage format, so no data conversion or upgrade tool is required to use
  existing data with the new release. 
  However, please note that a downgrade to 6.x will not be possible, because the
  data format will be upgraded automatically on access.

* Version Interoperability:
  Clients and servers of 6.x and 7.x releases are not interoperable and thus cannot
  be used together in the same file system instance.

* init.d scripts are no longer supported on systemd setups:
  To aviod confusions and misconfigutaions, the init scripts are disabled
  on systems supporting systemd. Please use systemd where possible.
  Note that the /etc/default/* files are not considered when using systemd.

* Multimode-Startup:
  The startup mechanism for multi-mode daemon configurations on systems using systemd
  has changed. Systemd service templates are used. This allows to controll each 
  daemon instance individually.

  For example, starting the two instances called 1 and 2 of a meta server can be done
  like this:
      systemctl start beegfs-meta@1 beegfs-meta@2

  See https://www.beegfs.io/wiki/MultiMode for details.

* Drop support of 32bit packages (except on Debian)
  Use 64bit machines if possible or compile from source.