|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster Upgrade Guide Oracle Solaris Cluster 4.0|
The following matrixes summarize the supported upgrade methods for each Oracle Solaris OS version and platform, provided that all other requirements for any supported method are met. Check the documentation for other products in the cluster, such as volume management software and other applications, for any additional upgrade requirements or restrictions.
Table 1-1 Upgrade an Oracle Solaris Cluster 4.0 Cluster to a New Release
Choose from the following methods to upgrade your Oracle Solaris Cluster 4.0 cluster software:
Standard Upgrade – Upgrade the entire cluster to a new SRU release and upgrade the Oracle Solaris OS to the latest compatible version.
Rolling Upgrade – Upgrade one cluster node at a time to a new SRU release and upgrade the Oracle Solaris OS to the latest compatible version. Cluster nodes not being upgraded remain in production.
For overview information about planning your Oracle Solaris Cluster 4.0 configuration, see Chapter 1, Planning the Oracle Solaris Cluster Configuration, in Oracle Solaris Cluster Software Installation Guide.
A standard upgrade upgrades a cluster to a new release 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.
Any time you upgrade the Oracle Solaris Cluster software, you should also upgrade the data services and Geographic Edition software. However, if you want to upgrade the data services separately, see Overview of the Installation and Configuration Process in Oracle Solaris Cluster Data Services Planning and Administration Guide. If you want to upgrade Oracle Solaris Cluster Geographic Edition separately, see the Oracle Solaris Cluster Geographic Edition Installation Guide.
Note - An SRU can be installed with either the pkg commands or the scinstall -u command. For instructions on using the pkg command to upgrade single or multiple packages, see Updating a Specific Package in Oracle Solaris Cluster System Administration Guide.
For complete instructions on performing a standard upgrade, see Chapter 3, Performing a Standard Upgrade.
The cluster outage is limited to the amount of time that is needed to reboot the cluster nodes into the upgraded boot environment.
In a rolling upgrade, you upgrade software to an update release or a new SRU on one node at a time. Services continue on the other nodes except for the time it takes to switch services from a node to be upgraded to a node that will remain in service.
Observe the following additional restrictions and requirements for the rolling upgrade method:
Minimum Oracle Solaris Cluster version - The cluster must be running an Oracle Solaris Cluster 4.0 release.
Oracle Solaris upgrade paths - You can upgrade the Oracle Solaris OS only to a new SRU or an update version of the same release.
Hardware configuration changes - Do not change the cluster configuration during a rolling upgrade. For example, do not add to or change the cluster interconnect or quorum devices. If you need to make such a change, do so before you start the rolling upgrade procedure or wait until after all nodes are upgraded and the cluster is committed to the new software version.
Duration of the upgrade - Limit the amount of time that you take to complete a rolling upgrade of all cluster nodes. After a node is upgraded, begin the upgrade of the next cluster node as soon as possible. You can experience performance penalties and other penalties when you run a mixed-version cluster for an extended period of time.
Software configuration changes - Avoid installing new data services or issuing any administrative configuration commands during the upgrade.
New-feature availability - Until all nodes of the cluster are successfully upgraded and the upgrade is committed, new features that are introduced by the new release might not be available.