Table 16 Multipathing software by operating system

OS

Multipathing Software

 

 

Windows Server 2012

Windows native MPIO

 

 

Windows Server 2008 R2

Windows native MPIO

 

 

Windows Server 2003

HP MPIO1

 

 

Linux

device-mapper

 

 

1 For Windows Server 2003, HP uses a specific DSM: HPMpioDSMFor3Par_Kit_Ver_1_0_23_1

After the migration preparation phase is complete, the host might need to be shut down and reconfigured to use the native multipathing software DSM for MDM.

NOTE: For MDM, when reconfiguring a host to use the native Microsoft MPIO DSM on Windows 2008 R2 or Windows 2012, use 3PARdataVV as the device hardware ID.

When reconfiguring a host to use the native Linux device-mapper DSM, whitelist the HP 3PAR-specific information in multipath.conf.

For more information about the multipath.conf file, see the HP 3PAR Red Hat Enterprise Linux and Oracle Linux Implementation Guide. This document is available on the following website:

HP Storage Information Library (http://www.hp.com/go/storage/docs)

For MDM, the data transfer migration phase is then started, and the host is brought back online. This process ensures that the host is never multipathing between the source EMC Storage system and the destination HP 3PAR StoreServ Storage system. Even if the native multipathing software DSM is already configured, it is necessary to restart the host after unzoning the source EMC Storage system from the host.

IMPORTANT: If you unzone the host and EMC Storage system but do not reconfigure the host DSM, the host/cluster will experience an outage, because it will not be able to communicate with the destination HP 3PAR StoreServ Storage system.

Network and Fabric Zoning Requirements

Data migration requires the necessary zoning to create paths between the source and destination storage systems and any hosts involved in the migration. The data paths used are shown in Figure 1 (page 33).

Two unique paths must be zoned between the source and destination storage systems. To create two paths, the two controller ports on the source EMC Storage system must be connected to two peer ports on the destination HP 3PAR StoreServ Storage system. See “Zoning the Source EMC Storage to the Destination HP 3PAR StoreServ Storage System” (page 33).

The paths between the host and the source EMC Storage system are unzoned before the migration starts. The timing for this depends on the operating system of the host and the migration type.

During data migration, paths must be zoned between the host and destination HP 3PAR StoreServ Storage system. The time at which these paths are created is determined by the operating system of the host and the migration type.

32 Preparing for Data Migration