Product data

116 PowerVM Migration from Physical to Virtual Storage
hdisk LUN # Ownership User Label
hdisk4 1 B (preferred) PW9405-17-1
hdisk5 2 B (preferred) PW9405-17-2
The previous output describes where the hard disks that are SAN
connected are sourced from (in this case the Storage Subsystem
ITSO_DS4800) and how the disks are named in the storage array
(PW9405-17-1 and PW9405-17-2, respectively). If you are using EMC
storage then the powermt display command may be used or the lspath
command for other MPIO-capable storage to display details.
4. Gather information for any data volume groups that are going to migrate. This
includes:
a. The physical volumes contained in the volume group. Use the lsvg
command with the -p flag:
# lsvg datasrcvg -p
datasrcvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE
DISTRIBUTION
hdisk5 active 119 102 24..07..23..24..24
#
b. The logical volumes in the data volume groups. Use the lsvg command
with the -l flag:
# lsvg datasrcvg -l
datasrcvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT
POINT
loglv00 jfs2log 1 1 1 open/syncd N/A
fslv00 jfs2 16 16 1 open/syncd /data
From the previous output you have determined that the datasrcvg has a single
jfs2 file system that is mounted at the /data mount point. To assist in the
context of performing migration tests, we wrote a signature to the /data
directory using the AIX touch command and verified that the file was created
using the AIX ls command:
# ls /data
lost+found
# touch /data/migrate_FC_to_VFC.sig
# ls /data
lost+found migrate_FC_to_VFC.sig
#
5. The last piece of disk identification information required is the unique
identification string for each disk that will migrate. Use the AIX lsattr
command to obtain this information. For further information about disk