most cases, the OS automatically discovers the relationship between the volume and the migrated
LUN(s) on a destination storage array.
Table 39 Physical device information
LUN IDPhysical Disk or
Raw Device Node
VolumeMount Point
nl
(if any)
ApplicationServer
Step 4. List and create LUN ID mappings
Create a list of LUNs containing the size and mapping information that shows how the LUNs are seen
by the server and the MPX200, as shown in Table 40. Although a specific LUN may be presented at
a different LUN ID to a server other than to MPX200, it is recommended that you use the same LUN
ID, if possible. This will be helpful while creating new LUNs on a destination array and while presenting
source and destination LUNs to MPX200 data migration service. For operating systems other than
Windows, HP highly recommends that source and destination LUNs are the same size.
NOTE:
• You should complete the information for the source and destination LUN during the planning
phase of data migration.
• Determine the unique volume ID for the source storage array to make it easier to refer to the LUN,
because on large arrays, different LUNs with the same LUN ID are sometimes presented to different
hosts.
• Each MPX200 has up to four virtual port groups (VP Groups), each of which can be seen by an
array as a different host entity. You can expose the different LUNs as the same LUN ID on each
VP Group, enabling you to maintain the same LUN ID exposure to both the host and the MPX200.
Table 40 LUN ID mappings
CapacityDestina-
tion LUN
Presen-
ted to
Server
as LUN
ID
Destination LUN
Presented to
MPX200 as LUN ID
and MPX200 VP
Group
Source LUN Presen-
ted to MPX200 as
LUN ID and
MPX200 VP Group
CapacityVolume
ID,
Source
Array
Source
LUN
Seen by
the Serv-
er as
LUN ID
Server
LUN IDVP
group
LUN IDVP
group
Data migration best practices372
To Next Page
Loading...
Need help?
General