Performing a Standard Upgrade of a Cluster

The following table lists the tasks to upgrade from Oracle Solaris Cluster 4.0 to a 4.0 SRU. Performing these tasks also upgrades the Oracle Solaris OS to the latest compatible version.

Table 3-1 Task Map: Performing a Standard Upgrade for Oracle Solaris Cluster 4.0 Software

How to Upgrade Quorum Server Software

If the cluster uses a quorum server, upgrade the Quorum Server software on the quorum server before you upgrade the cluster.

Perform all steps as superuser on the cluster and on the quorum server.

1. If the cluster has two nodes and the quorum server is the cluster's only quorum device, temporarily add a second quorum device.

   See Adding a Quorum Device in Oracle Solaris Cluster System Administration Guide.

   If you add another quorum server as a temporary quorum device, the quorum server can run the same software version as the quorum server that you are upgrading, or it can run the 4.0 version of Quorum Server software.

2. Unconfigure the quorum server from each cluster that uses the quorum server.

   phys-schost# clquorum remove quorumserver

3. From the quorum server to upgrade, verify that the quorum server no longer serves any cluster.

   quorumserver# clquorumserver show +

   If the output shows any cluster is still served by the quorum server, unconfigure the quorum server from that cluster. Then repeat this step to confirm that the quorum server is no longer configured with any cluster.

   ---

   Note - If you have unconfigured the quorum server from a cluster but the clquorumserver show command still reports that the quorum server is serving that cluster, the command might be reporting stale configuration information. See Cleaning Up Stale Quorum Server Cluster Information in Oracle Solaris Cluster System Administration Guide.

   ---

4. From the quorum server to upgrade, halt all quorum server instances.

   quorumserver# clquorumserver stop +

5. Uninstall the Quorum Server software from the quorum server to upgrade.

   quorumserver# pkg uninstall ha-cluster/*

6. (Optional) Clean up or remove the quorum server directories.

   By default, this directory is file is /var/scqsd.

7. Install the Oracle Solaris Cluster 4.0 Quorum Server software, reconfigure the quorum server, and start the quorum server daemon.

   Follow the steps in How to Install and Configure Oracle Solaris Cluster Quorum Server Software in Oracle Solaris Cluster Software Installation Guide for installing the Quorum Server software.

8. From a cluster node, configure the upgraded quorum server as a quorum device.

   Follow the steps in How to Configure Quorum Devices in Oracle Solaris Cluster Software Installation Guide.

9. If you configured a temporary quorum device, unconfigure it.

   phys-schost# clquorum remove tempquorum

How to Prepare the Cluster for a Standard Upgrade

Perform this procedure to remove the cluster from production before you perform a standard upgrade. Performing a standard upgrade also upgrades the Oracle Solaris OS to the latest compatible version. Perform all steps from the global zone only.

Before You Begin

Perform the following tasks:

• Ensure that the configuration meets the requirements for upgrade. See Upgrade Requirements and Software Support Guidelines.

• Have available the installation media, documentation, and software updates for all software products that you are upgrading, including the following software:

  • Oracle Solaris OS

  • Oracle Solaris Cluster

  • Applications that are managed by Oracle Solaris Cluster data services

  • Any other third-party applications to upgrade

  For instructions on updating single or multiple packages, see Chapter 11, Updating Your Software, in Oracle Solaris Cluster System Administration Guide.

• If you use role-based access control (RBAC) instead of superuser to access the cluster nodes, ensure that you can assume an RBAC role that provides authorization for all Oracle Solaris Cluster commands. This series of upgrade procedures requires the following Oracle Solaris Cluster RBAC authorizations if the user is not superuser:

  • solaris.cluster.modify

  • solaris.cluster.admin

  • solaris.cluster.read

  See Role-Based Access Control (Overview) in Oracle Solaris Administration: Security Services for more information about using RBAC roles. See the Oracle Solaris Cluster man pages for the RBAC authorization that each Oracle Solaris Cluster subcommand requires.

1. Ensure that the cluster is functioning normally.
   1. View the current status of the cluster by running the following command from any node.

      phys-schost% cluster status

      See the cluster(1CL) man page for more information.

   2. Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.
   3. Check the volume-manager status.
2. Become superuser on a node of the cluster.
3. Take each resource group offline and disable all resources.

   Take offline all resource groups in the cluster, including those that are in non-global zones. Then disable all resources, to prevent the cluster from bringing the resources online automatically if a node is mistakenly rebooted into cluster mode.

   • If you want to use the clsetup utility, perform the following steps:
     1. Start the utility.

        phys-schost# clsetup

        The Main Menu is displayed.

     2. Choose the menu item, Resource Groups.

        The Resource Group Menu is displayed.

     3. Choose the menu item, Online/Offline or Switchover a Resource Group.
     4. Follow the prompts to take offline all resource groups and to put them in the unmanaged state.
     5. When all resource groups are offline, type q to return to the Resource Group Menu.
     6. Exit the clsetup utility.

        Type q to back out of each submenu or press Ctrl-C.

   • To use the command line, perform the following steps:
     1. Take each resource offline.

        phys-schost# clresource offline resource-group

     2. From any node, list all enabled resources in the cluster.

        phys-schost# clresource show -p Enabled
        === Resources ===
        
        Resource:                                       resource
          Enabled{nodename1}:                               True
          Enabled{nodename2}:                               True
        …

     3. Identify those resources that depend on other resources.

        phys-schost# clresource show -p resource_dependencies
        === Resources ===
        
        Resource:                                       node
          Resource_dependencies:                           node
        …

        You must disable dependent resources first before you disable the resources that they depend on.

     4. Disable each enabled resource in the cluster.

        phys-schost# clresource disable resource

        See the clresource(1CL) man page for more information.

     5. Verify that all resources are disabled.

        phys-schost# clresource show -p Enabled
        === Resources ===
        
        Resource:                                       resource
          Enabled{nodename1}:                               False
          Enabled{nodename2}:                               False
        …

     6. Move each resource group to the unmanaged state.

        phys-schost# clresourcegroup unmanage resource-group

4. Verify that all resources on all nodes are Offline and that all resource groups are in the Unmanaged state.

   phys-schost# cluster status -t resource,resourcegroup

5. Stop all applications that are running on each node of the cluster.
6. Ensure that all shared data is backed up.
7. If your cluster uses dual-string mediators for Solaris Volume Manager software, unconfigure your mediators.

   See Configuring Dual-String Mediators in Oracle Solaris Cluster Software Installation Guide for more information about mediators.

   1. Run the following command to verify that no mediator data problems exist.

      phys-schost# medstat -s setname

      -s setname

      Specifies the disk set name.

      If the value in the Status field is Bad, repair the affected mediator host. Follow the procedure How to Check For and Fix Bad Mediator Data in Oracle Solaris Cluster Software Installation Guide.

   2. List all mediators.

      Save this information for when you restore the mediators during the procedure How to Finish the Upgrade.

   3. For a disk set that uses mediators, take ownership of the disk set if no node already has ownership.

      phys-schost# cldevicegroup switch -n node devicegroup

   4. Unconfigure all mediators for the disk set.

      phys-schost# metaset -s setname -d -m mediator-host-list

      -s setname

      Specifies the disk set name.

      -d

      Deletes from the disk set.

      -m mediator-host-list

      Specifies the name of the node to remove as a mediator host for the disk set.

      See the mediator(7D) man page for further information about mediator-specific options to the metaset command.

   5. Repeat Step c through Step d for each remaining disk set that uses mediators.
8. Ensure that each system disk is backed up.

Next Steps

Upgrade the cluster and OS software. Go to How to Perform a Standard Upgrade.

How to Perform a Standard Upgrade

A standard upgrade upgrades a cluster to a new release, including installed data service software, and upgrades the Oracles Solaris OS to the latest compatible version. You do not need to place the cluster in noncluster mode before performing this upgrade because the upgrade always occurs in the new boot environment and the existing boot environment remains unchanged. You can specify a name for the new boot environment or you can use the auto-generated name.

Depending on the content in the repositories, you might have to unset the undesired publishers or freeze the undesired incorporations if you do not want to upgrade the cluster software and the OS all at once. For instructions, see Chapter 5, Configuring Installed Images, in Adding and Updating Oracle Solaris 11 Software Packages or the pkg(1) man page.

Anytime you upgrade the Oracle Solaris Cluster software, you should also upgrade the data services and Geographic Edition software.

1. Become superuser or assume a role that provides solaris.cluster.admin RBAC authorization.
2. Subscribe to the ha-cluster publisher which you want to upgrade.

   # pkg unset-publisher ha-cluster
   # pkg set-publisher -g FMRI for cluster ha-cluster

3. Run the upgrade.

   # scinstall - u update [-b bename] 

   You can choose to specify a name for the new boot environment with the -b bename option.

   If you are upgrading a failover zone, follow the instructions in How to Upgrade Failover Zones.

4. Follow the prompts to boot the machine into the new boot environment.

Next Steps

Go to Chapter 5, Completing the Upgrade.