HP MPX200 Data Migration Planning Guide

Table 4 Physical device information
LUN ID
Physical disk or raw device
nodeVolumeMount point (if any)ApplicationServer
Step 4: List and create LUN ID mappings
Create a list of LUNs containing the size and mapping information showing how they are seen by
the server and the MPX200, as requested in Table 5 (page 9). Although a specific LUN can be
presented at a different LUN ID to a server other than an MPX200, HP recommends that you use
the same LUN ID, if possible.
This practice is helpful while creating new LUNs on a destination array, and while presenting
source and destination LUNs to the MPX200 data migration service. For operating systems other
than Windows, HP also recommends that source and destination LUNs be the same size.
This step uses the LUN remapping feature of mpx Manager to map LUNs to the server through
MPX200. With LUN remapping, you can present LUNs to the MPX200 at any available ID,
regardless of the IDs presented to the server. However, if your environment allows, it is simpler to
present the same LUNs to the server through the MPX200 as presented by the array.
Table 5 LUN ID mappings
CapacityDestination LUNSource LUNCapacityVolume ID,
source
Source
LUN seen
Server
Presented
to server
as LUN ID
Presented
to
MPX200
as LUN ID
Remapped
and
presented
to host
Presented
to
MPX200
as LUN ID
array (if
applicable)
by the
server as
LUN
through
MPX200
at LUN ID
Complete the information for the source and destination LUNs during the data migration planning
phase.
Determine the unique volume ID for the source storage array to make it easier to refer to the LUN.
On large arrays, sometimes different LUNs with the same LUN ID are presented to different hosts.
Step 5: List and create FC zoning
For an FC SAN, create a list of fabric zones. The list should contain the WWPN associated with
servers, storage arrays (source and destination), and the MPX200, as shown in Table 6 (page
10). Before migration, zone in the destination array only with the MPX200. After migration, zone
in the destination array with the servers, as shown in Table 7 (page 10).
Step 4: List and create LUN ID mappings 9