Howdy,

Richard has a couple of points which in my morning fog I passed off as
"Yeah, so? Everyone knows that".
Not so fast there Cooter.  This question comes from a person doing something
new to them which is not
a minor undertaking.  Over the years I've stuffed a number of operating
systems into the 3000, only
one (4.0 --> 5.0) has gone as expected without a hitch.  For the new folks
let me from my/our
experience re-emphasize a couple of things Richard says.

On Monday, January 11, 1999 4:56 PM, Richard Gambrell
[SMTP:[log in to unmask]] wrote:
> Bonnie Roman wrote:
> >
> > I have been an administrator for some years now but never done an
upgrade,
> > I have done tones to
> > pathes, and now my boss asked me to put a project plan together.
> >
> > Other than printing out copies of the system configuration, and course
the
> > obvious a full backup, and slt.
> >
> > what other things should I keep in mind, and prepare for?
< opening snipped >
> I haven't done a update to 6, but I can give general advice:
>
> Be sure your backup was done with the ;directory option (for Store, or
> equivalent for other backup products).   If you use user volumns, each of
them
> and the system must be specified in the store command for the directory.

 And if time allows (make time) verify the backups or make a second backup
or both.

< snip dealing with volume sets >

>
> If you use 3rd party system utilities, like MPEX, Formation, even Qedit,
and
> others, be sure you know how to reinstall the hooks into "the system for
> these products.

Be prepared for a third party product not to work when it hits production.
Have you got phone numbers
for weekend/night tech assistance?  Yes some outfits don't provide this sort
of service - are you good
buddies with other sites that run the same product)s)?

> Take a look at the backout part in the update documentation to see what
else
> you might need.
>

I sort of briefed over it once.  Then had to regress the operating system
from 4.5 back to 4.0 after it had
been in production for a week. Not pretty.

> Finally, when you do the update, be sure to login manager.sys from as
"clean"
> and "standard" an enviornment as possible.  Little thinks like file
equates,
> changes to HPPATH, UDCs with the same names as system commands, etc., can
> cause trouble.
>
The manual tells you to do this.  Do it.

> If something goes wrong, call the RC before you try to fix it, unless your
> very, very sure of what needs to be done.  Most things that happen to
cause
> trouble an upgrade can be fixed easily enough without going through
> re-install of the old stuff.
>

Absolutely.  If the manual says go  F, G, H, I, .... and the installation
goes F, G, bump, straighten it
out now.  Even if you don't have access to HPRC insure you have some sort of
tech backup - unless you
have a crash and burn system and oodles of time.  And an extremely high
frustration level.

> >
> > In what order should I do the upgrade, FOS,  SUBSYS tape etc...?
>
> Just follow the directions in the update manual.  It may help to look over
> them ahead of time:-)
>
> Be sure to read any other "stuff" that comes with in the update kit,
before
> doing the update.
>

Amen.  Read it twice. Read it thrice.  Make notes.  Highlight or otherwise
markup the path *you* will be
using.  Any questions/doubts contact whoever and get them resolved before
the installation.

In addition to Richard's advise I might add: Prior to installation get a
good nights sleep, pound down a big
breakfast, wave goodby to the kids.

Seriously, these things usually go smoothly in direct proportion to
preparedness.

Now, off to prepare my next post - off topic.

Jim Trudeau