Oracle® Solaris Cluster Upgrade Guide

Exit Print View

Updated: July 2014, E39644–01

Performing a Standard Upgrade of a Cluster

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 (BE) and the existing BE remains unchanged. Normal cluster operations and services can continue while you are upgrading the new BE. You can specify a name for the new BE or you can use the auto-generated name.

If you do not want to upgrade all of your software to the latest available version, you can prevent certain components from being upgraded. You can do this by freezing individual packages or incorporations, or by disabling the appropriate publisher. For instructions, see Chapter 5, Configuring Installed Images, in Adding and Updating Software in Oracle Solaris 11.2 or the pkg (1) man page.

Any time you upgrade the Oracle Solaris Cluster software in the global cluster, by default you also upgrade the data services in the global cluster and in any zone clusters, and upgrade Geographic Edition software in the global cluster. However, you must always manually upgrade Geographic Edition software in a zone cluster. For information about upgrading Geographic Edition software, see Chapter 3, Upgrading or Updating Geographic Edition Software, in Oracle Solaris Cluster Geographic Edition Installation and Configuration Guide .

Note -  If you want to install any individual Oracle Solaris Cluster SRUs, instead see How to Update a Specific Package in Oracle Solaris Cluster System Administration Guide .

The following table lists the tasks to upgrade to Oracle Solaris Cluster 4.2 software or to a 4.2 SRU. By default, all Oracle Solaris packages are automatically upgraded.

Table 3-1  Task Map: Performing a Standard Upgrade for Oracle Solaris Cluster 4.2 Software
1. Read the upgrade requirements and restrictions. Determine the proper upgrade method for your configuration and needs.
2. If failover zones of brand type solaris are configured in the cluster, upgrade the failover zones.
3. If a quorum server is used, upgrade the Quorum Server software.
4. Remove the cluster from production and back up shared data.
5. Upgrade to Oracle Solaris Cluster 4.2 framework, data-service, and Geographic Edition software (global cluster only). If necessary, upgrade applications that support alternate boot environments.
6. Use the scversions command to commit the cluster to the upgrade.
7. Verify successful completion of upgrade to Oracle Solaris Cluster 4.2 software.
8. Enable resources and bring resource groups online. Migrate existing resources to new resource types. If necessary, boot into noncluster mode and upgrade applications that do not support alternate boot environments.