EMC VMAX 100K, Product Manual

Page: 167 / 200

l
Simple process for migration:
1. Select storage group to migrate.
2. Create the migration session.
3. Discover paths to the host.
4. Cutover storage group to VMAX3 or VMAX All Flash array.
5. Monitor for synchronization to complete.
6. Commit the migration.
l
Allows for inline compression on VMAX All Flash array during migration.
l
Maintains snapshot and disaster recovery relationships on source array, but are
not migrated.
l
Allows for non-disruptive revert to source array.
l
Allows up to 16 concurrent migration sessions.
l
Requires no license since it is part of HYPERMAX OS.
l
Requires no additional hardware in the data path.
The following graphic shows the connections required between the host (single or
cluster) and the source and target array, and the SRDF connection between the two
arrays.
Figure 49 Non-Disruptive Migration zoning
The App host connection to both arrays uses FC, and the SRDF connection between
arrays uses FC – GigE .
It is recommended that migration controls run from a control host and not the
application host. The control host should have visibility to both the source array and
target array.
The following devices and components are not supported with NDM:
l
CKD devices, IBM i devices
l
eNAS data
l
ProtectPoint, FAST.X, and CloudArray relationships and associated data
Data Migration
Non-Disruptive Migration overview 167