HP EVA P6000 Manual do Utilizador Página 4

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 19
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 3
4
Figure 1. Migration options tree diagram for Online Import
An Online Import migration is assisted by a software wizard. The wizard presents a sequence of dialog boxes that lead
the administrator through a series of well-defined steps to complete the Online Import migration task. The starting point
for the wizard is the selection by the administrator of a single vdisk or host; this is called the explicit selection. This
explicit selection can be complemented by the wizard by one or more implicitly selected objects. The implicitly selected
objects arise from rules embedded in the migration software that find relationships between hosts and vdisks. As an
example, when selecting a vdisk that is exported to multiple hosts, the rules will add these other hosts and their presented
vdisks to the list of objects to migrate. When a presented vdisk is chosen, all other vdisks presented to that same host
are implicitly included in the list of objects to migrate. This ensures that all vdisks engaged in a logical volume management
(LVM) structure on the host are included, as the source EVA P6000 does not know about these LVM structures on the host.
If you want to change the selection of the online vdisks for migration, you have to unpresentvdisks, meaning they no
longer perform I/O to a host. One has to accept the combined explicit and implicit list of vdisks before proceeding to the
next step. In an offline migration, vdisks can be selected on an individual basis and no implicit selection takes place.
After the explicit and implicit selection of vdisks, the wizard validates the source and the destination systems and checks
for the presence of dual FC Peer links between them. The list of vdisks defined for migration can be exported to a CSV
file for inspection. The wizard next prompts for the provisioning type (full or thin) and the Common Provisioning Group
(CPG) name for the destination volumes on the HP 3PAR StoreServ system. The default provisioning type on the destination
system is thin. The CPG proposed for the destination VV has characteristics that are identical or close to those of the disk
group for the vdisk. The size for the destination volume does not need to be specified as it will be identical to the source
vdisk. The wizard next creates a new host in P6000 Command View that is in reality the HP 3PAR StoreServ system
connected to the EVA P6000 via the FC Peer links. Subsequently all vdisks set to migrate are exported to this newly
defined host. Finally the wizard executes the admitof these newly exported volumes on the destination system,
thereby creating a so-called Peer volume per vdisk to be migrated. A Peer volume is a structure for a VV inside the
HP 3PAR OS that is related to a vdisk on the EVA P6000 system via the Peer links. Peer volumes are created in RAID0 on
the physical disks of the HP 3PAR StoreServ with the Peer provisioning type and with the same size as the vdisks they
relate to on the EVA P6000. Peer Volumes are visible in the HP 3PAR Management Console. Initially a Peer volume
consumes no space on the HP 3PAR StoreServ system but it will eventually hold the data from the source vdisks and
become a thin or full VV with the correct RAID level after the migration. During the actual migration the data will be
written to the destination system in the selected CPG and with the correct provisioning type. Online Import is thin-
aware: blocks of zeros migrated to the HP 3PAR StoreServ will not be written to disk if the destination volumes are
thin-provisioned.
Just before the migration definition is committed by the administrator in P6000 Command View, its details can be
exported to a CSV file for inspection. After commitment of the migration, the wizard executes some preparatory work
and next enters a pending state. For a minimally disruptive migration on Windows hosts, the required zone/unzone
operation followed by a reboot of the Windows system is executed during this pending state. For online migrations on
non-Windows systems, the required zone changes are also executed at this point but no reboot is required. For offline
Vista de página 3
1 2 3 4 5 6 7 8 9 ... 18 19

Comentários a estes Manuais

Sem comentários