Performing a rolling cluster upgrade from OES 1 Linux to OES 2 Linux lets you keep your cluster up and running and lets your users continue to access cluster resources while the upgrade is being performed.
During a rolling cluster upgrade, one server is upgraded to OES 2 Linux while the other servers in the cluster continue running OES 1 Linux. Then, if desired, another server can be upgraded, and then another, until all servers in the cluster have been upgraded to OES 2 Linux. You should complete the upgrade as soon as possible. Don’t leave the cluster in a mixed version state for an extended period.
To perform a rolling cluster upgrade from OES 1 Linux to OES 2 Linux:
Make a note of the OES components that are installed on the server you are upgrading.
You will probably want to install the same components on the node as you perform the upgrade.
NOTE:NSS, eDirectory, and NCP Server are not required components for Novell Cluster Services on OES 2, but are required components for Novell Cluster Services on OES 1 Linux. Ensure that you install these components on OES 2 Linux servers when you upgrade your OES 1 Linux cluster servers.
Bring down the OES 1 Linux cluster server you want to upgrade to OES 2.
Any cluster resources that were running on the server should fail over to another server in the cluster.
You can also manually migrate the resources to another server in the cluster prior to bringing down the server. This prevents the resources from failing back to the node after you have completed the upgrade.
Stop Novell Cluster Services (rcnovell-ncs stop).
Upgrade the server by using the option on the OES 2 Linux installation, making sure to install the components that are currently installed on the server that you noted in Step 1.
See Upgrading to OES 2 SP3
in the OES 2 SP3: Installation Guide.
Repeat Step 1 through Step 4 for each OES 1 Linux cluster server until your entire cluster has been upgraded to OES 2.
Start Novell Cluster Services (rcnovell-ncs start).
(Conditional) If necessary, manually migrate the resources that were on the former OES 1 server to this Linux server.
The resources will automatically fail back if both of the following apply:
The failback mode for the resources was set to Auto.
This Linux server is the preferred node for the resources.
After the last OES 1 cluster node has been upgraded to OES 2 and only OES 2 nodes remain, the conversion is complete.
(Optional) Enable Monitoring for the cluster resources and configure the Monitor scripts as described in Section 10.6, Enabling Monitoring and Configuring the Monitor Script.