HP MPX200 Data Migration Planning Guide

2 Inventory checklists
Data migration checklists help the system administrator take inventory of all items affected by a
data migration project. This chapter provides a list of servers and applications, and defines
relationships of application data to LUNs and shows how LUNs are accessed through the server.
The migration checklists also help to identify possible changes required on the server after migration.
The tables in this chapter help you take proper inventory to plan data migration.
Step 1: Source and destination storage arrays
Retrieve the information for Table 2 (page 8) from the storage administrator in the data center.
Table 2 Storage array information
WWPN
2
(FC)
Number of
controllers
Array
management
software
1
Firmware
version
Source or
destinationStorage array
1
The storage array specific software used in data migration to present the source LUNs to the MPX200 and to create
destination LUNs to be presented to the MPX200 and to the server. The array management software also provides the
controller and WWPN information for the storage array ports.
2
WWPN of the FC array; used in performing zoning in FC switch firmware.
Step 2: List the servers affected by the data migration project
The information requested in Table 3 (page 8) can be retrieved by the server administrator.
Installation of new multipathing software might be required when changing the class of an array
or changing the array vendor, An upgrade to existing software might also be required for the
same class of array. You must identify the user ID and password for each server.
Table 3 Server information
Multipathing software for
destination array
Logical volume
manager (if any)
Multipathing
software for
source arrayIP address
Operating
system and
versionServer
Step 3: Applications, mount points, and paths to the physical devices
The server administrator can retrieve applications, mount points, and paths to the physical device
requested in Table 4 (page 9). For Windows, or any UNIX operating system with an LVM, the
LUN ID association with the server or application and volume is important. In most cases, the
operating system automatically discovers the relationship between the volume and the migrated
LUNs on a destination storage array.
8 Inventory checklists