Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Upgrade Guide Oracle Solaris Cluster 3.3 3/13 |
1. Preparing to Upgrade Oracle Solaris Cluster Software
Choosing an Oracle Solaris Cluster Upgrade Method
2. Performing a Standard Upgrade to Oracle Solaris Cluster 3.3 3/13 Software
3. Performing a Dual-Partition Upgrade to Oracle Solaris Cluster 3.3 3/13 Software
4. Performing a Live Upgrade to Oracle Solaris Cluster 3.3 3/13 Software
5. Performing a Rolling Upgrade
Observe the following requirements and software-support guidelines when you upgrade to Oracle Solaris Cluster 3.3 3/13 software:
Minimum Oracle Solaris OS - Oracle Solaris 10 8/11 software is the minimum version required to support Oracle Solaris Cluster 3.3 3/13 software.
Minimum Oracle Solaris Cluster software version - The following are the minimum Oracle Solaris Cluster versions the cluster must run before you upgrade to the 3.3 3/13 release:
If using the rolling upgrade method, the cluster must already run Oracle Solaris Cluster version 3.3 (initial release) or 3.3 5/11. In addition, when using the rolling upgrade method, you can only upgrade Oracle Solaris software to an Oracle Solaris update release, such as from version 10 10/09 to version 10 8/11.
For all other upgrade methods, the cluster must run at least Oracle Solaris Cluster version 3.2 11/09.
See Choosing an Oracle Solaris Cluster Upgrade Method for additional requirements and restrictions for each upgrade method.
Supported hardware - The cluster hardware must be a supported configuration for Oracle Solaris Cluster 3.3 3/13 software. Contact your Oracle representative for information about current supported Oracle Solaris Cluster configurations.
Architecture changes during upgrade - Oracle Solaris Cluster 3.3 3/13 software does not support upgrade between architectures.
Software migration - Do not migrate from one type of software product to another product during Oracle Solaris Cluster upgrade. Perform only software configuration changes that are specified by upgrade procedures of an installed software product.
Global-devices partition size - If a node uses a dedicated partition for the /global/.devices/node@nodeid file system and the partition is less than 512 Mbytes but it provides sufficient space for existing device nodes, you do not need to change the file-system size. The 512 Mbyte minimum applies to new installations of Oracle Solaris Cluster software.
However, you must still ensure that the global-devices file system has ample space and ample inode capacity for existing devices and for any new devices that you intend to configure. Certain configuration changes, such as adding disks, disk volumes, or metadevices, might require increasing the partition size to provide sufficient additional inodes.
Data services - You must upgrade data-service software to the Oracle Solaris Cluster 3.3 3/13 version.
Upgrading to compatible versions - You must upgrade all software on the cluster nodes to a version that is supported by Oracle Solaris Cluster 3.3 3/13 software. For example, if a version of an application is supported on Sun Cluster 3.2 software but is not supported on Oracle Solaris Cluster 3.3 3/13 software, you must upgrade that application to the version that is supported on Oracle Solaris Cluster 3.3 3/13 software, if such a version exists. See Supported Products in Oracle Solaris Cluster 3.3 3/13 Release Notes for information about supported products.
Downgrade - Oracle Solaris Cluster 3.3 3/13 software does not support any downgrade of Oracle Solaris Cluster software.
Limitation of scinstall for data-service upgrades - The scinstall upgrade utility only upgrades those data services that are provided with Oracle Solaris Cluster 3.3 3/13 software. You must manually upgrade any custom or third-party data services.