|
| |
| Sun Java Enterprise System 2005Q4 Upgrade Guide | |
Chapter 3
Sun Cluster SoftwareThis chapter describes how to upgrade Sun Cluster software to Java ES 2005Q4 (Release 4): Sun Cluster 3.1 8/05.
The chapter provides a general overview of upgrade issues and procedures for upgrading Sun Cluster software to Java ES Release 4.
Sun Cluster software is supported only on Solaris platforms.
The upgrade of Sun Cluster software described in this chapter includes both Sun Cluster framework software and Sun Cluster data-service software, or agents.
Overview of Sun Cluster Software UpgradesThis section describes the following general aspects of Sun Cluster software that impact upgrading to Java ES 2005Q4 (Release 4):
About Java ES Release 4 Sun Cluster Software
Java ES Release 4 Sun Cluster software includes a number of new features, including improved cluster installation and upgrade functionality, enhanced support for Network Appliance NAS devices, a simplified SunPlex Manager interface, and other features detailed in the Sun Cluster Release Notes, http://docs.sun.com/doc/819-1405/6n3p13hac?a=view
Sun Cluster Software Upgrade Roadmap
Table 3-1 shows the supported Sun Cluster upgrade paths to Java ES Release 4. The table applies to the Solaris operating system only.
Sun Cluster versions do not map one-to-one to Java ES releases. This is because Sun Cluster software’s interim feature releases (IFRs) were incorporated into Java ES between formal Java ES releases. For this reason, the upgrade of Java ES Release 3 Sun Cluster and Java ES Release 2 Sun Cluster to Java ES Release 4 Sun Cluster, as shown in Table 3-1, includes the upgrade of both Sun Cluster 3.1 4/04 and Sun Cluster 3.1 9/04 software to Java ES Release 4.
Sun Cluster Data
The following table shows the type of data that could be impacted by an upgrade of Sun Cluster software.
Compatibility Issues
Java ES Release 4 Sun Cluster software includes new graphical administration interfaces, but is backwardly compatible with earlier releases of Sun Cluster agents.
Sun Cluster Dependencies
Sun Cluster dependencies on other Java ES components can impact the procedure for upgrading and re-configuring Sun Cluster software. Changes in Sun Cluster interfaces or functions, for example, could require upgraded versions of components upon which Sun Cluster software depends. The need to upgrade such components depends upon the specific upgrade path.
Sun Cluster has dependencies on the following Java ES components:
- Shared components. Sun Cluster software has dependencies on specific Java ES shared components (see Table 1-6).
- Data services. Sun Cluster software requires specific data services (or agents) to make Java ES product components highly available. For each product component running in a Sun Cluster environment there must be a corresponding data service to manage the corresponding cluster resources. Agent packages are typically upgraded as part of the Sun Cluster upgrade process.
Upgrading Sun Cluster Software to Java ES Release 4This section includes information about upgrading Sun Cluster software from both Java ES 2005Q1 (Release 3) and Java ES 2004Q2 (Release 2) to Java ES Release 4. The upgrade procedure is the same for the two Sun Cluster versions found in these Java ES releases: Sun Cluster 3.1 4/04 and Sun Cluster 3.1 9/04 software.
The section covers the following topics:
Introduction
When upgrading Sun Cluster software to Java ES Release 4, consider the following aspects of the upgrade process:
- General Upgrade Approach. The upgrade is performed by running the scinstall script which upgrades Sun Cluster software and applies the previous Sun Cluster configuration after the software upgrade is complete. However all nodes in a cluster environment must be upgraded to the same version, either by shutting down the cluster and upgrading all nodes, or through a rolling upgrade in which the nodes are successively upgraded one at a time without shutting down the cluster.
- Upgrade Dependencies. While Sun Cluster software has dependencies on a number of Java ES shared components (see Table 1-6), Java ES Release 4 Sun Cluster software is compatible with the Release 3 versions of these components. Upgrade of these shared components is therefore optional with respect to upgrade of Sun Cluster software to Release 4.
- Backward Compatibility. Release 4 Sun Cluster software is backwardly compatible with earlier cluster agents, however all nodes in a cluster must run the same version of framework and agent software.
- Upgrade Rollback. Rollback of the Release 4 upgrade of Sun Cluster software to earlier versions is not supported.
- Platform Issues. The approach for upgrading Sun Cluster software is the same on all Solaris platforms, however Sun Cluster software is not supported on Linux platforms.
Sun Cluster Upgrade
This section provides an overview of how to perform an upgrade of Sun Cluster software from Java ES Release 3 to Java ES Release 4:
The section covers the case of a nonrolling Sun Cluster upgrade. The case of a rolling upgrade is a bit different, in that the cluster is not shut down. However both cases involve the same general procedures, as described below, for a given cluster node. The specific procedures can be found in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view.
Pre-Upgrade Tasks
Before you upgrade Sun Cluster software you should perform the tasks described below.
Verify Current Version Information
You can verify the current version of Sun Cluster software by entering the following command:
% scinstall -pv
The command returns the Sun Cluster version and the version of each software package installed. If this command returns the 3.1 8/05 version, 3.1u4, then no upgrade to Java ES Release 4 is needed.
Prepare the Cluster Node for Upgrade
The cluster node must be removed from the cluster environment before Sun Cluster software can be upgraded:
- Nonrolling upgrades. Removing the node from the cluster environment means shutting down the environment: switching resource groups offline, disabling them, shutting down applications running in the environment, backing up shared data, shutting down the cluster, backing up the system disk, and rebooting the node into non-cluster mode.
- Rolling upgrades. Removing the node from the cluster environment means moving all resource groups and device groups from the node, backing up shared data and the system disk, and rebooting the node into non-cluster mode.
The details of these operations and others that might need to be performed in specific situations are provided in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view.
Upgrade the Operating System
You might wish to make use of any upgrade downtime to upgrade your operating system to its most current version, and also upgrade the version of volume manager that you are using.
The details of these operations are provided in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view.
Upgrade Sun Cluster 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 4. Upgrade of Release 3 shared components upon which Sun Cluster software depends is optional, but upgrade of Release 2 shared components to Release 4 is mandatory.
To upgrade all shared components upon which Sun Cluster software depends (see Table 1-6), you can follow the instructions provided in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view, except upgrade all the shared components even if minimum version requirements are met.
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 Sun Cluster Software
This section discusses considerations that impact the upgrade procedure for Sun Cluster software followed by a description of the procedure itself.
Upgrade Considerations
The upgrade of Sun Cluster software to Java ES Release 4 takes into account the following considerations:
- When upgrading Sun Cluster framework software it is a good idea to upgrade the data services needed to manage highly available Java ES components or other applications that run in your cluster environment.
- Upgrading Sun Cluster software also provides an opportunity to upgrade Java ES components or other applications that run in your cluster environment.
Upgrade Procedure
The procedure below applies to upgrading Sun Cluster software on each cluster node. The steps that follow are very general; details on how to perform these steps are provided in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view.
- Log in as root or become superuser.
su -
- Change to the following directory on the Java ES distribution:
cd /Solaris_arch/Product/sun_cluster/Solaris_ver/Tools
where arch is sparc or x86 and ver is 8, 9, or 10 for Solaris 8, 9, or 10, respectively.
- Run the scinstall utility.
./scinstall
A main menu is displayed for performing cluster installation, configuration, and upgrade tasks.
- Upgrade Sun Cluster framework software and any desired data services.
Upgraded data services need to be configured by migrating the corresponding resources to the upgraded resource types (see Post-Upgrade Tasks).
- Apply any necessary patches to Sun Cluster framework software and to data services.
Information on accessing and applying the relevant patches is provided in the Sun Cluster Release Notes, http://docs.sun.com/doc/819-1405.
- Reboot the node into the cluster.
Verifying the Upgrade
You can verify successful upgrade of Sun Cluster software as follows:
- Check the version number of Sun Cluster framework software.
scinstall -pv
See Table 3-3 for output values.
- Check the data service upgrade log file.
The log file is referenced at the end of upgrade output messages.
Post-Upgrade Tasks
After you perform the upgrade of Sun Cluster software, you might need to perform a number of additional tasks, depending on whether you performed a nonrolling or a rolling upgrade. Among the tasks required to fully restore your cluster environment are:
Details for these post-installation steps are provided in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view.
Rolling Back the Upgrade
Rollback of Sun Cluster software is not supported. Changes made during the upgrade procedure cannot easily be backed out.