G Data migration best practices
This appendix provides end-to-end “best practices” for using the HP StorageWorks MPX200 data
migration service. The MPX200 data migration service migrates the data at block level. When data
migration is successful, the application is able to access the same data after the data is migrated to
a new logical unit number (LUN). Proper planning for data migration reduces downtime and creates
first-pass success.
Overview
In a typical storage area network (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 following:
•
Which applications and servers (or cluster) are affected?
•
How is application data related to physical storage?
•
How does the server access old and new physical storage?
A single blade of the MPX200 can deliver a migration rate of up to 4TB/hr. Following the suggestions
outlined in this guide may allow you to perform most migration jobs using simple offline migration
while meeting application downtime requirements, thus removing the complexity of performing online
data migration using other data migration tools.
Terminology
This appendix uses the following terms:
•
Mount point
—A node or a directory where application data is stored.
•
Volume
—A single, logical presentation of one or more physical disks.
•
Physical disk
—The raw disk device discovered and configured in the operating system. The object
represented in the operating system is usually associated to a LUN on a storage array.
•
Multi-pathing software
—The LUN may be accessed through multiple ports on a storage array.
Each port of a storage array may be accessed through multiple ports (adapters) in the server.
Multi-pathing software in the host manages the multiple paths to a LUN.
Relationship between application data and physical storage
Successful data migration requires that you understand the relationship between the application data
and the physical device (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. For example:
MPX200 Multifunction Router
369
Summary of Contents for Storageworks 8100 - enterprise virtual array
Page 20: ...20 ...
Page 30: ...MPX200 Multifunction Router overview 30 ...
Page 47: ...Figure 27 iSCSI controller options Remove controller MPX200 Multifunction Router 47 ...
Page 48: ...Managing the MPX200 using HP Command View EVA 48 ...
Page 59: ...Figure 32 Virtual disk properties Figure 33 Host details MPX200 Multifunction Router 59 ...
Page 112: ...MPX200 iSCSI configuration rules and guidelines 112 ...
Page 219: ...Load Balancing Enabled Array License Not Applied MPX200 Multifunction Router 219 ...
Page 248: ...Offline Data Migration 248 ...
Page 258: ...Diagnostics and troubleshooting 258 ...
Page 306: ...Command referencecommand reference 306 ...
Page 330: ... Blade number 1 or 2 Simple Network Management Protocol setup 330 ...
Page 368: ...Saving and restoring the MPX200 configuration 368 ...
Page 402: ...Data migration best practices 402 ...
Page 408: ...408 ...