Re: Upgrading VMS on a system where hardware is newer than the system disk OS supports

From: Mike Naime (mnaime_at_kc.rr.com)
Date: 02/27/04 

Date: Thu, 26 Feb 2004 20:39:19 -0600

I had a similar experience when moving a box from a QBB of a GS320 to an
ES47. I had already re-pointed my SAN drives to the newer server, and I
tried to boot. It failed. I was not able to boot until after I performed
the VMS upgrade. I inserted the Upgrade CD, booted the CD and upgraded the
SAN based OS disk. After the upgrade completed, I was able to boot the
system.

Rich Jordan <jordan@ccs4vms.com> wrote in message
news:cc5619f2.0402261407.4d6ebda8@posting.google.com...
> Here's a new one for us. I've never had this come up, and I can't do
> a test run due to lack of hardware. We have a customer with a DS10
> running V7.2-1. They're going to upgrade to a DS15, which has a
> minimum VMS requirement of V7.3-1 (plus TIMA). There is a miniscule
> downtime window.
>
> Since doing a V7.2-1 upgrade to V7.3-1 or newer on the DS10 is not
> feasible due to time, I'm wondering if the following is supported.
>
> Image backup the DS10 disks to tape, then restore on the DS15 disks
> using the CD boot environment. We won't try to boot the DS15 on the
> V7.2-1 system disk.
>
> Boot the DS15 with the V7.3-1 (or -2) CD and upgrade the V7.2-1 system
> disk. Bring up a happy DS15 with supported OS.
>
> In other words are there any issues upgrading a VMS system disk from a
> version not supported on the hardware being used for the upgrade,
> since we are obviously using a supported version to boot and actually
> perform the upgrade?
>
> Seems like there should be no problem, but if anyone knows I'd
> appreciate hearing about it.
>
> Rich Jordan
> CCS

Relevant Pages