Introduction
About this document
This document provides information that you can use to configure and manage VNX imports (migrations) on the Unity system. Along with relevant concepts and instructions to configure VNX imports using the Unisphere GUI, this document also includes information about the CLI commands that are associated with configuring VNX imports.

Additional resources
Where to get help
Support, product, and licensing information can be obtained as follows:
For product and feature documentation or release notes, go to Unity Technical Documentation at: www.emc.com/en-us/documentation/unity-family.htm.
For information about products, software updates, licensing, and service, go to Online Support (registration required) at: https://Support.EMC.com. After logging in, locate the appropriate Support by Product page.
For technical support and service requests, go to Online Support at: https://Support.EMC.com. After logging in, locate Create a service request. To open a service request, you must have a valid support agreement. Contact your Sales Representative for details about obtaining a valid support agreement or to answer any questions about your account.
Special notice conventions used in this document





About import
The Import feature allows you to migrate a VDM, or a LUN or a consistency group (CG) of LUNs, with its configuration and data from an existing source VNX storage system to a target Unity storage system. This feature provides a built-in capability for NFS-only VDM imports with minimal or no disruption to clients. It also provides a built-in capability for CIFS-only VDM and block-based imports. However, cutting over of a CIFS-only VDM or a block import session can be a disruptive process.
For a block-based import, after the cutover completes, host I/O operations are switched to the target system and the import process completes automatically. For a file-based virtual data mover (VDM) import, after cutover completes, the import process does an incremental copy automatically but you must complete the import manually.
An import is always conducted from the Unity storage system. The target system makes a remote call to the VNX storage system and instigates a pull (for file-based import) or push (for block-based import) of the source storage resources to the target system.