HP MPX200 Data Migration Planning Guide

1 Getting started
Related materials
For reference information and procedures for using the DMS features of the HP utility for the MPX200
Multifunction Router, see the following:
• HP MPX200 Multifunction Router Data Migration User Guide
• HP mpx Manager help system
Overview
In a typical SAN, the storage array serves one or more servers. When data is migrated from a
source LUN to a destination LUN on a different storage array or the same storage array, it is
important to understand:
• The applications and servers (or cluster) that are affected
• How application data relates to physical storage
• How the server accesses old and new physical storage
An MPX200 single chassis can deliver up to 4 TB/hour migration rate. The procedures outlined
in this guide enable completion of most migration projects using simple offline migration, while
meeting application downtime requirements. Simple offline migration avoids the complexity of
online data migration.
Relationship between application data and physical storage
Successful data migration requires an understanding of the relationship between the application
data and the physical device (or LUN).
NOTE: The UNIX operating system in this discussion refers to HP-UX, Linux, Solaris, and AIX.
Typically, the application accesses the data using a mount point as shown in Table 1 (page 4).
Table 1 Application mount points
Mount pointApplication
F:\SharepointWindows SharePoint
/home/oracleOracle application running on an HP-UX host
/data/webinfoApache Web Server application on a Linux host
Typically, the administrator creates a mount point on a volume. On Windows operating systems,
volume refers to a drive letter (for example, D:\ or F:\). On UNIX operating systems, a mount
point can be either a volume managed by a logical volume manager (Veritas or native), or raw
device (for example, /dev/rdsk/c0t1d4).
You can create a volume on a single physical disk or on multiple physical disks. For example, in
Windows, drive letter F:\ a volume might span multiple physical disks (Disk2, Disk3, and so on).
On UNIX, a Veritas Volume Manager might have a volume /dev/vg-1/vol1 created on three
physical disks: /dev/rdsk/c0t1d2, /dev/rdsk/c0t1d3, and /dev/rdsk/c0t1d4.
The physical disk or raw device is associated with a LUN. For example, in Windows, Disk2 is
LUN 5 on a storage array and Disk3 is LUN 6 on a storage array. In UNIX, /dev/rdsk/c0t1d2
is LUN 2 on a storage array and /dev/rdsk/c0t1d3 is LUN 3 on a storage array.
4 Getting started