Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Geographic Edition Installation Guide

Search Scope:

- This Document
- Entire Library

## Upgrading a Geographic Edition Configuration

This section provides the following information to upgrade a Geographic Edition configuration:

- Upgrade Requirements and Software Support Guidelines

- How to Prepare the Cluster for an Upgrade

- How to Upgrade Geographic Edition Software

- How to Verify Upgrade of Geographic Edition Software

### Upgrade Requirements and Software Support Guidelines

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 5/11 software:

- Supported hardware - The cluster hardware must be a supported configuration for Geographic Edition 3.3 5/11 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 11/09 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 or Oracle Solaris Cluster 3.3 5/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 or 3.3 5/11 software, if any cluster node is not already running one of those versions.

## How to Prepare the Cluster for an Upgrade

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 5/11 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 Required Patches in Oracle Solaris Cluster Geographic Edition 3.3 5/11 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.

1. Ensure that the cluster is functioning properly.
   1. From any node, view the current status of the cluster.

          % cluster status

      See the `cluster`(1CL) man page for more information.

   2. Search the `/var/adm/messages` log on the same node for unresolved error messages or warning messages.
   3. Check the volume manager status.
2. Become superuser on a node of the cluster.
3. Remove all application resource groups from protection groups.

   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.

4. Perform the preceding steps on all clusters that have a partnership with this cluster.
5. Stop all protection groups that are active on the cluster.

       # geopg stop protectiongroup -e local

   See the `geopg`(1M) man page for more information.

6. Stop the Geographic Edition infrastructure.

       # geoadm stop

   See the `geoadm`(1M) man page for more information.

Next Steps

Upgrade the Geographic Edition software on the clusters. Go to How to Upgrade Geographic Edition Software.

## 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 or 3.3 5/11 software before the Geographic Edition 3.3 5/11 software can start.

1. To use the `uninstall` program with a GUI, ensure that the display environment of the cluster node to uninstall is set to display the GUI.

       % 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.

2. Become superuser on a node where you intend to uninstall Geographic Edition software.
3. Uninstall the current Geographic Edition software.

   Version of Geographic Edition Software | Version of Solaris OS | Method of Uninstallation
   --- | --- | ---
   3.1 8/05 | 8 or 9 | The `uninstall` program that is provided with Geographic Edition 3.1 8/05. For more information, see Chapter 4, Uninstalling the Sun Cluster Geographic Edition Software, in Sun Cluster Geographic Edition Installation Guide.
   10 | The `pkgrm` command. For more information, see Limitations on Running Sun Cluster Geographic Edition Software on Solaris OS 10 in Sun Cluster Geographic Edition 3.1 8/05 Release Notes.
   3.1 2006Q4 | 8 | The `pkgrm` command. For more information, see Uninstalling Sun Cluster Geographic Edition Software on Solaris OS 8 in Sun Cluster Geographic Edition Installation Guide.
   9 or 10 | The `uninstall` program. For more information, see Uninstalling Sun Cluster Geographic Edition Software on Solaris OS 9 and 10 in Sun Cluster Geographic Edition Installation Guide.
   3.2 | 9 or 10 | The `uninstall` program. For more information, see Uninstalling Sun Cluster Geographic Edition Software on Solaris OS 9 and 10 in Sun Cluster Geographic Edition Installation Guide.

4. Ensure that the cluster is functioning properly and that all nodes are online and part of the cluster.
   1. From any node, view the current status of the cluster.

          % cluster status

      See the `cluster`(1CL) man page for more information.

   2. Search the `/var/adm/messages` log on the same node for unresolved error messages or warning messages.
   3. Check the volume manager status.
5. Upgrade to either Oracle Solaris Cluster 3.3 or Oracle Solaris Cluster 3.3 5/11 software.

   See Oracle Solaris Cluster Software Installation Guide for more information.

6. Install Geographic Edition 3.3 5/11 software as described in Chapter 2, Installing Geographic Edition Software.
7. Install all the required patches as described in Installing Patches.
8. Perform the preceding steps on all other nodes of the cluster.

   Note - All clusters in a partnership must run either Oracle Solaris Cluster 3.3 or Oracle Solaris Cluster 3.3 5/11 software. If a cluster is already running on Oracle Solaris Cluster 3.3 software, you are not required to upgrade it to Oracle Solaris Cluster 3.3 5/11 software to upgrade that cluster to Geographic Edition 3.3 5/11 software.

9. On one node of each partner cluster that you upgraded, enable Geographic Edition software.

       # geoadm start

10. Update the public keys on all nodes on both partner clusters.
    1. On each node in the local cluster, remove the public keys.

           localnode# geops remove-trust -c remotecluster

    2. On each node in the remote cluster, remove the public keys.

           remotenode# geops remove-trust -c localcluster

    3. On one node of the local cluster, import the public keys from the remote cluster.

           localnode# geops add-trust -c remotecluster

    4. On one node of the remote cluster, import the public keys from the local cluster.

           remotenode# geops add-trust -c localcluster

    5. On each node of each cluster, verify trust.

           # 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.

11. From one node in one of the partner clusters, add back to the protection group all application resource groups that you removed while you were preparing the cluster for upgrade.

        # geopg add-resource-group resourcegroup protectiongroup

    See the `geopg`(1M) man page for more information.

12. Start all the protection groups that you added.

        # 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.

## How to Verify Upgrade of Geographic Edition Software

Perform this procedure to verify that the cluster is successfully upgraded to Geographic Edition 3.3 5/11 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.

1. Become superuser on each node.
2. On each upgraded node, view the installed levels of Geographic Edition software.

       # 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 5/11 software is 1.7.

3. Ensure that the cluster is running properly.

       # geoadm status

4. (Optional) Perform a switchover to ensure that Geographic Edition software was installed properly.

       # 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.

Copyright © 2004, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |