SUMMARY: Upgrading from 4.0G to 5.1A

From: Deacy, Michael (Michael.Deacy@TycoHealthcare.com)
Date: Mon Feb 03 2003 - 15:39:30 EST


Admins:

My original question followed by the responses. Thanks to the following for
their replies and sorry for the late summary:

> Admins:
>
> I'm upgrading an A/S 4100 from 4.0G to 5.1A. According to HP I need
> to go through 5.1. I'm considering using an offline system to build
> the disks (root_domain / usr_domain) ahead of time, and then boot
> from them instead of the existing disks. These two domains are on
> ordinary HSZ70 devices. The user/application data is on domains
> that reside on LSM volumes - some of the domains have more than one
> AdvFS volumes.
>
> I've checked the archives and gotten some mixed reviews on whether
> this is a wise course of action. Are there any other
> recommendations or fresh experiences?

For the record, I staged it ahead of time in test and the normal install
path went well. If I uncover anything worthwhile I will re-summarize. I
may try the fresh install for the next system when I have more time to run
through the paces. Mike

from Pat O'Brien

You have a little differeent scenario than I did. I did not have advfs
root, usr doamins, but I did have lsm mirrored which I think was worse. I
have done 20 upgrades from 4.0e, or f to 5.1 via 4.0g. I add 2 additional
disks which I call the lsm vol and the miniroot disk. Partition miniroot as
desired /, usr, swap, and newfs, and then vdump |vrestore the fs data to the
new domains, then boot to verified that root disk will work. If I need to
re-size original root, then I will utilize the lsm disk to save lsm config
by adding lsm private area on this disk. resize root disk, and vdump
|vrestore bacck to the original root single disk. The upgrades go miserable
with mirrored root disks, and sometimes do work, but my experience is go for
it in single disk mode and mirror afterwards. If you have multiple kgpsa,s,
get ready for fun. This is of course the 50 thousand foot view, as there
are many details involved in making the miniroot bootable etc.

fyi skip 5.0a as it is buggy at best, and will fail miserable at worst.
with a online copy of the os, failback is real painless. I discovered more
failure points than I care to ever think about, but having the live failback
really simplified things rather than getting tapes out for restores.

from Thomas Sjolshagen

My personal opinion is that a clean install is a more clean method when
going from V4.0x to V5.1x. If you do a clean install of V5.1a, do an lsm
config export from V4.0g and configure LSM on V5.1a, LSM should scan the
physical storage for LSM volumes and convert the v4.0g LSM metadata to
the V5 format automatically (note that once you start LSM on V5, vold
will scan for LSM volumes in the storage environment and silently
commence the conversion - a one-way conversion).

  // Thomas

from Kjell Andresen:

Reinstall; much faster and you get rid of many older files not in use.
My systems seems a lot healthier after the last round were I only did one
upgrade; fra v5.1 to v5.1a - the rest was reinstalled.

I wrote down my experiences at
<URL:http://www.usit.uio.no/it/unix/du/reinstallere-v51A.txt> - guess
you are able to scan through it even though there are words in Norwegian
in the text.
If you want to use it and have questions I may find the effort worth
of translating it as well

Regards,
Kjell Andresen



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:06 EDT