Chapter 8. Updating to Red Hat Gluster Storage 3.1.x
- 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 there are large number of snapshots, ensure to deactivate the snapshots before performing an update. The snapshots can be activated after the update is complete. For more information, see Chapter 4.1 Starting and Stopping the glusterd service in the Red Hat Gluster Storage 3 Administration Guide.
8.1. Updating Red Hat Gluster Storage from 3.0.x to 3.1.x in the Offline Mode
dracutpackages are previously installed, then exclude the
dracutpackages while updating to Red Hat Gluster Storage 3.1 during offline ISO update using the following command:
# yum update -x dracut -x dracut-kernel
- Offline upgrade results in a downtime as the volume is offline during upgrade.
- Make a complete backup using a reliable backup solution. This Solution covers one possible approach: https://access.redhat.com/solutions/1484053.If you use an alternative backup solution:
- Ensure that you have sufficient space available for a complete backup.
- Copy the .glusterfs directory before copying any data files.
- Ensure that no new files are created on Red Hat Gluster Storage file systems during the backup.
- Ensure that all extended attributes, ACLs, owners, groups, and symbolic and hard links are backed up.
- Check that the backup restores correctly before you continue with the migration.
- Delete the existing Logical Volume (LV) and recreate a new thinly provisioned LV. For more information, see https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/thinprovisioned_volumes.html
- Restore backed up content to the newly created thinly provisioned LV.When you are certain that your backup works, execute the following steps to update Red Hat Gluster Storage in the offline mode:
# yum updateThe update process automatically restarts the
glusterdmanagement deamon. The glusterfs server processes,
glusterfsdis not restarted by default since restarting this daemon affects the active read and write operations.After all the nodes in the cluster are updated, the volume must be restarted for the changes to be applied. Red Hat recommends that you restart the system when there are no active read and write operations running on the cluster.To restart the volume, run the following commands:
# gluster volume stop volname # gluster volume start volname
- When all nodes have been upgraded, run the following command to update the
op-versionof the cluster. This helps to prevent any compatibility issues within the cluster.
# gluster volume set all cluster.op-version 30707