To perform online data migration using RHEL 5.x, RHEL 6.x, or Oracle RAC, follow these steps.
NOTE: Before migrating a SAN-based Oracle RAC cluster using the HP 3PAR Online Import Utility, it is critical to understand whether and how the Oracle RAC cluster registry (CRS), voting disks, and data disks are distributed across the source arrays, and to plan migrations accordingly. Since the HP 3PAR Online Import Utility is currently designed to execute a migration exclusively from one source array at a time, multiple migrations must be executed serially in order to transfer all the Oracle-based disks from multiple source arrays to a single destination HP 3PAR StoreServ Storage. This use-case scenario is described in detail in“Appendix E: Use Case: Data Migration for an Oracle RAC Cluster” (page 112).
At the time of this publication, the coexistence or distribution of Oracle RAC disks is supported across the HP 3PAR StoreServ Storage and HDS Storage arrays listed in HP SPOCK:
HP SPOCK(http://www.hp.com/storage/spock)
1. Zone the host to the destination HP 3PAR StoreServ Storage system to establish communication.
2. Configure the native device-mapper multipath on the host.
In a cluster environment, update the multipath.conffile on each of the cluster nodes.
NOTE: For Oracle RAC, multipath should be configured in accordance with Oracle recommendations.
Edit the/etc/multipath.conffile to map the device WWNs to a persistent device alias. This alias will be used by the ASMlib to label ASM disks for the Oracle RAC application. The
/etc/multipath.conffiles should be edited identically on each of the cluster nodes. For example:
multipath { wwid 36006016087202e00029a62ca76d3e411 alias <DEVICE_ALIAS>}
The value foralias must match the label used by the native OS multipath software for that device.
NOTE: For ESXi 5.5, set the multipath load balance policy to round-robinfor all the devices on all ESX cluster nodes.
To verify newly discovered paths using ESXi 5.5, issue theesxcfg-mpath -bcommand on the ESX node, or use the vCenter console.
For HP-UX 11i v3, issue theioscan -m luncommand to verify newly discovered paths.
Example 28 Rescanning HBAs and listing the updated multipath mapping for RHEL 5.x and RHEL 6.x # ls /sys/class/fc_host host4 host5 # echo "1" > /sys/class/fc_host/host4/issue_lip # echo "1" > /sys/class/fc_host/host5/issue_lip # echo "- - -" > /sys/class/scsi_host/host4/scan # echo "- - -" > /sys/class/scsi_host/host5/scan # multipath -ll
mpath2 (360060e80045be50000005be500001249) dm-3 HITACHI,OPEN-8 [size=6.8G][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active]
\_ 4:0:0:1 sdb 8:16 [active][ready] \_ 5:0:1:1 sdh 8:112 [active][ready]
mpath1 (360060e80045be50000005be500001248) dm-2 HITACHI,OPEN-8 [size=6.8G][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active]
\_ 4:0:0:0 sda 8:0 [active][ready] \_ 5:0:1:0 sdg 8:96 [active][ready]
3. RHEL 5.x or RHEL 6.x: Using the HP 3PAR Online Import Utility, issue thecreatemigration
command with the-migtype onlineoption.
Optionally, migrations with consistency groups are also supported, using the
-allvolumesincg or-cgvolmap parameters.
NOTE: For Oracle RAC, you must issue thecreatemigrationcommand using the
-allvolumesincg parameter.
Example 29 Usingcreatemigrationwith-migtype onlinefor RHEL 5.x or RHEL 6.x # createmigration -sourceuid xxxxx -srchost "X7DBU-02-IG" -destcpg testcpg -destprov full -migtype online —persona “RHEL_5_6”
# SUCCESS: Migration job submitted successfully. Please check status/details using showmigration command. Migration id: 1411673030253
For Oracle RAC: Using the HP 3PAR Online Import Utility, issue thecreatemigration
command with the-migtype onlineand-allvolumesincgparameters.
Example 30 Usingcreatemigrationwith -migtype onlinefor Oracle RAC
# createmigration -sourceuid xxxxx -srchost "x8dtuf-01" -allvolumesincg -migtype online -destcpg testcpg -destprov full -persona "RHEL_5_6"
Example 31 Usingcreatemigrationwith-migtype onlinefor HP-UX 11i v3 (Standalone)
# createmigration -sourceuid xxxxx -srchost "x8dtuf-01" -allvolumesincg -migtype online -destcpg testcpg -destprov full -persona "HPUX_11_v3"
Example 32 Usingcreatemigrationwith-migtype onlinefor ESXi 5.5
# createmigration -sourceuid xxxxx -srchost "x8dtuf-01" -allvolumesincg -migtype online -destcpg testcpg -destprov full -persona "ESX_4_5"
This step admits LUNs presented to the HDS Storage system and exports them to the HP 3PAR host created on the HDS Storage system.
NOTE: Thecreatemigrationcommand may take several minutes to complete.
TIP: Make a note of the migration ID, as it will be used in commands to track migration progress.
4. Issue theshowmigrationcommand to verify that the data migration task preparation has completed successfully. This may take some time. Upon successful creation of the
createmigrationtask, theSTATUScolumn in theshowmigrationcommand output will indicatepreparationcomplete(100%). When this status is indicated, continue to the next
step.
Example 33 Issuing theshowmigrationcommand # showmigration
MIGRATIONID TYPE SOURCE_NAME DESTINATION_NAME START_TIME
END_TIME STATUS(PROGRESS)(MESSAGE)
1411673030253 online USP_V.48748 3par_7200_DCA_01 Thu Sep 25 15: 23:50 EDT 2014
-NA- preparationcomplete(100%)(-NA-)
5. Using the HP 3PAR Management Console, verify that the host whose LUNs are under migration has paths to as many HP 3PAR controller nodes as are zoned in the SAN (seeFigure 10 (page 54)). This number of paths is listed in theNode ID(s)column. The path details are in theHost Detailspane.
Figure 10 HP 3PAR Management Console—Host Details
6. Update path configuration on the host by rescanning all HBAs and issuing themultipath -llcommand to verify the newly discovered paths. Multipath now recognizes extra paths to the HP 3PAR StoreServ Storage, but all paths are still managed as source array devices.
NOTE: With ESXi 5.5 and HP-UX 11i v3, HBA rescanning verifies new paths on the destination storage system.
Example 34 Rescanning HBAs and listing the updated multipath mapping with RHEL 5.x # # ls /sys/class/fc_host host4 host5 # echo "1" > /sys/class/fc_host/host4/issue_lip # echo "1" > /sys/class/fc_host/host5/issue_lip # echo "- - -" > /sys/class/scsi_host/host4/scan # echo "- - -" > /sys/class/scsi_host/host5/scan #multipath -ll
mpath2 (360060e80045be50000005be500001249) dm-3 HITACHI,OPEN-8 [size=6.8G][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:1 sdb 8:16 [active][ready] \_ 4:0:4:1 sdf 8:80 [active][ready] \_ 5:0:1:1 sdh 8:112 [active][ready] \_ 5:0:2:1 sdj 8:144 [active][ready]
mpath1 (360060e80045be50000005be500001248) dm-2 HITACHI,OPEN-8 [size=6.8G][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:0 sda 8:0 [active][ready] \_ 4:0:4:0 sde 8:64 [active][ready] \_ 5:0:1:0 sdg 8:96 [active][ready] \_ 5:0:2:0 sdi 8:128 [active][ready]
7. Delete the migrating LUN paths pertaining to the source array. For details about identifying and deleting LUN paths, see“Appendix B: Identifying and Deleting Source Array LUN Paths” (page 105).
8. Unzone the host from the source array, if applicable.
CAUTION: With ESXi 5.5 and HP-UX 11i v3, before starting the migration, make sure that the source storage system has been removed and is no longer present on the host. If the source storage system has not been removed from the host, I/O loss can occur.
Example 35 Output after unzoning the host from the source array with RHEL 5.x #multipath -ll mpath2(360060e80045be50000005be500001249) dm-3 3PARdata,VV [size=6.8G][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:1 sdb 8:16 [active][ready] \_ 5:0:1:1 sdh 8:112 [active][ready] mpath1(360060e80045be50000005be500001248) dm-2 3PARdata,VV [size=6.8G][features=1 queue_if_no_path][hwhandler=0][rw] \_ round-robin 0 [prio=1][active] \_ 4:0:0:0 sda 8:0 [active][ready] \_ 5:0:1:0 sdg 8:96 [active][ready]
9. Start the migration by using the HP 3PAR Online Import Utilitystartmigrationcommand.
Example 36 Starting migration by usingstartmigration # startmigration -migrationid 1411673030253 # SUCCESS: Data transfer started successfully.
NOTE: The-migrationid(in the example above,1411673030253) will have been assigned by thecreatemigrationcommand.
TIP: Theshowmigrationcommand status will indicatesuccesswhen all LDEVs have been migrated successfully.
Example 37showmigrationcommand showing successful migration # showmigration -migrationid 1411673030253
MIGRATION_ID TYPE SOURCE_NAME DESTINATION_NAME
START_TIME END_TIME STATUS(PROGRESS)(MESSAGE)
1411673030253 online USP_V.48748 3par_7200_DCB_01
Fri Apr 04 16:38:24 EDT 2014 -NA- success(-NA-)(-NA-)