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

Prerequisites for a CIFS-only VDM import session

Before you start a CIFS-only VDM import session, the following conditions must be met:

1. The source VNX system exists, and the VNX1 OE is 7.1.x or later or the VNX2 OE is 8.1.x or later.
2. (Optional) The specified name for the import session is not used by other import sessions.
3. The source VDM exists, and is in the loaded state.
4. The source VDM is not under import or has an associated complete import.
5. The source VDM does not have any NFS exports.
6. 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.
7. The maximum allowed deviation in time between the source side Data Mover (DM) that hosts the VDM and the target side SP that hosts the target NAS server is 5 seconds.
8. There exists only one network interface whose name starts with nas_migration_xx among all the up network interfaces that are attached to the source VDM. This interface is used as the source import interface.
9. Verify that the physical Data Mover on which the source VDM is located, has at least one IP interface configured that is not attached to the VDM being migrated.
10. One import interface of type replication exists on the default production port of the target SP, uses the same IP protocol (IPv4 or IPv6) and is in the same VLAN as the source import interface. The target import interface can reach the source import interface. This interface can be autodetected, or specified as the target import interface.
11. The default target production port exists, and supports the type file.
12. All the specified target production ports in the interface-port pairs exist, support the type file, and are on the same SP of the default target production port.
13. All the specified source production interfaces in the interface-port pairs exist, and are in the up state.
14. The import interface on the source must be dedicated for only the import purpose. Hosts must not use this interface for access. Ensure it is not used for any other purpose, for example, used to export NFS exports or CIFS shares to hosts.
15. All the specified source file systems in the file system-pool pairs exist, and are valid import candidates. (These import candidates are mounted to the source VDM, and cannot be NMFS, replication destination, root file system, raw file system, and nonimported FLR file system.).
16. The target pool that is specified to create the target NAS server exists.
17. All the specified target pools in the file system-pool pairs exist.
18. All the specified source file systems in the target VMware data store candidate exist, and are valid import candidates.
19. There is no active import session on the SP of the default target production port.
20. If the import session is created, the total number of the import candidate source file systems cannot exceed the limit of total file systems of all active sessions.
21. There is at least one valid source file system that is mounted on the source VDM.
22. There is at least one valid source production interface, which is up, attached to the source VDM.
23. The total number of valid source production interfaces cannot exceed the limit of network interfaces for each NAS server on the target Unity system. See the Unity Support Matrix on Online Support for information about network interface limits related to NAS servers.
24. A single CIFS server is configured on the source VDM.
25. C$ share is available on the source Data Mover that hosts the VDM and is not disabled or set to Read-only. The C$ share must be available, otherwise the import cannot start. If it was disabled or Read-only on the source, change the corresponding parameters to enable it:

    server_param <source_server> -facility cifs -modify admin.shareC_NotCreated -value 0

    server_param <source_server> -facility cifs -modify admin.shareC_RO -value 0

    NOTE: You must stop and start the service that is associated with the CIFS facility for changes to admin.shareC_NotCreated to take effect.
26. Local SMB users are enabled on the source CIFS server.
27. The user performing the import must belong to the source local administrator group and has backup and restore privileges.
28. The extended ACL feature is enabled on the source Data Mover that hosts the VDM (parameter cifs.acl.extacl should have bits 2, 3, and 4 set, decimal value 28). Use the following command to view the settings:

    server_param <source_datamover> -facility cifs -info acl.extacl

    If necessary, use the following command to change the setting:

    server_param <source_datamover> -facility cifs -modify acl.extacl -value 28

29. Unknown SID feature has been enabled on the source Data Mover that hosts the VDM (parameter cifs.acl.mappingErrorAction must be set to 0x0b, decimal value 11). Use the following command to view the settings:

    server_param <source_datamover> -facility cifs -info acl.mappingErrorAction

    If necessary, use the following command to change the setting:

    server_param <source_datamover> -facility cifs -modify acl.mappingErrorAction -value 11

30. NT security is enabled on the source. Share and UNIX security level is not supported.
31. The source VDM is not utf8-based.
32. The source CIFS server is not a Windows NT 4.0 like CIFS server.
33. DNS is configured for the Windows domain in the case of a domain-joined CIFS server.
34. Other VDMs from the source can reach DNS and domain controller (DC) after cutover.
35. DNS and DCs are reachable on the destination after cutover.
36. If you perform a VDM import of FLR-enabled file systems, the source VNX Data Mover that is running the DHSM service must be configured with username and password credentials.
37. Before you begin the import session, if there is tree quota that is configured on the file system, ensure that the CIFS share path and quota directory are the same and share the same case letters. For example, if the quota tree path is /DIR1, the CIFS share path must be /<fsname>/DIR1.