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

Target provisioning

The following is the sequence of provisioning of the NAS server and file systems (thin file systems) in the target system:

1. The import session is validated to be initialized and all parameters are set correctly.
2. The target NAS server is created in import target mode with the correct name.
3. The target file system or file systems are created in import target mode with correct names that exactly match the source mount path.
4. All network interfaces of the source VDM are cloned into the target NAS server. All interfaces are created in disabled mode.
5. All network routing tables relative to the source VDM interfaces are cloned at the destination.
6. (This step is only applicable when the SMB server is joined to a domain.) The DNS domain and its corresponding servers are selected from the source VDM and set at the target NAS server. The DNS domain is selected as follow:
   • The DNS domain configured at the VDM level (nsdomain).
   • The DNS domain at the storage system level matching exactly the domain name of the VDM's SMB server.
   In any other cases, the pre-check fails.
7. The SMB protocol is enabled on the target NAS server and the source CIFS server configuration is cloned.
   NOTE: All network interfaces that are attached to the source VDM are added to the target SMB server regardless whether they were or were not at the CIFS server of the source VDM.
8. The quota information is dumped from the source file system or file systems to the matching target file system or file systems. If the file system is imported as a VMware FS data store on Unity, quotas import dumping is skipped.
9. Copy data of all the file systems from the source to the target file systems. The whole directory and file structure of the file system is parsed and cloned at the destination. However, only cold data (data not modified within one hour) is copied. Data that cannot be accessed is skipped during initial copy.
   NOTE: Parsing is done only once. If files or directories are created after the parsing is done, those new nodes are migrated during the incremental copy.
10. Local groups and users are migrated before the CIFS shares.
11. All CIFS shares of the source VDM are cloned into the target NAS server.
12. Source parameters that are migrated during migration of CIFS-only VDM include:
    • acl.extAcl
    • acl.restrictedTakeOwnership
    • admin.shareC_NotCreated
    • admin.shareC_RO
    • allowSnapSureVss
    • cifsclient.timeout
    • LanmanServer.disableNameChecking
    • LanmanServer.IdleUserAutoLogoff
    • LanmanServer.MaxMpxCount
    • nullSession
    • ReadOnly.Comp
    • ReadOnly.Delete
    • set_eas_ok
    • smbsigning
    • srvmgr.diskdrive
    • srvpwd.updtMinutes
    • windowsTimeUpdate
    • virtualDirName
    • updateMode
    • updatePTRrecord
    • cacheMaxGroups
    • cacheMaxHosts
    • SecurityLayer
    • maxNISCacheGroupsCount
    • maxNISCacheUsersCount
    • followabsolutpath
    • followdotdot
    • Traces
    After the parameter values are applied, the NAS server is restarted to take the new values into account.

If import failed during initial copy, the configuration import is not rolled back. You can resume the import operation after fixing the reported issues, and import start can continue from the last point when it failed.