Realize new workload migration and consolidation possibilities

14
The example contains the summary vPar configuration output
(vparstatus)
which is useful for sanity checks:
• the verbose output
(vparstatus –v)
verifies that the I/O has been properly configured
• the
vparnet
output makes sure all of the virtual LANs are as expected
• the
vparhwmgmt
output shows how many resources are reserved for use by the VSP.
Provision virtual partitions
Once the VSP is up and the virtual partitions have been created, provision each vPar with an OE, applications, and data.
Given the assumption that most of your vPars will actually be migrated from legacy hardware, decide whether to create
fresh boot disks and attach the old data, or to keep your existing boot images and update them.
Starting with fresh boot images
The recommended method, particularly if you are migrating from a PA-RISC system or an older version of HP-UX, would
be to start with a new LUN and to use Ignite-UX to do a fresh install of HP-UX (this requires an AVIO NIC attached to a LAN
based vswitch or an internal only LAN with a running vPar functioning as an Ignite server). This is the fastest, easiest,
and least error prone method of getting an OS image. It has the added advantage of not carrying forward any outdated
HP or third-party software, such as the old vPars product.
If you choose this approach, be sure that you are installing the March 2012 update for HP-UX 11i v3 or later. The actual
operating environment you use does not matter from the virtualization standpoint, but other considerations, such as
high availability, may apply. See the HP-UX 11i v3 Installation and Update Guide. Once the root disk is installed, it will
be possible to either mount the old data and application disks, or to mount fresh volumes and copy the data.
Migrating disks from legacy servers
Please note that this is not recommended.
While it is possible to update a sufficiently large root disk for HP-UX, in many cases, between file system growth and changes to kernel
tunable parameters, it is often faster and cleaner to start with a new disk.
If you still wish to migrate your boot disk, HP does support creating boot disks on legacy HP Integrity servers and using
them to boot the new virtual partitions. This can be achieved in at least three ways:
1. Create a dynamic root disk (DRD) clone and update the clone to the HP-UX March 2012 release or later
2. Create an Ignite Recovery image and depots with the additional required software
3. Update the boot disk in place and then move it (or if it is on the SAN, remount it)
This section provides a summary of the document “Migrating an Integrity HP-UX 11i v3 instance to new hardware.”
For detailed coverage of this topic, please refer to the full paper which may be found online at hp.com/go/DRD under
“Learn more—White paper: Migrating an Integrity HP-UX 11i v3 instance to new hardware.”
The following table makes some suggestions in this area.
Table 5. Update method selection criteria
Situation Consider using this method
If you are moving the entire system—data as well as
boot disks
Move the boot disk or DRD clone, along with all data. Device files
will be preserved and very little additional setup will be needed.
If you do not have an Ignite-UX server set up already Move the boot disk or a DRD clone.
If you have many boot disks on a given system or hard
partition, thus making it challenging to identify a particular
boot disk
Deploy an Ignite-UX recovery image.
If your root disk is managed by VxVM Deploy an Ignite-UX Recovery image. DRD rehosting does not
support VxVM roots.
If you only use internal boot disks that are not hot-pluggable Deploy an Ignite-UX recovery image.
If you want to move an entire set of vPars Set up the vPars on the VSP, then either move DRD clones or
deploy Ignite-UX recovery images.