From: Mark Schubert (Mark.Schubert@cogita.com.au)
Date: Thu Apr 08 2004 - 00:53:14 EDT
Hi David,
The only suggestions were:
- Remove nodes from the cluster until there is only one and then perform the
upgrade(s).
- Perform the 'clu_upgrade_setup 1' before the outage as it always takes the
longest time and doesn't impact the operational system.
Regards,
Mark.
-----Original Message-----
From: David.Knight@clubcorp.com [mailto:David.Knight@clubcorp.com]
Sent: Monday, 5 April 2004 9:58 PM
To: Mark Schubert
Subject: Re: Cluster upgrade
I am about to preform the same upgrade this weekend. I feel the same
about the time/outage. Did you get any good responses from the list?
Thanks,
David Knight
Mark Schubert <Mark.Schubert@cogita.com.au>
Sent by: tru64-unix-managers-owner@ornl.gov
03/22/2004 07:08 PM
To: "'tru64-unix-managers@ornl.gov'"
<tru64-unix-managers@ornl.gov>
cc:
Subject: Cluster upgrade
Hi,
We are looking at upgrading a V5.1 cluster to V5.1B with the latest patch
kit. A test upgrade has been performed using a rolling upgrade, however
this
is a very long process with lots of reboots required etc. in order to
facilitate rolling.
Is it possible to do this upgrade without doing a rolling upgrade? Ie. We
are happy for the cluster to be out for a weekend, but we want the upgrade
to be as quick as possible. The rolling upgrade process takes too long.
Can
we avoid it?
TIA,
Mark.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:56 EDT