Problems regarding upgrading from 3.2G to 4.0B?

From: Spalding, Steve <SSPALDIN_at_mem-ins.com>
Date: Thu, 29 Jan 1998 09:15 -0600

This weekend we are going to upgrade one member of our two Alpha cluster
from DU 3.2G to 4.0A and then to 4.0B. We do not want to upgrade both
Alphas at the same time as one of them is our production server and the
other is our development server (the development server is the one that
we're upgrading). The reason for this is that after upgrading to DU 4.0,
an Oracle patch must be installed which we don't care to thrust upon our
production system until we've had time to take a good hard look at it in
development. We suspect that we will wait for a week and then upgrade the
other member. We were told by DEC that these two Alphas would still be
able to communicate through the shared SCSI bus and both access the disk
drives on our HSZ50 even though our operating systems and clustering
software versions will be different.

To recap, what we will have is one Alpha 2100 running DU 4.0B and
Truecluster 1.4 and one Alpha 4100 running DU 3.2G and ASE 1.3 which are
connected through a shared SCSI bus which has an HSZ50 in the middle of
it. The only thing that we use the clustering software for is the SCSI
drivers; we do not have any services set up yet. Has anyone had a similar
set up, and if so, would you care to share any problems or other issues
that needed to be dealt with?

Thank you very much!

Stephen Spalding
Missouri Employers Mutual Insurance
sspaldin_at_mem-ins.com
Received on Thu Jan 29 1998 - 16:14:30 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:37 NZDT