n
Multiple masking views on the storage group using the same initiator group are
only allowed if port groups on the target array already exist for each masking
view, and the ports in the port groups are selected.
n
Storage groups must be parent or standalone storage groups. A child storage
group with a masking view on the child storage group is not supported.
n
Gatekeeper devices in the storage group are not migrated to the target array.
n
Devices must not be masked or mapped as FCoE ports, iSCSI ports, or non-
ACLX enabled ports.
n
Devices cannot be in storage groups that are masked.
l
For objects that may already exist on the target array, the following restrictions
apply:
n
The names of the storage groups (parent and/or children) to be migrated must
not exist on the target array.
n
The names of masking views to be migrated must not exist on the target array.
n
The names of the initiator groups to be migrated may exist on the target array.
However, the initiator groups on the target array must have the exact same
initiators, child groups and port flags as the initiator groups to be migrated.
Port flags that are not supported on the VMAX3 arrays are ignored. If an IG on
the target array has the same WWNs used on the source array, then the IG
name on the target array must be exactly the same as the IG name on the
source array. If the initiators are already in an IG on the target array, the
operation will be blocked unless the IG on the target array has the same name
as the source array, and the IG must have the exact same, initiators, child
groups and port flags as the source array. In addition, the consistent lun flag
setting on the source array IG must also match the IG flag setting on the target
array.
n
The names of the port groups to be migrated may exist on the target array,
provided that the groups on the target array have the initiators logged into at
least one port in the port group.
l
The status of the target array must be as follows:
n
If a target-side Storage Resource Pool (SRP) is specified for the migration that
SRP must exist on the target array.
n
The SRP to be used for target-side storage must have enough free capacity to
support the migration.
n
If compression is enabled for the storage group to be migrated, it must be
supported by the SRP on the target array.
n
The target side must be able to support the additional devices required to
receive the source-side data.
n
All initiators provisioned to an application on the source array must also be
logged into ports on the target array.
l
Only FBA devices are supported (Celerra and D910 are not supported) and the
following restrictions apply:
n
Cannot have user geometry set, non-birth identity, or the BCV attribute.
n
Cannot be encapsulated, a Data Domain device, or a striped meta device with
different size members.
Data Migration
Non-Disruptive Migration overview
169
Summary of Contents for VMAX 100K
Page 1: ...EMC VMAX3 Family Product Guide VMAX 100K VMAX 200K VMAX 400K with HYPERMAX OS REVISION 6 5 ...
Page 20: ...Preface 20 Product Guide VMAX 100K VMAX 200K VMAX 400K with HYPERMAX OS ...
Page 46: ...VMAX3 with HYPERMAX OS 46 Product Guide VMAX 100K VMAX 200K VMAX 400K with HYPERMAX OS ...
Page 72: ...Open systems features 72 Product Guide VMAX 100K VMAX 200K VMAX 400K with HYPERMAX OS ...
Page 82: ...Provisioning 82 Product Guide VMAX 100K VMAX 200K VMAX 400K with HYPERMAX OS ...
Page 158: ...Remote replication solutions 158 Product Guide VMAX 100K VMAX 200K VMAX 400K with HYPERMAX OS ...
Page 186: ...Mainframe Error Reporting 186 Product Guide VMAX 100K VMAX 200K VMAX 400K with HYPERMAX OS ...
Page 200: ...Licensing 200 Product Guide VMAX 100K VMAX 200K VMAX 400K with HYPERMAX OS ...
