test

Sun Cluster Geographic Edition Installation Guide

Upgrading a Sun Cluster Geographic Edition Configuration

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

Upgrade Requirements and Software Support Guidelines

Observe the following requirements and software-support guidelines on all clusters that have a partnership with the cluster you are upgrading when you upgrade a cluster to the Sun Cluster Geographic Edition 3.1 2006Q4 software:

ProcedureHow 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 Sun Cluster Geographic Edition layer from production. On the Solaris 10 OS, perform all steps from the global zone only.

Highly available applications do not have downtime during the Sun Cluster Geographic Edition software upgrade.

Before You Begin

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 Solaris OS and Sun Cluster Geographic Edition 3.1 2006Q4 software.

If you want to upgrade the Solaris OS or other applications during the Sun Cluster Geographic Edition software upgrade process, you must remove the Sun Cluster Geographic Edition packages before you upgrade the Solaris OS or other applications.

For information about uninstalling Sun Cluster Geographic Edition software, see Uninstallation Overview to determine the proper method of uninstallation.

  1. Ensure that the cluster is functioning properly.

    To view the current status of the cluster, run the following command from any node:


    % scstat

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

    Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.

    Check the volume manager status.

  2. On a node of the cluster, become root. 


    % su

  3. Remove all application resource groups from protection groups.

    Highly available applications do not have downtime during the Sun Cluster Geographic Edition software upgrade.


    # geopg remove-resource-group resourcegroup protectiongroupname

    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 protectiongroupname -e local | global

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

  6. Stop the Sun Cluster Geographic Edition infrastructure. 


    # geoadm stop

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

Next Steps

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

ProcedureHow to Upgrade Sun Cluster 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 – Caution –

If the cluster is in a partnership, both partners must be upgraded to the Sun Cluster Geographic Edition 3.1 2006Q4 software before the Sun Cluster Geographic Edition 3.1 2006Q4 software can start.

  1. To use the uninstaller utility 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

  2. Become root on the node or cluster where you intend to uninstall the Sun Cluster Geographic Edition software.


    % su

  3. Uninstall the Sun Cluster Geographic Edition 3.1 8/05 software.

    For more information about how to leave applications running while shutting down the Sun Cluster Geographic Edition software, see Disabling the Sun Cluster Geographic Edition Software in Sun Cluster Geographic Edition System Administration Guide.

  4. Ensure that all the nodes are online and part of the cluster.

    To view the current status of the cluster, run the following command from any node:


    % scstat

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

    Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.

  5. Upgrade to common agent container 1.1.

    See Upgrading Common Agent Container in Sun Java Enterprise System 2006Q3 Upgrade Guide for more information.

  6. Install the Sun Cluster Geographic Edition software as described in Chapter 2, Installing the Sun Cluster Geographic Edition Software.

  7. Install all the required patches as described in Installing Patches.

  8. Perform the preceding steps on all clusters that have a partnership with this cluster.

  9. After you have installed Sun Cluster Geographic Edition software on all the nodes of a cluster, enable the Sun Cluster Geographic Edition software.


    # geoadm start

  10. Remove the ICRM plug-in from all the heartbeats on both partner clusters. 


    phys-paris-1 # geohb remove-plugin icrm_plugin hb_paris~new-york
phys-paris-1 # geohb remove-plugin icrm_plugin hb_new-york~paris
phys-newyork-1 # geohb remove-plugin icrm_plugin hb_paris~new-york
phys-newyork-1 # geohb remove-plugin icrm_plugin hb_new-york~paris

  11. Add all application resource groups you removed while you were preparing the cluster for an upgrade back to the protection group. 


    # geopg add-resource-group resourcegroup protectiongroupname

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

  12. Start all the protection groups that you have added. 


    # geopg start  protectiongroupname -e local | global [-n]

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

Next Steps

Go to How to Verify Upgrade of Sun Cluster Geographic Edition 3.1 2006Q4 Software

ProcedureHow to Verify Upgrade of Sun Cluster Geographic Edition 3.1 2006Q4 Software

Perform this procedure to verify that the cluster is successfully upgraded to Sun Cluster Geographic Edition 3.1 2006Q4 software. On the Solaris 10 OS, 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. On each node, become root.

  2. On each upgraded node, view the installed levels of Sun Cluster Geographic Edition software.


    # geoadm -V

    The first line of output states which version of Sun Cluster 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 Sun Cluster Geographic Edition 3.1 2006Q4 software should be 1.1.

  3. Ensure that the cluster is running properly. 


    # geoadm status

  4. (Optional) You can also run a switchover to ensure that the Sun Cluster Geographic Edition software was installed properly.


    # geopg switchover

    You must test you 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 all still works. If the switchover fails, the primary site is untouched and you can switch back. If all works on the secondary site then after a certain 'soak time' you can upgrade the primary site as well.

    Caution – Caution –

    A switchover might disrupt the services that are running on the cluster. You should carefully plan the required tasks and resources before performing a switchover.

    If you have added your application resource groups back into the protection groups, then performing a switchover shuts down the applications on the original primary cluster and migrates the applications to the secondary cluster.