Storage Foundation and High Availability 7.4.2 Configuration and Upgrade Guide - Linux

To upgrade Storage Foundation and High Availability

1. Log in as superuser.
2. Take all service groups offline.

   List all service groups:

   # /opt/VRTSvcs/bin/hagrp -list

   For each service group listed, take it offline:

   # /opt/VRTSvcs/bin/hagrp -offline service_group \
       -sys system_name

3. Enter the following commands on each node to freeze HA service group operations:

   # haconf -makerw 
   # hasys -freeze -persistent nodename 
   # haconf -dump -makero

4. Use the following command to check if any VxFS file systems or Storage Checkpoints are mounted:

   # df -h | grep vxfs

5. Unmount all Storage Checkpoints and file systems:

   # umount /checkpoint_name
   # umount /filesystem

6. Verify that all file systems have been cleanly unmounted:

   # echo "8192B.p S" | fsdb -t vxfs filesystem | grep clean
   flags 0 mod 0 clean clean_value

   A clean_value value of 0x5a indicates the file system is clean, 0x3c indicates the file system is dirty, and 0x69 indicates the file system is dusty. A dusty file system has pending extended operations.

   Perform the following steps in the order listed:

   • If a file system is not clean, enter the following commands for that file system:

     # fsck -t vxfs filesystem
     # mount -t vxfs filesystem mountpoint
     # umount mountpoint

     This should complete any extended operations that were outstanding on the file system and unmount the file system cleanly.

     There may be a pending large RPM clone removal extended operation if the umount command fails with the following error:

           file system device busy

     You know for certain that an extended operation is pending if the following message is generated on the console:

           Storage Checkpoint asynchronous operation on file_system
           file system still in progress.

   • If an extended operation is pending, you must leave the file system mounted for a longer time to allow the operation to complete. Removing a very large RPM clone can take several hours.

   • Repeat this step to verify that the unclean file system is now clean.

7. If a cache area is online, you must take the cache area offline before you upgrade the VxVM RPM. Use the following command to take the cache area offline:

   # sfcache offline cachename

8. Stop activity to all VxVM volumes. For example, stop any applications such as databases that access the volumes, and unmount any file systems that have been created on the volumes.
9. Stop all the volumes by entering the following command for each disk group:

   # vxvol -g diskgroup stopall

   To verify that no volumes remain open, use the following command:

   # vxprint -Aht -e v_open

10. Make a record of the mount points for VxFS file systems and VxVM volumes that are defined in the /etc/fstab file. You will need to recreate these entries in the /etc/fstab file on the freshly installed system.
11. Perform any necessary preinstallation checks.
12. Check if you need to make updates to the operating system. If you need to update the operating system, perform the following tasks:

    • Rename the /etc/llttab file to prevent LLT from starting automatically when the node starts:

      # mv /etc/llttab /etc/llttab.save

    • Upgrade the operating system.

      Refer to the operating system's documentation for more information.

    • After you have upgraded the operating system, restart the nodes:

      # shutdown -r now

    • Rename the /etc/llttab file to its original name:

      # mv /etc/llttab.save /etc/llttab

13. To invoke the common installer, run the installer command on the disc as shown in this example:

    # cd /cdrom/cdrom0
    # ./installer

14. Enter G to upgrade and press Return.
15. You are prompted to enter the system names (in the following example, "host1") on which the software is to be installed. Enter the system name or names and then press Return.

    Enter the 64 bit  <platform> system names separated 
    by spaces : [q, ?] host1 host2

    where <platform> is the platform on which the system runs.

    Depending on your existing configuration, various messages and prompts may appear. Answer the prompts appropriately.

    During the system verification phase, the installer checks if the boot disk is encapsulated and the upgrade's path. If the upgrade is not supported, you need to un-encapsulate the boot disk.

16. The installer asks if you agree with the terms of the End User License Agreement. Press y to agree and continue.
17. The installer discovers if any of the systems that you are upgrading have mirrored encapsulated boot disks. You now have the option to create a backup of the systems' root disks before the upgrade proceeds. If you want to split the mirrors on the encapsulated boot disks to create the backup, answer y.
18. The installer then prompts you to name the backup root disk. Enter the name for the backup and mirrored boot disk or press Enter to accept the default.

    Note:

    The split operation can take some time to complete.

19. You are prompted to start the split operation. Press y to continue.
20. Reboot the system if the boot disk is encapsulated before the upgrade.
21. If you need to re-encapsulate and mirror the root disk on each of the nodes, follow the procedures in the "Administering Disks" chapter of the Storage Foundation Administrator's Guide.

    If you have split the mirrored root disk to back it up, then after a successful reboot, verify the upgrade and re-join the backup disk group. If the upgrade fails, revert to the backup disk group.

22. If necessary, reinstate any missing mount points in the /etc/fstab file on each node that you recorded in step 10.
23. If any VCS configuration files need to be restored, stop the cluster, restore the files to the /etc/VRTSvcs/conf/config directory, and restart the cluster.
24. Make the VCS configuration writable again from any node in the upgraded group:

    # haconf -makerw

25. Enter the following command on each node in the upgraded group to unfreeze HA service group operations:

    # hasys -unfreeze -persistent nodename

26. Make the configuration read-only:

    # haconf -dump -makero

27. Bring all of the VCS service groups, such as failover groups, online on the required node using the below command:

    # hagrp -online groupname -sys nodename

28. Restart all the volumes by entering the following command for each disk group:

    # vxvol -g diskgroup startall

29. Remount all VxFS file systems and Storage Checkpoints on all nodes:

    # mount /filesystem
    # mount /checkpoint_name

30. You can perform the following optional configuration steps:

    • If you want to use features of Storage Foundation 7.4.2 for which you do not currently have an appropriate license installed, obtain the license and run the vxlicinst command to add it to your system.

    • To upgrade VxFS Disk Layout versions and VxVM Disk Group versions, follow the upgrade instructions.