Product specifications

2–Inventory Checklists
Step 3: List the Applications, Mount Points, and Paths to the Physical Devices
ISR654605-00 A 2-3
Step 3: List the Applications, Mount Points, and
Paths to the Physical Devices
The applications, mount points, and paths to the physical device requested in
Table 2-3 can be retrieved by the server administrator. For Windows OS or any
UNIX OS with a logical volume manager (LVM), the LUN ID association with the
server or application and volume is the most important because, in most cases,
the OS will automatically discover the relationship between the volume and the
migrated LUN(s) on a destination storage array.
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 2-4.
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 very 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, it is highly recommended that source and
destination LUNs are the same size.
Table 2-3. Physical Device Information
Server Application
Mount Point
(if any)
Volume
Physical Disk or
Raw Device
Node
LUN ID
Table 2-4. LUN ID Mappings
Server
Source
LUN Seen
by the
Server as
LUN ID
Volume
ID,
Source
Array
Capacity
Source LUN
Presented to
MPX200 as LUN
ID and MPX200
VP Group
Destination LUN
Presented to
MPX200 as LUN
ID and MPX200
VP Group
Destination
LUN
Presented
to Server
as LUN ID
Capacity
VP
Group
LUN ID
VP
Group
LUN ID