HP-UX 11i v3 Persistent DSF Migration Guide

This section discusses HP-UX subsystems that may be configured in a user’s system. A system can be configured

with LVM, VxVM, or whole disk (neither LVM nor VxVM).

o LVM is configured

The LVM configuration is maintained in the binary file /etc/lvmtab and optionally the ASCII file

/etc/lvmpvg, which may contain legacy DSFs, persistent DSFs, or a mix of both. LVM provides the

/usr/contrib/bin/vgdsf tool for migrating the LVM configuration from legacy DSFs to persistent

DSFs. For activated volume groups, the vgdisplay command with the –v option displays which DSFs

a volume group is using. However users must migrate all LVM volume groups, not only the activated

ones. For more information, see the LVM Migration from legacy to agile naming model HP-UX 11i v3

white paper at http://docs.hp.com/en/hpux11iv3.html#LVM%20Volume%20Manager

for LVM

migration details.

Note: Be sure to migrate the /etc/lvmpvg ASCII file using the vgdsf tool and not using the iofind

tool as vgdsf takes other actions required for proper LVM migration.

For LVM boot disk, run the lvlnboot command with the –v option to see if LVM is using legacy DSFs

or persistent DSFs for boot, swap, or dump. If LVM is using legacy DSFs for boot, swap, or dump, users

must

 run the /usr/contrib/bin/vgdsf –c vg_name command to migrate the LVM

configuration for the root volume group vg_name from legacy DSFs to persistent DSFs

 run the lvlnboot –R /dev/vg_name to migrate the LVM on-disk boot information to match

/etc/lvmtab.

See the LVM documentation in the Read before Migrating” to HP-UX 11i v3

section for more details.

o VxVM is configured

Agile view is not supported with VxVM 4.1. Therefore users cannot migrate to persistent DSFs if they

use VxVM 4.1. VxVM 5.0 provides support for the agile view.

o Whole disk configuration is used (neither LVM nor VxVM)

For whole disk configurations, typically a single boot disk has been configured for boot, swap, and

dump using either a legacy DSF or a persistent DSF. If a system is updated from HP-UX 11i v2 to HP-UX

11i v3, the update process migrates the legacy configuration to the agile view.

Users can verify the configuration by using the bdf command to check the file system configuration, the

setboot command to check the boot path, the crashconf command to check the dump device, and

the swapinfo command to check the swap device. The setboot and crashconf commands

automatically convert the configured DSFs into agile view. If swapinfo displays any configured

legacy DSFs, use the swapon command to perform the migration.

The /etc/fstab and /stand/system files contain information about the file system and other

system configuration. Swap and dump devices may be configured in /etc/fstab and

/stand/system.

If these two files contain legacy DSFs or legacy hardware paths, migrate them to

persistent DSFs or lunpath hardware paths either manually or by using the iofind tool described

below. Make sure to backup the files first before making any changes. Note that modifications to the

/etc/fstab and /stand/system files may require a reboot to take effect. For more information,

see bdf(1M), crashconf(1M), setboot(1M), swapinfo(1M), swapon(1M), and fstab(4).