Go to main content

Updating Your Oracle® Solaris Cluster 4.4 Environment

Exit Print View

Updated: March 2019

Performing a Standard Update of a Cluster

A standard update updates a cluster to a new release, including installed data service software, and updates the Oracle Solaris OS to the latest compatible version. You do not need to place the cluster in noncluster mode before performing this update because the update always occurs in the new boot environment (BE) and the existing BE remains unchanged. Normal cluster operations and services can continue while you are updating 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 update all of your software to the latest available version, you can prevent certain components from being updated. 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 Updating Systems and Adding Software in Oracle Solaris 11.4 or the pkg(1) man page.

Any time you update the Oracle Solaris Cluster software in the global cluster, by default you also update the data services and the Disaster Recovery Framework, formerly called Geographic Edition, in the global cluster and in any zone clusters.

Note -  If you want to install any individual Oracle Solaris Cluster SRUs, instead see How to Update a Specific Package or SRU (pkg).

The following table lists the tasks to update to Oracle Solaris Cluster 4.4 software or to a 4.4 SRU. By default, all Oracle Solaris packages are automatically updated.

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