• Personal tools
  • Log in / create account
• Navigation
  • Documentation Home
  • Gluster 3.1.x Documentation
  • GlusterFS Concepts
  • Recent changes
• Toolbox
  • What links here
  • Related changes
  • Upload file
  • Special pages

Gluster 3.0 to 3.2 Upgrade Guide

From GlusterDocumentation

This document describes how to upgrade your environment from Gluster v3.0 to Gluster v3.2. Gluster recommends that you back up your data before upgrading to Gluster v3.2.

Recreating your volumes using the procedure described in this document enables you to take advantage of new capabilities like elastic volume management, Geo-replication, directory quota and other features available in Gluster v3.2.

Note: Gluster recommends you to upgrade servers before upgrading clients.

To upgrade from Gluster v3.0 to Gluster v3.2

1. Uninstall the currently installed version of Gluster using the following command:
   
   # rpm -e glusterfs-common glusterfs-server glusterfs-client
   
   Use the equivalent command for Debian-based distributions.
   
   
2. Install GlusterFS v3.2.
   
   For detailed instructions, see Gluster 3.2 Filesystem Installation and Configuration Guide.
   
   
3. Examine the volume file to determine the current volume configuration.
   
   You can do this by displaying the first few lines of the volume file and searching for the glusterfs-volgen entry.
   
   For example, enter the following line to display the current volume file:
   
   # head VOLNAME.vol
   
   The command displays output similar to the following
   
   # ....
   # ....
   # 'cmd line: glusterfs-volgen -n VOLNAME -r 1 node1:/data/export1 node2:/data/export1 node3:/data/export1 node4:/data/export1'
   # ....
   ....
   
   In this example, the volume is configured as a distributed replicated with export paths defined as /data/export1 on servers node1, node2, node3, and node4.
   
   
4. Create Gluster v3.2 volumes corresponding to volumes in your current Gluster v3.0 environment.
   
   See Configuring GlusterFS Volumes for detailed instructions.
   
   
5. Make sure to mount the volume from only one client (not nfs mount) and also all the bricks are up and running. Then traverse the whole volume using the following command:
   #find /mount/glusterfs >/dev/null
   
   Note: This step ensures that the data from 3.0.x versions will become compatible with 3.1.x or 3.2.x versions.
   
   
6. Mount the other clients using either NFS or the Gluster Native Client.
   
   For more information, see Gluster 3.2 Exploring Gluster Clients.
   
   

Congratulations! You have successfully upgraded from Gluster v3.0 to Gluster v3.2.

Note : To upgrade from Gluster v3.1.x to Gluster v3.2, see here