From: Michael James Bradford (mjbr@tdc.dk)
Date: Wed May 07 2003 - 07:20:22 EDT
Thanks to: Maria Gilliland, Phil Baldwin, Paul LaMadeleine, Galen Johnson
and the ubiquitous Dr. Thomas Blinn for their responses.
The answer is perform a complete rolling upgrade (with all the reboots) from
V5.1 to V5.1A, then start another rolling upgrade from V5.1A to V5.1B with
patches.
To quote Dr. Tom:
Step 1: Upgrade the whole cluster from V5.1 to V5.1A. Supported,
gets
you to the starting point for the V5.1B install.
Step 2: Upgrade the whole cluster from V5.1A to V5.1B. Gets you to
the
desired end point.
You can't short-cut this. The only way I know to really shortcut
the
procedure is to go back to a single member cluster, then you've only
got one member to upgrade. But you can't roll a single member, when
you come down to it, there would be service disruptions.
Regards
Michael
============================================================
Original question:
Hi there,
We have a number of Tru Cluster clusters running V5.1 that we want to
upgrade to V5.1B. I know that it is necessary to do an installupdate to
V5.1A first. My question is: do you have to complete the whole rolling
upgrade (with all its reboots) for V5.1A before starting a complete new
rolling upgrade for V5.1B, or can you perform both installupdates in the
same Install phase?
Regards
Michael
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:18 EDT