A software update is a minor release that includes bug fixes for features, software enhancements, etc. Red Hat strongly recommends you update your Red Hat Gluster Storage software regularly with the latest security patches and upgrades.
To keep your Red Hat Gluster Storage system up-to-date, associate the system with the Red Hat Network or your locally-managed content service. This ensures your system automatically stays up-to-date with security patches and bug fixes.
Be aware of the following when updating your Red Hat Gluster Storage 3.4 installation:
Asynchronous errata update releases of Red Hat Gluster Storage include all fixes that were released asynchronously since the last release as a cumulative update.
When a Red Hat Gluster Storage server node that hosts a very large number of bricks or snapshots is updated, cluster management commands may become unresponsive as glusterd attempts to start all brick processes concurrently for all bricks and snapshots. If you have more than 250 bricks or snapshots being hosted by a single node, Red Hat recommends deactivating snapshots until the update is complete.
After performing inservice upgrade of NFS-Ganesha, the new configuration file is saved as "
/etc/ganesha folder. The old configuration file is not overwritten during the inservice upgrade process. However, post upgradation, you have to manually copy any new configuration changes from "
ganesha.conf.rpmnew" to the existing
ganesha.conf file in
Regardless of the approach that you use:
Back up to a location that is not on the operating system partition.
Ensure that you have sufficient space available for a complete backup.
.glusterfs directory before copying any data files.
Ensure that the following configuration directories and files are backed up.
If you use NFS-Ganesha, also ensure that the following files from all nodes are backed up:
Ensure that all extended attributes, ACLs, owners, groups, and symbolic and hard links are backed up.
Ensure that no new files are created on Red Hat Gluster Storage file systems during the backup or update process.
Check that the backup restores correctly before you continue with the update: