Thank you very much to the following people who responded to my request
for information regarding potential problems while upgrading from 4.0b
to 4.0d. For the record I have included their experiences.
The speedy responses were very much appreciated! Thanks again.
Rob
Pat Wilson
Jim R Jones
Ronald D Bowman
John Francini
Allan G Beardsley
Bryan Lavelle
I have upgraded about 40 workstations and 10 servers so far and have not
had any problems. The biggest problem is that on a number of the
workstations and several servers the system partitions were to small so
had to redo the partitions and then install,which is a real pain. But
that is about all.
jim jones
The one *big* gotcha is if you're doing any remote host stuff with
syslog - make sure to set up /etc/syslog.auth (see pg 4-14of the 4.0D
release notes).We've had lots of trouble with AdvFS at 4.0D - I think
the latest patches _may_ have made it stable, but some of our machines
are stuck at 4.0B because we can't take the chance that the upgrade will
break things. If you're not running AdvFS,though, this isn't an issue.
Pat Wilson
Hi Rob - I don't have any specific help on this matter. However, the
question has been asked several times. Below my name are the urls of the
search engines for the mailing list. I imagine you will be able to find
all the information you need there. I hope that helps some.
Ron Bowman
Unfortunately, I don't have any horror stories to tell. My upgrades all
went rather smoothly. If you're using any AdvFS filesets, do follow the
advice in the manual about running the fileset checker _prior_ to the
upgrade. Also: if you use any drivers for anything that has to be linked
into the kernel, such as the SCSI CAM Media Changer package or the CAM
Optical Driver package, you'll need to uninstall them, do the upgrade,
then reinstall them.The install update procedure will give you a list of
products that must be deinstalled before upgrade can take place.It will
also give you a list of products that you may have to reinstall after
the upgrade is complete. You should expect to do this, especially things
like the C++ runtime library and the like.
John Francini
Hi Robin, I just completed the upgrade on Saturday from DU 4.0B to 4.0D
on anAlpha 2100 server and I did run into some problems that I was able
to resolve with some help from the DEC support line. Be sure that you
upgrade the firmware and ECU first. When I started the upgrade, I
usedthe install update utility with the interactive (i) option set. The
subsetsall loaded and merged successfully but at that point the
interactive menu to select the kernel options did not appear, and the
system went into are boot and failed to reboot. I think the problem may
have been due to the fact that when I upgraded the firmware I did not
upgrade the ECU (EISA Configuration Utility). So I had to upgrade the
ECU before the system would continue with the new kernel build and from
that point it worked fine.
Alan Beardsley
1) Do a backup.
2) See # 1
3) Read the release notes, some products need to be reinstalled, you
should get a warning during the upgrade as to which ones they will be.
Heed the warnings.
4) Run verify against all advfs domains before attempting the update and
fix any problems that you have.
5) Immediately after the update, remove the daily defrag cron from cron
or comment it out.
6) Apply the latest patch kit.
7) If the latest patch kit is patch kit 2 or what we call BL10, then
remove patch #153 using the dupatch utility.
Bryan
______________________________________________________
Get Your Private, Free Email at
http://www.hotmail.com
Received on Tue Nov 17 1998 - 15:29:07 NZDT