To upgrade your installation from 2014.01 to 2015.03 no migration of your data is needed. The on-disk format of 2015.03 is fully compatible with the 2014.01 release series data format. However, with the 2015.03 release series, FhGFS was renamed to BeeGFS. Therefore, the names of the server binaries and tools, config options and paths have changed (e.g. /etc/fhgfs changed to /etc/beegfs and /opt/fhgfs changed to /opt/beegfs). This page will give an overview on how to upgrade to the 2015.03 release, while keeping your old configuration.
If you used mirroring with the 2014.01 release series (which was marked as experimental feature), please note that the mirroring mechanism has changed. Files that were mirrored using the 2014.01 release can still be accessed, but changes won't be mirrored. The old directory named "mirror" is no longer accessed after the upgrade and should be deleted to free up disk space. Please refer to "About BeeGFS Mirroring" for information on how mirroring is implemented in the 2015.03 release series.
|Note: The admon database from FhGFS is not migrated to BeeGFS. The configurations from the GUI windows "notification settings" (email notification, run script for down nodes) and "user settings" (password of admin and info user, autologin of info user) are reset to defaults.|
We recommend to convert all configuration files for use with the 2015.03 release first. You can do this by using the config migration script, which is provided here: Download migration script
After downloading, execute this script on all servers and clients. It will perform the following tasks:
- Migrate all configuration files from /etc/fhgfs to /etc/beegfs
- Update the path settings within the config files: connInterfacesFile, connNetFilterFile, logStdFile and databaseFile.
- Update the name of the client module autobuild argument for RDMA support.
- Update all fhgfs-* service startup configuration files in /etc/default.
|Note: The configuration options storeMgmtdDirectory, storeMetaDirectory and storeStorageDirectory are not changed, even if the path configured contains "fhgfs". This means you don't have to move your data.|
|Note: Make sure you run the config migration script on all servers and clients.|
$ wget http://www.beegfs.com/release/beegfs_2015.03/upgrade/beegfs-migrate-fhgfs-config.py $ chmod +x beegfs-migrate-fhgfs-config.py $ ./beegfs-migrate-fhgfs-config.py # requires root privileges
Now you can uninstall the old FhGFS version packages.
If you haven't done so yet, stop all FhGFS services by using their corresponding init scipt: /etc/init.d/fhgfs-*.
Afterwards uninstall the packages:
- On Red Hat: yum remove 'fhgfs-*'
- On SuSE: zypper remove 'fhgfs-*'
- On Debian: apt-get remove 'fhgfs-*'
Then remove the old FhGFS package repository files:
- On Red Hat: /etc/yum.repos.d/fhgfs-*.repo
- On SuSE: /etc/zypp/repos.d/fhgfs-*.repo
- On Debian: /etc/apt/sources.list.d/fhgfs*.list
After uninstalling the old FhGFS version packages, install the corresponding BeeGFS 2015.03 repositories and packages as described in "Download and Installation of Packages". Afterwards, start the BeeGFS services by using their init scripts: /etc/init.d/beegfs-*.
Back to table of contents