HP EVA-to-3PAR Online Import Migration Guide

13. If you are migrating HP-UX 11i V2 standalone hosts or Serviceguard cluster and if non-shared
volume groups are present:
a. Note down the new pv_paths to the physical volumes in the volume group from the output
of the LUN rescan done in the previous step.
b. Add the new paths to the volume group using vgextend vg_name pv_path
c. If you are booting from a disk that is being migrated, ensure to add new 3PAR paths to
the boot disk or update the setboot path definitions.
NOTE: The maximum number of VG path is 8. You might have to reduce the number of
paths to the existing EVA array to add new paths to the 3PAR array. Additional 3PAR paths
may be added after step 16.
14. If you are migrating Serviceguard cluster and if shared volume groups are present perform
the following steps:
a. Identify the shared volume group on which a configuration change is required.
For example, vg_shared
b. Identify one node of the cluster which is running an application using the shared volume
group.
For example, node1
The applications using the volume group, vg_shared, on this node will remain unaffected
during the procedure. Stop the applications using the shared volume group on all the
other cluster nodes thus scaling down the cluster application to the single cluster node
node1.
c. Deactivate the shared volume group on all other nodes of the cluster, except node1, using
the "-a n" option to the vgchange command.
vgchange -a n vg_shared
Ensure the volume group, vg_shared, is now active only on a single cluster node, node1
by using the vgdisplay command on all cluster nodes. The Status must display
available on a single node only.
d. Change the activation mode to exclusive on node1 vgchange -a e -x vg_shared
e. On node1, note down the new pv_paths to the physical volumes already in the volume
group from the output of the LUN rescan. Now add all the new paths to the volume group
using vgextend vg_shared pv_path
f. Export the changes to other cluster nodes:
1. From node1, export the mapfile for the vg_shared command
vgexport -s -p -m /tmp/vg_shared.map vg_shared.
2. Copy the mapfile /tmp/vg_shared to all the other nodes of the cluster.
3. On the other cluster nodes, export vg_shared and re-import it using the new map
file.
For example, ls -l /dev/vg_shared/group
crw-rw-rw- 1 root sys 64 0x050000 Nov 16 15:27 /dev/vg_shared/
group
4. Note down the minor number, that is, 0x050000 from the example.
vgexport vg_shared
mkdir /dev/vg_shared
mknod /dev/vg_shared/group c 64 0x050000 (minor number must
match with above number.)
vgimport -m /tmp/vg_shared.map -s vg_shared
g. Change the activation mode back to shared on all the cluster nodes.
Migrating an HP-UX host 27