Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Geographic Edition Installation Guide Oracle Solaris Cluster 3.3 3/13 |
1. Planning the Geographic Edition Installation
2. Installing Geographic Edition Software
3. Enabling and Configuring the Geographic Edition Software
4. Upgrading the Geographic Edition Software
Upgrading a Geographic Edition Configuration
Upgrade Requirements and Software Support Guidelines
How to Prepare the Cluster for an Upgrade
This section provides the following information to upgrade a Geographic Edition configuration:
Observe the following requirements and software-support guidelines on all clusters that have a partnership with the cluster that you are upgrading when you upgrade a cluster to the Geographic Edition 3.3 1/13 software:
Supported hardware - The cluster hardware must be a supported configuration for Geographic Edition 3.3 1/13 software. Contact your Oracle representative for information about Geographic Edition configurations that are currently supported.
Minimum Oracle Solaris OS version - The cluster must run on or be upgraded to at least Solaris 10 8/11 software, including the most current required patches.
Minimum Oracle Solaris Cluster version - The cluster must run on or be upgraded to either Oracle Solaris Cluster 3.3 8/11 or Oracle Solaris Cluster 3.3 1/13 software.
Note - All clusters in a partnership must run either Oracle Solaris Cluster 3.3 8/11 or Oracle Solaris Cluster 3.3 1/13 software. If a cluster is already running on Oracle Solaris Cluster 3.3 8/11 software, you are not required to upgrade it to Oracle Solaris Cluster 3.3 1/13 software to upgrade that cluster to Geographic Edition 3.3 8/11 software.
Cluster partnerships - You must upgrade Geographic Edition software on all nodes of all clusters that have a partnership with the cluster you are upgrading to either Geographic Edition 3.3 8/11 or 3.3 1/13 software, if any cluster node is not already running one of those versions.
Perform this procedure on all clusters that have a partnership with the cluster you are upgrading to remove the Geographic Edition layer from production. Perform all steps from the global zone only.
Before You Begin
Perform the following tasks:
Ensure that the configuration meets the requirements for the upgrade. See Upgrade Requirements and Software Support Guidelines.
Have available the installation media, documentation, and patches for all software products that you are upgrading, including Oracle Solaris OS, Oracle Solaris Cluster software, and Geographic Edition 3.3 1/13 software.
Ensure that you have installed all the required patches for your cluster configuration on each node of every cluster before you start upgrading the software. See Patches and Required Firmware Levels in Oracle Solaris Cluster 3.3 3/13 Release Notes for the location of patches and installation instructions.
Note - If you want to upgrade the Oracle Solaris OS or other applications during the Geographic Edition software upgrade process, you must remove the Geographic Edition packages before you upgrade the Oracle Solaris OS or other applications. For information about uninstalling Geographic Edition software, see Uninstalling Geographic Edition Software to determine the proper method of uninstallation.
% cluster status
See the cluster(1CL) man page for more information.
Highly available applications do not have downtime during the Geographic Edition software upgrade.
# geopg remove-resource-group resourcegroup protectiongroup
See the geopg(1M) man page for more information.
# geopg stop protectiongroup -e local
See the geopg(1M) man page for more information.
# geoadm stop
See the geoadm(1M) man page for more information.
# clresourcegroup set -p Auto_start_on_new_cluster=False resourcegroup
This setting ensures that, when the geoadm stop command is issued, data replication resource groups are not left in the Offline state. It also prevents the Oracle Solaris Cluster resource group manager from automatically starting the replication resource groups.
Next Steps
Upgrade the Geographic Edition software on the clusters. Go to How to Upgrade Geographic Edition Software.
Perform this procedure on all nodes of the cluster. You can perform this procedure on more than one node at the same time.
Caution - If the cluster is in a partnership, both partners must be upgraded to Geographic Edition 3.3 8/11 or 3.3 1/13 software before the Geographic Edition 3.3 1/13 software can start. |
% xhost + % setenv DISPLAY nodename:0.0
If the display environment is not set to display the GUI, the uninstall program instead runs in text-based mode.
If Geographic Edition 3.2 software is installed, follow procedures in Uninstalling Sun Cluster Geographic Edition Software on Solaris OS 9 and 10 in Sun Cluster Geographic Edition Installation Guide.
% cluster status
See the cluster(1CL) man page for more information.
See Oracle Solaris Cluster Software Installation Guide for more information.
Note - All clusters in a partnership must run either Oracle Solaris Cluster 3.3 8/11 or Oracle Solaris Cluster 3.3 1/13 software. If a cluster is already running on Oracle Solaris Cluster 3.3 8/11 software, you are not required to upgrade it to Oracle Solaris Cluster 3.3 1/13 software to upgrade that cluster to Geographic Edition 3.3 1/13 software.
# geoadm start
localnode# geops remove-trust -c remotecluster
remotenode# geops remove-trust -c localcluster
localnode# geops add-trust -c remotecluster
remotenode# geops add-trust -c localcluster
# geops verify-trust -c partnercluster
For a complete example of how to configure and join a partnership, see How to Join a Partnership in Oracle Solaris Cluster Geographic Edition System Administration Guide.
# geopg add-resource-group resourcegroup protectiongroup
See the geopg(1M) man page for more information.
# geopg start protectiongroup -e local [-n]
See the geopg(1M) man page for more information.
Next Steps
Go to How to Verify Upgrade of Geographic Edition Software.
Perform this procedure to verify that the cluster is successfully upgraded to Geographic Edition 3.3 1/13 software. Perform all steps from the global zone only.
Before You Begin
Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.
# geoadm -V
The last line of output states which version of Geographic Edition software the node is running. This version should match the version to which you just upgraded.
Note - The version number that the geoadm -v command returns does not coincide with the marketing release version numbers. The version number for Geographic Edition 3.3 1/13 software is 3.32.
# geoadm status
# geopg switchover remotecluster protectiongroup
You must test your geographically separated cluster properly, so that no problems prevent a switchover. Upgrading the secondary cluster first and switching over to it enables you to verify that switchover still works. If the switchover fails, the primary site is untouched and you can switch back. If switchover works on the secondary site, then after a certain 'soak time' you can upgrade the primary site as well.
Note - A switchover might interrupt the services that are running on the cluster. You should carefully plan the required tasks and resources before you perform a switchover.
If you have added your application resource groups back into the protection groups, performing a switchover shuts down the applications on the original primary cluster and migrates the applications to the secondary cluster.