6.2. Upgrading from Red Hat Storage 2.0 to Red Hat Storage 2.1 using yum

⁠6.2. Upgrading from Red Hat Storage 2.0 to Red Hat Storage 2.1 using yum

Pre-Upgrade Steps:

Unmount the clients using the following command:
```
umount mount-point
```
Stop the volumes using the following command:
```
gluster volume stop volname
```
Unmount the data partition(s) on the servers using the following command:
```
umount mount-point
```
To verify if the volume status is stopped, use the following command:
```
# gluster volume info
```
If there is more than one volume, stop all of the volumes.
Stop the glusterd services on all the servers using the following command:
```
# service glusterd stop
```

yum Upgrade Steps:

Important

You can upgrade to Red Hat Storage 2.1 only from Red Hat Storage 2.0 Update 6 release. If your current version is lower than Update 6, then upgrade it to Update 6 before upgrading to Red Hat Storage 2.1.
Upgrade the servers before upgrading the clients.

If the current version is lower than Update 6, first upgrade to Update 6 using the following command:
```
# yum update
```

Change the base channel and the child channels using the following command:

# cd /usr/lib/glusterfs/.unsupported
# python rhs_upgrade.py --username=username  --password=password 
--rhs-version=2.1

Note

If you receive the following error while adding subscriptions, remove the old EUS entitlements before running rhs_upgrade.py.

Error Message:
    Insufficient Software Channel Entitlements:
 
    cfid9170  Red Hat Enterprise Linux Server (v. 6) Extended Update Support

note: One of the above Software Channel Entitlement(s) are required
to provides access to: cid17799 RHEL EUS Server (v. 6.4.z for 64-bit x86_64)
Error Class Code: 70

To remove the old EUS entitlements, log on to http://rhn.redhat.com, locate your system and delete it.

You can also use alternate methods to change the channels as mentioned in Chapter 6, Upgrading Red Hat Storage

To upgrade the server from Red Hat Storage 2.0 to 2.1, use the following command:
```
# yum update
```
The server is now upgraded from Red Hat Enterprise Linux 6.2 to Red Hat Enterprise Linux 6.4
Note
It is recommended to add the child channel of Red Hat Enterprise Linux 6 that contains the native client to refresh the clients and access the new features in Red Hat Storage 2.1. For more information, refer to Installing Native Client in the Red Hat Storage Administration Guide.
Reboot the servers. This is required as the kernel is updated to the latest version.
After the yum update, start the glusterd service on all machines using the following command:
```
# service glusterd start
```
Start the volume on one of the servers, using the following command:
```
# gluster volume start volname force
```
In case you have a pure replica volume (1*n) where n is the replica count and is less than or equal to 3, perform the following additional steps:
1. Run the fix-layout command on the volume using the following command:
```
# gluster volume rebalance volname fix-layout start
```
2. Wait for the fix-layout command to complete. You can check the status for completion using the following command:
```
# gluster volume rebalance volname  status
```
3. Stop the volume using the following command:
```
# gluster volume stop volname
```
4. Force start the volume using the following command:
```
# gluster volume start volname  force
```
If you have a geo-replication setup, then re-establish the geo-replication session between the master and slave using the following steps:
1. Run the following commands on any one of the master nodes:
```
# cd /usr/share/glusterfs/scripts/ 
# sh generate-gfid-file.sh localhost:${master-vol} $PWD/get-gfid.sh /tmp/tmp.atyEmKyCjo/upgrade-gfid-values.txt 
# scp /tmp/tmp.atyEmKyCjo/upgrade-gfid-values.txt root@${slavehost}:/tmp/
```
2. Run the following commands on a slave node:
```
# cd /usr/share/glusterfs/scripts/ 
# sh slave-upgrade.sh localhost:${slave-vol} /tmp/tmp.atyEmKyCjo/upgrade-gfid-values.txt $PWD/gsync-sync-gfid
```
  Note
  If the SSH connection for your setup requires a password, you will be prompted for a password for all machines where the bricks are residing.
3. Re-create and start the geo-replication sessions.
  For information on creating and starting geo-replication session, refer to Managing Geo-replication in the Red Hat Storage Administration Guide
  Note
  It is recommended to add the child channel of Red Hat Enterprise Linux 6 that contains the native client so that you can refresh the clients and get access to all the new features in Red Hat Storage 2.1. For more information refer, Upgrading Native Client in the Red Hat Storage Administration Guide.
  .