Migrating vPar Systems to Integrity VM

13 of 13

Summary

The steps provided here will enable you to transition an Integrity system from running vPars to hosting

Integrity Virtual Machines. The steps necessary to do the reverse transition are very similar in general

and identical for maintaining disk and volume configurations across the transition.

When you complete the transition from vPars to VMs as outlined above, you will not be sharing

hardware very efficiently. However, the Integrity VM system will now be in a position to begin

sharing hardware in two important ways.

First, you may be able to share physical NICs by combining VMs that use the same subnet and

gateways onto a single virtual switch (associated with a physical NIC on that same subnet and

gateway configuration of course).

Second, and more generally, the physical Integrity server is now ready to accommodate more

workloads due to its sharing of CPU, network, and storage devices. New or existing, unused storage

space on the VM Host may be now used to host additional VMs and those VMs can be configured to

share that storage through the use of files or logical volumes for their virtual disks. These VMs can

also share existing (as well as new) physical NICs connected to the desired subnet.

For more information

The following references, available online from docs.hp.com, provide useful material on Integrity VM,

Virtual Partitions, and logical volume management. Part numbers are provided wherever possible,

but always use the latest version of the document or that related to your particular configuration.

• HP Integrity Virtual Machines Installation, Configuration, and Administration manual (HP Part

Number T2767-90004)

• Installing and Managing HP-UX Virtual Partitions (vPars) (HP Part Number T1335-90018)

• Managing Systems and Workgroups, A Guide for HP-UX System Administrators (HP Part Number

B2355-9095)

see section “Moving Disks Across Systems”

• Configuring HP-UX For Peripherals (HP Part Number B2355-90675)

see section “Configuring into your System an LVM Disk Already Containing Data” and chapter 4

“Configuring Disk Drives, Disk Arrays, and CD-ROM Drives”

• VERITAS Volume Manager 3.5 Administrator’s Guide (HP Part Number 5991-0603)

see section “Moving Disk Groups Between Systems”

• VERITAS Volume Manager 3.5 Migration Guide (HP Part Number 5991-0609)

see section “Comparison of LVM and VxVM Tasks”

Packard Development Company, L.P. The information

contained herein is subject to change without notice. The only warranties for

HP products and services are set forth in the express warranty statements

accompanying such products and services. Nothing herein should be construed

as constituting an additional warranty. HP shall not be liable for technical or

editorial errors or omissions contained herein.

Itanium is a trademark or registered trademark of Intel Corporation in the U.S.

and other countries and is used under license.

VERITAS, VERITAS Volume Manager, and VxVM are trademarks or registered

trademarks of VERITAS Operating Corporation in the U.S. and other countries

and are used under license.

Version 1.0, 02/2006