Migrating from HP-UX 11i v1 Virtual Partitions to a Mixed HP-UX Version Environment

3
As stated above, the update strategy means less downtime for those virtual partitions that are not
moving forward, but involves more steps for those virtual partitions that are being upgraded. It is
even possible that an “update” approach will actually start by re-installing HP-UX 11i v1.
A cold migration strategy requires that the entire nPartition be booted back into nPars mode for the
duration of at least one Ignite-UX session. Once that has succeeded, the user may either stay in nPars
mode and ignite all of the remaining virtual partitions in sequence, or they may return to vPars mode
and igniting all of the virtual partitions in parallel.
These are further discussed in the rest of this document.
Migration Decisions
Starting with a homogeneous set of HP-UX 11i v1 or 11i v2 virtual partitions, wanting to move to
HP-UX 11i v3, the user must answer two fundamental questions:
1. Can the hardware in question support HP-UX 11i v3?
2. Is it feasible/desirable to use Update-UX or must a “cold migration
1
” be used? In other words, is it
desirable to keep the unchanging virtual partitions up as much as possible or is it better to reduce
the total number of update steps?
Figure 1 provides an overview of the necessary decisions to upgrade to either homogeneous or mixed
HP-UX 11i v1, 11i v2, and/or 11i v3 virtual partitions.
1
Cold migration: the process of using Ignite-UX to install a new OS image to a new boot disk, and then importing all of the data/application
disks.