|
| |
| Sun Java Enterprise System 5 Upgrade Guide for UNIX | |
Chapter 4
Sun Cluster Geographic EditionThis chapter describes how to upgrade Sun Cluster Geographic Edition to Java ES 5 (Release 5): Sun Cluster Geographic Edition 3.1 2006Q4.
The chapter provides an overview of upgrade considerations for the different upgrade paths supported by Release 5. The chapter covers upgrades on only the Solaris operating system:
Overview of Sun Cluster Geographic Edition UpgradesThis section describes the following general aspects of Sun Cluster Geographic Edition that impact upgrading to Java ES 5 (Release 5):
About Java ES Release 5
Java ES Release 5 Sun Cluster Geographic Edition is the first release to be delivered as a Java ES component; Sun Cluster Geographic Edition 3.1 was first released as a standalone product.
Release 5 Sun Cluster Geographic Edition represents a minor release with respect to Sun Cluster Geographic Edition 3.1 8/05. It is the first release to support the Solaris x86 platform. Release 5 Sun Cluster Geographic Edition also includes some selected bug fixes, qualifications for various hardware and software components, and support for additional data replication products.
Java ES Release 5 Upgrade Roadmap
Table 4-2 shows the supported Sun Cluster Geographic Edition upgrade paths to Java ES Release 5. The table applies to the Solaris operating system only.
Sun Cluster Geographic Edition Data
The following table shows the type of data that can be impacted through an upgrade of Sun Cluster Geographic Edition software.
Sun Cluster Geographic Edition Upgrade Strategy
Your strategy for upgrading Sun Cluster Geographic Edition generally depends on the many considerations discussed in Chapter 1, "Planning for Upgrades": upgrade path, dependencies between Java ES components, selective upgrade versus upgrade all, multi-instance deployments, and so forth.
This section is to particularize that general discussion to Sun Cluster Geographic Edition by presenting issues that might influence your Sun Cluster Geographic Edition upgrade plan.
Compatibility Issues
Both clusters in a partnership have to run the same version of Sun Cluster Geographic Edition. Hence, Release 5 Sun Cluster Geographic Edition cannot be mixed in a partnership with Sun Cluster Geographic Edition 3.1 8/05 (there is no backward compatibility). Release 5 Sun Cluster Geographic Edition includes additional configuration data which can't be read by Sun Cluster Geographic Edition 3.1 8/05.
Dependencies
Sun Cluster Geographic Edition dependencies on other Java ES components can impact the procedure for upgrading and re-configuring Sun Cluster Geographic Edition software. Changes in Sun Cluster Geographic Edition interfaces or functions, for example, could require upgraded version of components upon which Sun Cluster Geographic Edition depends. The need to upgrade such components depends upon the specific upgrade path.
Sun Cluster Geographic Edition has dependencies on the following Java ES components:
- Shared components. Sun Cluster Geographic Edition has dependencies on specific Java ES shared components (see Table 1-9).
- Sun Cluster. Sun Cluster Geographic Edition has a mandatory dependency on Sun Cluster, which provides base functionality.
Dual Upgrade
Dual upgrades, in which both Sun Cluster Geographic Edition software and operating system are upgraded (as described in Dual Upgrades: Java ES and Operating System Softwared) do not apply to Sun Cluster Geographic Edition.
Because Sun Cluster Geographic Edition has a hard upgrade dependency on Sun Cluster, the operating system upgrade is performed in the context of the Sun Cluster upgrade. See Dual Upgrade for information about Sun Cluster dual upgrades.
Upgrading Sun Cluster Geographic Edition from Version 3.1 8/05This section includes information about upgrading Sun Cluster Geographic Edition from version 3.1 8/05 to Java ES 5 (Release 5). The section covers the following topics:
Introduction
When upgrading Sun Cluster Geographic Edition 3.1 8/05 to Release 5, consider the following aspects of the upgrade process:
- General Upgrade Approach. The upgrade is achieved by uninstalling Version 3.1 8/05 and performing a fresh install of Release 5 Sun Cluster Geographic Edition. Configuration data is retained.
- Upgrade Dependencies. Sun Cluster Geographic Edition has dependencies on a number of Java ES shared components (see Table 1-9), all of which are automatically upgraded to Release 5 by the Java ES installer when you perform an upgrade of Sun Cluster Geographic Edition. In particular, Sun Cluster Geographic Edition has a hard upgrade dependency on Common Agent Container, version 1.1. Sun Cluster Geographic Edition also has a hard upgrade dependency on Sun Cluster: Release 4 Sun Cluster (3.1 8/05) must be upgraded to Release 5 to support Release 5 Sun Cluster Geographic Edition.
- Backward Compatibility. Release 5 Sun Cluster Geographic Edition is not compatible with Sun Cluster Geographic Edition 3.1 8/05. All clusters in a partnership must be upgraded to Release 5.
- Upgrade Rollback. Rollback of the Release 5 upgrade of Sun Cluster Geographic Edition software to version 3.1 8/05 is not supported.
- Platform Issues. The approach for upgrading Sun Cluster Geographic Edition software is the same on all Solaris platforms and hardware architectures, however Sun Cluster Geographic Edition software is not supported on Linux platforms.
Version 3.1 8/05 Sun Cluster Geographic Edition Upgrade
This section describes how to perform an upgrade of Sun Cluster Geographic Edition from version 3.1 8/05 to Java ES Release 5. The section covers the following topics:
Pre-Upgrade Tasks
Before you upgrade Sun Cluster Geographic Edition software you should perform the following tasks:
Verify Current Version Information
You can verify the current version of Sun Cluster Geographic Edition using the following command:
/usr/cluster/bin/geoadm --version
The version string follows the copyright text, and is shown in the following table:
Table 4-4 Sun Cluster Geographic Edition Version Verification Outputs
Java ES Release
Sun Cluster Geographic Edition Version Number
Version 3.1 8/05
1.0
Release 5
1.1
Prepare a Cluster for an Upgrade
Perform the following steps on all clusters that have a partnership with the cluster you are upgrading. The procedure removes the Sun Cluster Geographic Edition layer from production.
- Ensure that the cluster is functioning properly.
To view the current status of the cluster, run the following command from any node.
scstat
- Log in as root or become superuser.
su -
- Remove all application resource groups from protection groups.
Highly available applications do not have downtime during the Sun Cluster Geographic Edition upgrade.
geopg remove-resource-group resourcegroup protectiongroupname
- Stop all protection groups that are active on the cluster.
geopg stop protectiongroupname -e local | global
- Remove the ICRM plug-in from all the heartbeats on both partner clusters.
geohp remove-plugin icrmplugin heartbeatname
Upgrade Sun Cluster Geographic Edition Dependencies
It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Java ES Release 5. Sun Cluster Geographic Edition has hard upgrade dependencies on a number of shared components and on Sun Cluster.
When upgrading Sun Cluster Geographic Edition dependencies, you should do so in the order below (skipping any that might already have been upgraded), before you upgrade Sun Cluster Geographic Edition. Upgrade of shared components is normally achieved automatically by the Java ES installer.
- Shared Components. Instructions for synchronizing Java ES shared components to Release 5 are provided in Upgrading Java ES Shared Components. However, all shared components required by Sun Cluster Geographic Edition are upgraded automatically by the Java ES installer when you perform an upgrade of Sun Cluster Geographic Edition to Release 5.
- Sun Cluster. Instructions for upgrading Sun Cluster to Release 5 are provided in Chapter 3, "Sun Cluster Software".
Back Up Sun Cluster Geographic Edition Data
Sun Cluster Geographic Edition stores all data in the Cluster Configuration Repository, so there is no need to back up current data.
Obtain Required Configuration Information and Passwords
No special information about your currently installed version is needed. However you will have to log in as superuser to perform the upgrade.
Upgrading 3.1 8/05 Sun Cluster Geographic Edition
This section discusses considerations that impact the upgrade procedure for Sun Cluster Geographic Edition followed by a description of the procedure itself.
Upgrade Considerations
The upgrade of Sun Cluster Geographic Edition software to Java ES Release 5 should be possible without disturbing running applications. You can upgrade Sun Cluster Geographic Edition software on a running cluster without disruption; the cluster remains in production with services running. Similarly, you can also apply Sun Cluster Geographic Edition patches without downtime. Configuration data is retained across the upgrade process.
Sun Cluster Geographic Edition software must be upgraded on all nodes of all clusters that have a partnership with the cluster you are upgrading.
If you want upgrade the Solaris operating system during the Sun Cluster Geographic Edition software upgrade process, you must remove the Sun Cluster Geographic Edition packages before you upgrade the Solaris operating system.
Upgrade Procedure
The procedure documented below applies to Sun Cluster Geographic Edition instances residing locally on the computer where the upgrade is taking place.
- Log in as root or become superuser.
su -
- Shut down Sun Cluster Geographic Edition 3.1 8/05.
/usr/cluster/bin/geoadm stop
To leave the underlying applications running while shutting down Sun Cluster Geographic Edition, see the Sun Cluster Geographic Edition System Administration Guide, http://docs.sun.com/doc/819-8003.
- Uninstall Sun Cluster Geographic Edition 3.1 8/05.
SunClusterGeo-base/install/uninstall/uninstaller
Use the Sun Cluster Geographic Edition installer in uninstall mode, as documented in the Sun Cluster Geographic Edition Installation Guide, http://docs.sun.com/doc/819-8004.
- If Sun Cluster is not running start it up.
Sun Cluster must be running to install Sun Cluster Geographic Edition. You can check it using the scstat command.
- Perform a fresh install of Release 5 Sun Cluster Geographic Edition using the Java ES installer.
- Launch the Java ES installer on the computer hosting Release 4 Access Manager.
cd Java ES Release 5 distribution/os_arch
./installerwhere os_arch matches your platform, such as Solaris_sparc. (Use the installer -nodisplay option for the command line interface.)
After the Welcome and License Agreement pages are displayed, you will be presented with a component selection page. (When installed components are detected that can be directly upgraded by the Java ES installer, they are shown with a status of “upgradable.”)
- Select Sun Cluster Geographic Edition from the component selection page.
- Choose to Configure Now or Configure Later.
It makes no difference whether you choose to configure now or to configure later because no Reconfiguration is required.
- If needed, select the option to install localized packages.
- Exit the Java ES installer when installation is complete.
- Install all the required Sun Cluster Geographic Edition patches.
For instructions, see the Sun Cluster Geographic Edition Installation Guide, http://docs.sun.com/doc/819-8004.
- Re-start Release 5 Sun Cluster Geographic Edition software.
/usr/cluster/bin/geoadm start
If the cluster is in a partnership, all nodes on both partners must be upgraded before Sun Cluster Geographic Edition software is started up.
For more information, consult the Installation Guide referenced above and the Sun Cluster Geographic Edition System Administration Guide, http://docs.sun.com/doc/819-8003.
- Add all application resource groups you removed when preparing for a cluster upgrade as described in Prepare a Cluster for an Upgrade.
geopg add-resource-group resourcegroup protectiongroupname
- Start all the protection groups you have added.
geopg start protectiongroupname -e local | global [-n]
Verifying the Upgrade
You can verify successful upgrade of Sun Cluster Geographic Edition software as follows:
- Run the following command:
/usr/cluster/bin/geoadm --version
See Table 4-4 for output values.
- If applicable, after upgrading both partners, run the following commands on one cluster node of each partner.
/usr/cluster/bin/geoadm start
/usr/cluster/bin/geoadm showThe command will show whether Sun Cluster Geographic Edition software is active on that node.
Post-Upgrade Tasks
There are no post-upgrade tasks beyond the steps described in Upgrade Procedure.
Rolling Back the Upgrade
Rollback of Sun Cluster Geographic Edition software is not supported.
However, you can remove Release 5 Sun Cluster Geographic Edition using the uninstall function of the Java ES installer and then use the version 3.1 8/05 installer to re-install version 3.1 8/05. Because Release 5 Sun Cluster Geographic Edition writes data which version 3.1 8/05 cannot read, any such rollback would have to be performed before Release 5 had been started, that is before you start the upgraded Sun Cluster Geographic Edition.software, as described in Upgrade Procedure.