The steps shown here are high-level and typical. For details, see the referenced sections of this guide.
Migration 1: Source array 1 to HP 3PAR StoreServ Storage
1. Follow the premigration steps for the source array and the HP 3PAR StoreServ Storage as detailed in“Premigration Steps” (page 36). Premigration steps for an online migration include:
a. Zoning source array 1 to the destination HP 3PAR StoreServ Storage
b. Identifying source array 1 and the destination HP 3PAR StoreServ Storage using the HP 3PAR Online Import Utility
2. Follow the online migration procedure described“Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3” (page 44). Typical steps include:
a. Zoning the Oracle RHEL nodes to the destination HP 3PAR StoreServ Storage.
b. Configuring the RHEL native device-mapper multipath on all nodes.
c. Issuing thecreatemigrationcommand with the–migtype onlineparameter and
using the –allvolumesincgparameter on source array 1. All volumes, including the
CRS, voting disks, and data disks will be presented and exported to the HP 3PAR StoreServ Storage together as one volume set.
d. Making a note of the migration task ID, and issuing theshowmigrationcommand to verify that the data migration task preparation has completed successfully.
e. Issuing theshowmigrationdetailscommand to verify the volumes being migrated.
f. Updating the path configuration on the host by rescanning all HBAs and issuing the
multipath -llcommand to verify the newly discovered paths.
g. Deleting the LUN paths from source array 1 and verifying that themultipath –ll
command shows only the newly discovered or destination HP 3PAR paths.
h. Unzoning the Oracle RAC nodes from source array 1.
i. Starting the migration by using the HP 3PAR Online Import Utilitystartmigration
command
j. Issuing theshowmigrationcommand against the migration task ID (generated by issuing thecreatemigrationcommand) to verify that the data migration task preparation has completed successfully.
3. At this stage, although the CRS, voting and the data disks that were on the source array have been completely migrated to the HP 3PAR StoreServ Storage, and there are data disks present on the source array, the Oracle database and services should continue to be ONLINE and accessible. This can be verified by running the following Oracle based command on the primary RHEL node:
# $GRID_HOME/bin/crs_stat –t
4. Execute the post-migration steps for migration 1 by performing the following (optional) steps:
a. Remove the migration definition when the migration has completed by issuing the
removemigration command against the migration task ID (generated by the
createmigration, above).
b. When all migrations are complete, physically remove source array 1.
c. When all migrations are complete, remove source array 1 from the HP 3PAR Online Import Utility, using theremovesourcecommand.
d. Reconfigure peer ports to host ports on the HP 3PAR StoreServ Storage.
Migration 2: Source array 2 to HP 3PAR StoreServ Storage
5. Follow the premigration steps for the source array and the HP 3PAR StoreServ Storage as detailed in“Premigration Steps” (page 36). Typical premigration steps for an online migration include:
a. Zoning source array 2 to the destination HP 3PAR StoreServ Storage.
b. Identifying source array 2 and the destination HP 3PAR StoreServ Storage using the HP 3PAR Online Import Utility.
6. Follow the online migration procedure described in“Performing Data Migration for Red Hat Linux, Oracle RAC, ESXi 5.5, and HP-UX 11 v3” (page 44). Typical steps include:
a. Zoning the Oracle RHEL nodes to the destination HP 3PAR StoreServ Storage.
b. Configuring the RHEL native device-mapper multipath on all nodes.
c. Issuing thecreatemigrationcommand with the –migtype online parameter with the –allvolumesincgparameter on source array 2. All volumes, including the CRS, voting
disks, and data disks will be presented and exported to the HP 3PAR StoreServ Storage together as one volume set.
NOTE: If a single data disk, rather than multiple data disks, is present on source array 2, the–allvolumesincgparameter should not be issued. The disk should be treated like a single volume as opposed to a consistency group-based volume set.
d. Making a note of the migration task ID, and issuing theshowmigrationcommand to verify that the data migration task preparation has completed successfully.
e. Issuing theshowmigrationdetailscommand to verify the volumes being migrated.
f. Updating the path configuration on the host by rescanning all HBAs and issuing the
multipath -llcommand to verify the newly discovered paths.
g. Deleting the LUN paths from the source array and verifying that themultipath –ll
command only shows the newly or destination 3PAR paths.
h. Unzoning the Oracle RAC nodes from source array 2.
i. Starting the migration by using the HP 3PAR Online Import Utilitystartmigration
command.
j. Issuing theshowmigrationcommand against the migration task ID (generated by issuing thecreatemigrationcommand) to verify that the data migration task preparation has completed successfully.
7. At this point, all the data disks that were on source array 2 have completely migrated to the HP 3PAR StoreServ Storage. The Oracle database and services should continue to be online and accessible. This can be verified by running the following Oracle-based command on the primary RHEL node:
# $GRID_HOME/bin/crs_stat –t
8. Follow post-migration steps for migration 2 (see“Performing Common Migration and Post-migration Tasks” (page 80)) by performing the following optional steps:
a. Remove the migration definition when the migration has completed by issuing the
removemigration command against the migration task ID (generated by issuing the
createmigration command).
b. When all migrations are complete, physically remove source array 2.
c. When all migrations are complete, remove source array 2 from the HP 3PAR Online Import Utility, using the removesource command.
d. Reconfigure peer ports to host ports on the HP 3PAR StoreServ Storage
This completes the Oracle RAC migration from source array 1 and source array 2 to the destination HP 3PAR StoreServ Storage.