BeeGFS Upgrade Notes: Version 2014.01 to 2015.03 ================================================ This document contains the relevant changes for users who are upgrading from the 2014.01 release series to the 2015.03 release series. * Rebranding: All packages, tools, config files etc. have been renamed from "fhgfs-*" to "beegfs-*". * New feature - High Availability for Storage Targets: The most notable new feature in the 2015.03 release series is support for a new mirroring approach with transparent failover and self-healing on the beegfs-storage servers. See here for more details: http://www.beegfs.com/wiki/AboutMirroring * Note on old raid10-style mirror format: The old raid10-style mirror format was always marked as "experimental" and did not support transparent server failure in previous releases. This mirror format is obsolete now. Files in raid10 mirror format can still be read and written, but the mirror chunk copies are no longer updated. Thus, the corresponding subdirectory named "mirror" of each storage target is no longer used and can be deleted by the administrator to free up disk space. The new buddy mirroring uses a subdirectory with a new name ("buddymir") on the storage targets to avoid conflicts. * A complete list of new features, improvements and general changes is available in the changelog here: http://www.beegfs.com/release/beegfs_2015.03/Changelog.txt * For upgrade instructions to preserve existing data and config files, see here: http://www.beegfs.com/wiki/Upgrade2014To2015 * On-Disk Format: The BeeGFS 2015.03 release servers are backwards compatible with the 2014.01 and 2012.10 release series storage format, so no data conversion or upgrade tool is required to use existing data with the new release. * Version Interoperability: Clients and servers of 2014.01 and 2015.03 releases are not interoperable and thus cannot be used together in the same file system instance. However, BeeGFS 2015.03 packages and (FhGFS) 2014.01 release series packages can be installed side-by-side, so it is possible to e.g. install a 2014.01 client and a 2015.03 client together on the same machine to access different file system instances. * Admon Database: 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.