Dell Unity™ Family VNX® Series Data Import to Unity All Flash or Hybrid, or UnityVSA™ System User Guide

PDF

Multiprotocol VDM import

Beginning with Unity OE 5.1, you can perform a multiprotocol migration session only if the source VNX VDM and the Unity VDM support multiprotocol access.

When configuring a multiprotocol import session, you must specify qualifiers for both the CIFS and NFS parts of the migration.

NOTE: Access policies might affect client access after the migration is complete.

For CIFS/SMB, you must create a network interface and add it to the source VDM to migrate.

NOTE: For SMB operations, SMB1 must be enabled for the initial copy to start. SMB1 is a requirement for all CIFS-based migrations. You can disable SMB1 after the migration is finished.

All file systems are migrated as Thin and maintained as Thin on the target Unity system. File systems cannot be migrated individually, only as part of the VDM server migration.

The following conditions apply to VNX to Unity migration:

  • If the source VDM has an NFS export and an enabled CIFS server, you can use multiprotocol migration to migrate the VDM to Unity.

    You can migrate that VDM even if it does not have a CIFS share.

  • If the source VDM only has an NFS export and the CIFS server is disabled, you can use NFS migration to migrate this VDM to Unity.
  • If the source VDM has a CIFS share and the CIFS server that is enabled, you can use CIFS migration to migrate this VDM to Unity.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\