
17
Figure 14. Numerical output for the throughput of the Peer links
When the data migration is finished, the bar graphs in Figure 12 show 100% while the Status column in Figure 13 will
show “Completed.”
In a fifth and final step, cleanup is done on the source and destination systems. The HP 3PAR StoreServ system that was
presented as a host to the EVA P6000 can be removed if no more Online Import migrations between these two systems
will take place. The Peer links on the HP 3PAR StoreServ system can be unzoned and the Peer Connection Type on both
ports reset to Host.
Best practices
The P6000 Command View application managing the Online Import migration should not execute on the Windows host
whose vdisks are under migration. In the case of a minimally disruptive type of migration, the Windows host has to get
shut down precluding access to the P6000 Command View application to start the actual data transfer.
Before starting the Online Import wizard, you need to have the Peer FC links between the source and the destination system
in place and zoned properly. This means you need to have two unused FC ports on HBAs on adjacent controller nodes on
the destination HP 3PAR StoreServ system. If only one or no FC links are present while executing the wizard, an error
message gets displayed upon which you have to cancel the migration wizard, create the proper zoning and restart the
wizard. HP recommends [single initiator – single target] zoning for all SAN zones. This improves performance, security,
and fault isolation and decreases troubleshooting time.
The host definition on the destination HP 3PAR StoreServ system is created automatically at the start of the Online Import
data migration; you do not have to do that manually. The VVs created on HP 3PAR StoreServ carry the same name as the
vdisk on the EVA P6000. Companies that identify volumes in part after the name of the storage system can change the
name of the destination VVs online. The organization of vdisks into folders on the EVA P6000 is not recreated on the
HP 3PAR StoreServ system.
When using Windows Server 2003 on the host, the HP 3PAR MPIO for Microsoft Windows 2003 multipathing driver has to
be installed and configured when the migration wizard pauses showing the “Unzoned” button. The required reboot for it
can be integrated in the shutdown of the Windows system needed for the SAN zoning changes.
In the wizard for Online Import, one needs to supply the TCP port numbers for the HP 3PAR Event and Secure CLI ports.
These are predefined on 5781 and 5783, but may have been changed by the system administrator. HP recommends
verifying with the storage administrator if the port numbers for these functions deviate from the default ones. Also,
Comentarios a estos manuales