Import Volumes - HP 3PAR StoreServ 7200 2-node Manual

2. If the system is using online migration or minimally disruptive migration, select the Host, Host
Set, or Linked Hosts for which you want to migrate virtual volumes to the destination system.
NOTE:
For example: VV1 is exported to Host1, VV2 is exported to Host2 and Host3, and VV3 is
exported to Host1 and Host3. To migrate VV1, you must also migrate VV2 and VV3 because
the hosts they are exported to overlap.
NOTE:
must be exported.
3. If the system is using offline migration, select the virtual volumes to migrate to the destination
system and click Add.
4. Click Next to go to the Import Volumes page (recommended), or click Finish if you want to
check the configuration and run the Import Volumes wizard later. If you click Finish, the peer
volumes are created but do not contain any data until the Import Volumes step or wizard has
been completed. (To run the Import Volumes wizard, see

Import Volumes

1. Select the virtual volumes to be configured during import to <destination system>.
2. Select allocation settings. You can assign Same As Source, Thin, or Full provisioning to the
virtual volumes being imported. The default is Thin.
Same As Source – Each source volume will retain its current provisioning type when
imported. If you are importing virtual copies, this option assigns the parent volume's
provisioning type to each copy. If your list of volumes contains a mix of Thin and fully
provisioned volumes, that mix is retained upon import.
Thin – All source volumes will be migrated as thinly provisioned.
Full – All source volumes will be migrated as fully provisioned.
All virtual volumes exported to overlapping hosts (Linked Hosts) must be exported.
If a volume being exported is a member of a domain, all volumes in that domain
"Importing Volumes" (page
Migrating Data
21).)
19