XDelta - OpenVMS-based mission critical systems and infrastucture
OpenVMS migration - urgency and complexity

How urgent is my need to migrate ?

The diagram illustrates the typical levels of urgency by hardware platform and scale. There are three hardware platform types (Integrity, Alpha and VAX) and the HPVM virtualisation platform hosted on HPUX. Hardware platforms can be either physical or emulated (both Alpha and VAX emulators are available). Emulated platforms do not solve the problem of end-of-life for the operating system, they only solve the problem of end-of-life for the physical hardware.

If you operate in a business environment where supported systems are mandated, you have no choice but to migrate to a supported version of the operating system running on a supported hardware platform. Migration should be completed before support expires for the operating system or the hardware platform. VSI have supported versions of OpenVMS for Integrity Servers and AlphaServers, plus a "performance release" for EV6 and later AlphaServers.

Those running large and complex systems have the greatest problem, especially with hardware such as the AlphaServer GS1280 or BL890c-i2 Integrity Server with EVA based storage infrastructure.

Integrity Server platforms

The final "Kittson" processor Itanium based systems (the -i6 family of Integrity Servers) went "end of sale" at the end of 2020. The HPE blade system based on the c7000 and c3000 chassis also went "end of sale" during 2020.

Those running large machines and now reaching the edge of capacity and performance have an urgent requirement. They need to migrate to VSI OpenVMS and VSI layered products which have support for the -i4 and -i6 families of servers.

EVA storage is now end-of-life. 3PAR storage is qualified for use with OpenVMS on Integrity, including use as a boot device. Other storage subsystems are also available and support for them is documented on the VSI web site. The rack-mount rx2800-i6 Integrity Server supports fibrechannel HBAs at up to 16GigFC, which provides significantly greater storage IO bandwidth than is available with Alpha.

HP VM Integrity platforms

HP VM V6 and later does not support OpenVMS guests. For uses such as dedicated quorum nodes, running an emulated Alpha (with the same version of OpenVMS) on a Linux host as a guest under VMware may be sufficient. For uses such as giving each developer their own personal OpenVMS environment, or running multiple test environments, it may be necessary to develop alternative strategies.

Alpha platforms

In general, those still running on physical Alpha hardware have an urgent need to migrate. Those still running large and complex systems such as AlphaServer GS1280 with EVA storage have a significant challenge.

Migrating a large and complex set of applications from OpenVMS on Alpha (eg: GS1280) to OpenVMS on Integrity (eg: BL890c-i2/i4/i6) with a substantial storage infrastructure can take a significant period of time, allowing for pre-production testing and transition with minimal disruption to service. The choices will largely depend on the scale and complexity of the application software and the extent to which the applications are integrated with the systems and infrastructure.

Fibrechannel HBAs for the Alpha platform are to a maximum of 2Gig bandwidth with standard components. EVA storage is now end-of-life. Expansion of storage infrastructure for Alpha systems is thus another constraint for the Alpha platform.

VAX platforms

Those still running VAX platforms (either physical or emulated) have effectively taken the decision to run self-supported or unsupported systems. Most systems still based on VAX are running well-bounded applications with well-defined workloads. As such, there is little additional urgency for VAX users to migrate.