HP EVA P6000 Manual de usuario descargar pdf (Pagina 5)

migrations on Windows and non-Windows systems, no zone changes and no reboots are required. After the required

zone changes, if any, were made, the administrator clicks the button in the wizard to proceed with the actual data

transfer. The vdisks migrating receive a Management Lock which remains after the end of the migration. After the

migration completes, the Online Import setup is removed in a manual way by removing the HP 3PAR StoreServ host

on the EVA P6000 and by removing the Peer links and the zoning for them.

The WWN of destination VV is the 128-bit WW LUN ID of vdisk on EVA. The Vendor ID and the Product ID in the SCSI

Inquiry string for the volume change with the migration from HP and HSVxxx (with xxx a 3 digit number typical for

the controller type of the EVA P6000) on the EVA P6000 to 3PARdata and VV (independent of the model of HP 3PAR

StoreServ) on the HP 3PAR StoreServ respectively. The LUN ID for the destination VV on the HP 3PAR StoreServ is the

same one as for the vdisk on the source EVA P6000.

For Windows Server 2003, the migrated disks will come online on the host automatically. For Windows Server 2008 and

2012, the status of the migrated disks depends on the SAN Policy set in the diskpart utility. If the SAN Policy is set to

Offline, the disks have to be brought online using diskpart or Disk Manager. On non-Windows hosts you need to

rescan the SCSI bus on the host to make the host operating system see the new LUNs.

The granularity by which Online Import moves data is a block of 256 MB. Space for the VVs is allocated across physical

disks on the HP 3PAR StoreServ system based on the CPG details of the destination volumes. Snapshots, snapclones and

mirrorclones of a vdisk on the source system get transferred to the destination system but their relationship to the vdisk

is not maintained. Vdisks in a remote replication configuration with another EVA can be migrated; the replication does

not need to be stopped. During the data migration, all reads by the host from the migrating vdisks are served by the EVA

P6000. Writes by the host go to the HP 3PAR StoreServ VVs if the block for it was already migrated. Writes also always

go to the EVA P6000 vdisks to keep them updated in case the migration halts for some reason.

In the Performance Manager section of HP 3PAR Management Console 4.3, a predefined chart showing the throughput

for the Peer ports was added.

Technical prerequisites

All models of EVA P6000, except the EVA 3000 and 5000, are supported as source systems for an Online Import operation.

HP 3PAR StoreServ 7000 and 10000 models are supported as destinations systems. The list of supported XCS firmware

versions for the EVA P6000 source systems and the minimum versions of HP 3PAR OS and Management Console for the

HP 3PAR StoreServ are available in SPOCK

HP Software Evaluation Portal

. The HP MPIO DSM for EVA P6000, the multipathing software for the EVA

P6000 system, is required on a Windows host. It does not have to be removed from the host during the zone changes for

a minimally disruptive migration. For Windows Server 2008 and 2012, the multipathing software needed for HP 3PAR

StoreServ systems is the native Windows MPIO DSM that was automatically enabled at the time of the installation of

the EVA P6000 DSM. For Windows Server 2003, the HP 3PAR MPIO for Microsoft® Windows multipathing driver has to be

installed before starting the actual migration. This driver can be downloaded from the

SPOCK

Installing the driver requires a reboot of the host. Please consult the Release Notes for it at the HP Software Evaluation

Portal. For non-Windows hosts, consult

for the list of supported multipathing software.

HP 3PAR Online Import requires two FC ports on the destination HP 3PAR StoreServ system configured in the Peer

Connection Mode. These ports have to be configured manually by the administrator before starting the migration

wizard. After becoming a Peer port, the WWN of the FC port changes from xx:xx:00:02:AC:xx:xx:xx to

xx:xx:

The firewall on the Windows system running P6000 Command View and any network-based firewall in the data path to

the destination HP 3PAR StoreServ system must allow traffic over TCP ports 2386, 5781, and 5783. The first port is used

by the Online Import Web service to publish its data in a Web browser. The last two ports are the Event port and the

Secure CLI port on HP 3PAR StoreServ. Note that all three port numbers are configurable and may have been changed

from their default values by the system administrator.

:02:AC:xx:xx:xx (the change is underlined). The changed WWN is the one to be used in the SAN zoning

of the Peer links. The physical FC ports for them have to be on HBAs in adjacent controller nodes (e.g., nodes 2/3 or 7/8);

the one or three other FC ports on the HBAs of an HP 3PAR StoreServ 7000 and 10000 can be used for host connectivity.

Exactly two Peer links are supported to the host ports of the EVA P6000. The Peer links run over redundant SAN switches,

direct FC connect is not supported.

hp.com/go/spock

https://h20575.www2.hp.com/evalportal/displayProductsList.do?prdcenter=TS_3PAR

1 2 3 4 5 6 7 8 9 10 ... 18 19

Comentarios a estos manuales

Sin comentarios

HP EVA P6000 Manual de usuario Pagina 5

Comentarios a estos manuales

Relacionado con productos y manuales para Barebones Pc / Estación De Trabajo HP EVA P6000