BeeGFS Upgrade Notes: Version 7.1.4 =================================== This is a patch release, no data migration is involved. No special actions are required when upgrading within BeeGFS v7.1 BeeGFS Upgrade Notes: Version 7.1.3 =================================== This is a patch release, no data migration is involved and no additional settings have been introduced. Therefore, no special actions are required when upgrading within BeeGFS v7.1 BeeGFS Upgrade Notes: Version 7.1.2 =================================== * IMPORTANT: due to a bug related to quota settings, it is necessary to backup quota information while the management server is still running (in case you have configured quota settings). See https://www.beegfs.io/wiki/BackupRestoreQuota for more details. Besides that, there are no special actions required when upgrading within the BeeGFS v7 series. For upgrades from v6, see below. BeeGFS Upgrade Notes: Version 7.1 ================================= * IMPORTANT: due to a bug related to quota settings, it is necssary to backup quota information while the management server is still running (in case you have configured quota settings). See https://www.beegfs.io/wiki/BackupRestoreQuota for more details. * IMPORTANT: Direct upgrade from BeeGFS 2015.X and older to v7.1 is not possible. The beegfs-mgmtd is no longer able to read data from mgmtd versions older than 7.0. In order to upgrade from 2015.X or an older BeeGFS version to 7.1, please upgrade the mgmtd to version 7.0 first. Start the beegfs-mgmtd service, then stop it again. This causes it to upgrade all persistently stored information to the new format. Then you can upgrade all services to version 7.1 and start them. See the following links for an overview. beegfs.io/release/beegfs_7_1/UpgradePath.png * IMPORTANT: It is no longer possible to mix daemons and clients of different minor versions (e.g. version 7.0 and version 7.1). This means all parts of the BeeGFS Installation have to be updated together at the same time. See the following link for an overview: beegfs.io/release/beegfs_7_1/VersionInterop.png * IMPORTANT: Downgrade (even to v7.0) is not possible after upgrade. * Sockets Direct Protocol (SDP) support was removed. If you have been using SPD, consider switching to RDMA. The `connUseSDP` option is no longer recognized in any config file. Remove the corresponding line from existing files. Services will not start with this option present, even though set to false. * Supported kernel versions and distributions All recent kernels used by the following distributions are supported: RHEL/CentOS 6.10, 7.5 Debian 8, 9 SLES 12, 15 Ubuntu 16.04, 18.04 See beegfs.io/release/beegfs_7_1/SupportKernelVersions.txt for more details. * Structure and names of software packages (*.deb, *.rpm) has changed - Debian: The `client-devel` package has been renamed to `client-dev` - New package `libbeegfs-ib`, required for Infiniband Support for server services - `beegfs-opentk-lib` removed * Automatic runtime detection of Infiniband/RDMA The `beegfs-setup-rdma` tool was removed and no user action is required anymore to enable IB for server services. The Infiniband/RDMA support was moved to a separate library shipped in the new `libbeegfs-ib` package. Once the package is installed, the library is loaded and IB is switched on automatically at runtime. All BeeGFS service packages (mgmtd, meta, storage) make use of the `libbeegfs-ib` package, if it is also installed. Therefore, if you are using Infiniband/RDMA, you must also install this package. With Debian, the package manager 'recommends' this during installation. * SUSE Linux 15 You need to install the package 'insserv-compat' prior to BeeGFS package installation. Otherwise, the following error message will appear during installation: Executing: /usr/lib/systemd/systemd-sysv-install enable beegfs-mgmtd /sbin/insserv: No such file or directory BeeGFS Upgrade Notes: from Version 7.0rc-X Release Candidates ============================================================= Upgrading 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.x to 7.1.2 ========================================== This document contains the relevant changes for users who are upgrading from the v6 release series to the v7 release series. * IMPORTANT: to preserve quota information, please make sure that you read the instructions further down below on quota limits. In addition, you may want to create a backup of your quota settings. See https://www.beegfs.io/wiki/BackupRestoreQuota for more details. * 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. * If you have Quota Limits configured: Before upgrading, please make a backup of `quota/quotaUserLimits.store` and `quota/quotaGroupLimits.store` located in the data directory of the management daemon. After the upgrade place them in the `quota/1/` directory. If the directory does not exist, create it. ``` cp $MGMTDIR/quota/quota*Limits.store $BACKUPDIR/ # Upgrade BeeGFS mkdir -p $MGMTDIR/quota/1 cp $BACKUPDIR/quota*Limits.store $MGMTDIR/quota/1/ # restart BeeGFS ``` Background Information: BeeGFS version 7 introduces storage pools. Every target is part of a storage pool, the default pool has the ID 1. When upgrading to v7, all targets are placed in the default pool. By copying the files as described above, the quota limits are applied for the default pool (ID 1). You can apply the same limits additionally to other pools by copying both files to the corresponding `quota/$ID/` directories.