Hi All :)
When we went from 5.5 to 6.5 pp 2 the biggest time factor was the
reboots... since our 928 takes 45+ minutes to boot... and our 979-200 (with
~6 gb of RAM) takes 30+ minutes to boot we saw some serious time there...
mixed with DDS3 tape speeds...
Art "hmmm.... reminds me time to check patch levels" Bahrs
----- Original Message -----
From: "Gary Jackson" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, October 24, 2001 8:16 AM
Subject: Re: [HP3000-L] Installing MPE 6.0: time estimates and gotchas?
> A couple more items:
>
> 1. Using PATCHIX rather than Autoinst or Autopat is a good idea. Much
> easier to use.
>
> 2. I hope Scott is planning to move to 6.5 or 7.0 soon since 6.0 will
soon
> be off of support.
>
> 3. Installation speed seems to be most affected by the age of the tape
> drive (i.e. transfer rate) and having adequate, contiguous disk space. Oh
> yeah, a fast processor help, but not as much as I first believed. My
> installations that include moving to a new base release and then adding a
> power patch usually come in at 5-6 hours, exclusive of the backup time.
>
> HTH,
>
> Gary
>
> -----Original Message-----
> From: Jim Phillips [mailto:[log in to unmask]]
> Sent: Wednesday, October 24, 2001 7:51 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Installing MPE 6.0: time estimates and gotchas?
>
>
> Scott Gates <[log in to unmask]> ponders thusly:
>
> > We're a single HP shop upgrading from MPE 5.5 to 6.0 from tape this
> weekend.
> > (oh, joy.) The manual is vague about the estimates for downtime. Has
> anyone
> > done this recently? If so, how long were you down? How long does the
> power
> > patch tape take?
>
> We did the same upgrade recently. Although we allocated the entire day
> (Sunday), it took us just over 6 hours including the full system backup
> (which obviously may vary for you). This included loading the FOS, PP,
and
> Subsys tapes (again may vary for you depending on how many sub systems you
> have). We did it all via Autoinst, rather than staging and patchman,
which
> may be quicker (I don't know, I've never used them).
>
> > Are there any gotchas you can think of.
>
> None that I know of, but we're not pushing the envelope on our production
> server. Our test server had some issues with internet-related patches, so
> if you're using Apache, Samba, or other internet-related services, be
extra
> diligent.
>
> > I've heard from the grape vine that something changes with FTP? We have
a
> > lot of jobs that FTP. Is this going to ruin my week?
>
> This may be one of those internet-related issues. I don't know as we
don't
> use FTP on our production machine, and only occasionally on our
development
> machine.
>
> > Thanks in advance for any advice or info.
>
> HTH
>
> <remainder snipped 'cause it's confidential>
>
> Jim Phillips Information Systems Manager
> Email: [log in to unmask] Therm-O-Link, Inc.
> Phone: 330-527-2124 P. O. Box 285
> Fax: 330-527-2123 10513 Freedom Street
> Web: http://www.tolwire.com Garrettsville, OH 44231
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
