HP 3PAR Management Console 4.3.0 Software User's Guide (QL226-96337, December 2012)

DescriptionColumn
The total size (in GiB) of the volumes exported from the source system.Source Total Exported Size
The name of the destination host set.Destination Host Set
The name of the destination domain (if any).Destination Domain
The number of destination hosts.Destination Host
The total size (in GiB) of the volumes exported to the destination system.Destination Total Exported Size
Indicates if the migration is minimally disruptive..Minimally Disruptive Migration
The detail pane provides Summary, Hosts, Paths, and Virtual Volume information for both the
source and destination hosts. The source system must be connected for the source information to
be displayed. For information on the detail pane screens, see “The Host Set Details Summary Tab
(page 104), “The Host Set Details Paths Tab (page 106), “The Host Set Details Hosts Tab (page 105),
and “The Host Set Details Virtual Volumes Tab (page 106).
Admitted/Importing Linked Hosts Screen
The Linked Hosts screen is divided into a list pane and a detail pane.
The list pane provides the following information:
DescriptionColumn
The name of a host set on the source system.Name
The domain (If any) to which the host set belongs.Domain
The number of host ports on the system.Host Ports
The number of exported volumes.Volumes Exported
The total size (in GiB) of the exported volumes.Total Exported Size
The total amount of reserved space in GiB.Total Reserved Size
The persona information for the specified port (e.g. 1–Generic).Persona
Any user-created comments.Comments
The detail pane contains a VLUNs tab and a Virtual Volumes tab. For details see, “VLUN Details
(page 94), “Virtual Volumes Details (page 96).
Available/Imported Volumes Screen
The Available Volumes screen displays the volumes that are visible to the source and destination
storage system but that have not yet been admitted.
The Imported Volumes screen displays the volumes that have been imported to the destination
storage system.
256 Using the Peer Motion Manager