Performing a rolling upgrade using the script-based installer

Before you start the rolling upgrade, make sure that Veritas Cluster Server (VCS) is running.

Note:

Before performing a rolling upgrade from version 5.1SP1RP3 to version 6.0, install patch VRTSvxfen-5.1SP1RP3P2. For downloading the patch, search VRTSvxfen-5.1SP1RP3P2 in Patch Lookup on the SORT website.

To perform a rolling upgrade

  1. Complete the preparatory steps on the first sub-cluster.
  2. Complete updates to the operating system, if required. For instructions, see the operating system documentation.

    The nodes are restarted after the operating system update.

    If you are performing a major OS upgrade (such as Solaris 9 to Solaris 10), do the following:

    • Mount the software disc for the previous version of SFCFSHA.

    • From the top level disc directory, start the installer.

    • Uninstall the SFCFSHA packages.

    • To finish the uninstallation, start the installer again, and install the packages for the previous version of SFCFSHA on the upgraded OS.

      When the installation completes, the CPI prompts you to reboot the nodes again.

    Restart the nodes again manually. Failing to perform this additional reboot prevents the upgrade from proceeding further.

    # shutdown -g0 -y -i6
  3. Log in as superuser and mount the SFCFSHA Veritas Storage Foundation Cluster File System High Availability 6.0 installation media.
  4. Complete the preparatory steps again for the first sub-cluster.
  5. From root, start the installer.
    # ./installer
  6. From the menu select G) Upgrade a product; then select 2)Rolling Upgrade;.
  7. The installer checks system communications, release compatibility, version information, and lists the cluster name, ID, and cluster nodes. Type y to continue.
  8. The installer inventories the running service groups and determines the node or nodes to upgrade in phase 1 of the rolling upgrade. Type y to continue. If you choose to specify the nodes, type n and enter the names of the nodes.
  9. The installer performs further prechecks on the nodes in the cluster and may present warnings. You can type y to continue or quit the installer and address the precheck's warnings.
  10. Review the EULA, and type y if you agree to its terms.
  11. The installer prompts you to stop the applicable processes. Type y to continue.

    The installer fails over failover service groups to the node or nodes that are not upgraded at this time. The downtime is the time that it normally takes for the service group's failover. The installer stops parallel service groups on the nodes that are to be upgraded.

  12. The installer stops relevant processes, uninstalls old kernel packages, and installs the new packages.

    It performs the configuration for the upgrade and re-starts processes.

    In case of failure in the startup of some of the processes, you may need to reboot the nodes and manually check the cluster's status.

  13. Complete the preparatory steps on the nodes that you have not yet upgraded.
  14. Complete updates to the operating system, if required, on the nodes that you have not yet upgraded. For instructions, see the operating system documentation.

    The nodes are restarted after the operating system update.

    If you are performing a major OS upgrade (such as Solaris 9 to Solaris 10), do the following:

    • Mount the software disc for the previous version of SFCFSHA.

    • From the top level disc directory, start the installer.

    • Uninstall the SFCFSHA packages.

    • To finish the uninstallation, start the installer again, and install the packages for the previous version of SFCFSHA on the upgraded OS.

      When the installation completes, the CPI prompts you to reboot the nodes again.

    Restart the nodes again manually. Failing to perform this additional reboot prevents the upgrade from proceeding further.

    # shutdown -g0 -y -i6
  15. The installer begins phase 1 of the upgrade on the remaining node or nodes. Type y to continue the rolling upgrade.

    If the installer reboots nodes, restart the installer.

    The installer repeats step 8 through step 12.

    For clusters with larger number of nodes, this process may repeat several times. Service groups come down and are brought up to accommodate the upgrade.

  16. When phase 1 of the rolling upgrade completes, begin phase 2 of the upgrade. Phase 2 of the upgrade includes downtime for the VCS engine (HAD), which does not include application downtime. Type y to continue.

    If the boot disk is encapsulated, you need to reboot nodes when phase 1 completes.

  17. The installer determines the remaining packages to upgrade. Press Enter to continue.
  18. The installer stops Veritas Cluster Server (VCS) processes. Type y to continue.

    The installer performs prechecks, uninstalls old packages, and installs the new packages. It performs post-installation tasks, and the configuration for the upgrade.

  19. Type y or n to help Symantec improve the automated installation.
  20. If you have network connection to the Internet, the installer checks for updates.

    If updates are discovered, you can apply them now.

  21. Upgrade application.
  22. To upgrade VCS or Storage Foundation High Availability (SFHA) on the Coordination Point (CP) server systems to version 6.0, upgrade all the application clusters to 6.0. You then upgrade VCS or SFHA on the CP server systems.

    For instructions to upgrade VCS or SFHA on the CP server systems, refer to the appropriate installation guide.