Veritas Access Installation Guide

To perform a rolling upgrade

1. Phase 1 of a rolling upgrade begins on the second subcluster. Complete the preparatory steps on the second subcluster.

   Unmount all VxFS file systems not under VCS control:

   # umount mount_point

2. Complete updates to the operating system, if required.

   Make sure that the existing version of Veritas Access supports the operating system update you apply. If the existing version of Veritas Access does not support the operating system update, first upgrade Veritas Access to a version that supports the operating system update.

   For instructions, see the Red Hat Enterprise Linux (RHEL) operating system documentation.

   Switch applications to the remaining subcluster and upgrade the operating system of the fist subcluster.

   The nodes are restarted after the operating system update.

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

   # sfcache offline cachename

4. Log on as superuser and mount the Veritas Access 7.3.1 installation media.
5. From root, start the installer.

   # ./installaccess -rolling_upgrade

6. The installer checks system communications, release compatibility, version information, and lists the cluster name, ID, and cluster nodes. The installer asks for permission to proceed with the rolling upgrade.

   Would you like to perform rolling upgrade on the cluster? [y,n,q] (y)

   Type y to continue.

7. Phase 1 of the rolling upgrade begins. The installer suggests system names for the upgrade. Press y to upgrade the suggested systems, or enter the name of any one system in the cluster on which you want to perform a rolling upgrade.
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. If the boot disk is encapsulated and mirrored, you can create a backup boot disk.

    If you choose to create a backup boot disk, type y. Provide a backup name for the boot disk group or accept the default name. The installer then creates a backup copy of the boot disk group.

11. After the installer detects the online service groups, the installer prompts the user to do one of the following:

    • Manually switch service groups

    • Use the CPI to automatically switch service groups

    The downtime is the time that it takes for the failover of the service group.

    Note:

    Veritas recommends that you manually switch the service groups. Automatic switching of service groups does not resolve dependency issues.

12. The installer prompts you to stop the applicable processes. Type y to continue.

    The installer evacuates all service groups to the node or nodes that are not upgraded at this time. The installer stops parallel service groups on the nodes that are to be upgraded.

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

13. The installer performs the upgrade configuration and starts the processes. If the boot disk is encapsulated before the upgrade, the installer prompts you to restart the node after performing the upgrade configuration.
14. Complete the preparatory steps on the nodes that you have not yet upgraded.

    Unmount all the VxFS file systems not under VCS control on all the nodes.

    # umount mount_point

15. If operating system updates are not required, skip this step.

    Go to step 3.

    Else, complete updates to the operating system on the nodes that you have not yet upgraded. For instructions, see the Red Hat Enterprise Linux (RHEL) operating system documentation.

    Repeat steps 3 to 13 for each node.

    Phase 1 of the rolling upgrade is complete on the first subcluster. Phase 1 of the rolling upgrade begins on the second subcluster.

16. Offline all cache areas on the remaining node or nodes:

    # sfcache offline cachename

17. The installer begins phase 1 of the upgrade on the remaining node or nodes. Type y to continue the rolling upgrade. If the installer was invoked on the upgraded (restarted) nodes, you must invoke the installer again.

    The installer repeats step 8 through step 13.

    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.

18. When phase 1 of the rolling upgrade completes, mount all the VxFS file systems that are not under VCS control manually. 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. Phase 2 of the rolling upgrade begins here.
19. The installer determines the remaining RPMs to upgrade. Press y to continue.
20. The installer stops Cluster Server (VCS) processes but the applications continue to run. Type y to continue.

    The installer performs a prestop, uninstalls the old RPMs, and installs the new RPMs. It performs post-installation tasks, and the configuration for the upgrade.

21. If you have a network connection to the Internet, the installer checks for updates.

    If updates are discovered, you can apply them now.

22. Verify the cluster's status:

    # hastatus -sum