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

Prerequisites for a multiprotocol VDM import session

Conditions must be met before starting a multiprotocol VDM import session.

Those conditions include the following:

1. 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 is configured for multiprotocol imports.
   NOTE: If the source VDM has NFS exports and a CIFS server that is enabled, you can migrate the VDM even if there are no CIFS shares. A single CIFS server must be configured on the VDM to allow multiprotocol imports to occur.
6. The user performing the import must belong to the source local Administrator group and have backup and restore privileges.
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 must be 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 and access all the source base exports. 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 that the import interface is not used for any other purpose; for example, migrating NFS-only exports or CIFS-only shares to hosts.
15. The extended ACL feature must be enabled on the source Data Mover that hosts the VDM.
16. The DNS must be configured in the Windows domain.
17. The NT security must be enabled on the source VDM.
    NOTE: Share and UNIX-level security levels are not supported.
18. 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.).
19. The target pool that is specified to create the target NAS server exists.
20. All the specified target pools in the file system-pool pairs exist.
21. All the specified source file systems in the target VMware data store candidate exist, and are valid import candidates.
22. There is no active import session on the SP of the default target production port.
23. 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.
24. There is at least one valid source file system that is mounted on the source VDM.
25. There is at least one valid source production interface, which is up, attached to the source VDM.
26. The total number of valid source production interfaces cannot exceed the limit of network interfaces for each NAS server on the target Unity system.
27. The specified file systems to be imported as a VMware NFS data store should have only one export at root directory.
28. NFS export does not contain an unsupported character or characters, such as comma (,) or double quote (").
29. There are no NFS exports that were only temporarily unexported and whose path does not exist anymore. To check for this kind of export run the following command on the control station: nas_server -query:name==vdm147 -fields:exports -format:%q -query:IsShare==False -fields:Path,AlternateName,Options -format:"<Path>%s</Path>\n<AlternateName>%s</AlternateName>\n%s\n" Compare the resulting list with the output of server_export. If there are some differences, you must delete the old entry in the VDM in the vdm.cfg file. Do the following:
    1. Log in as root on the control station.
    2. Go to the root file system of the VDM (cd /nas/quota/slot_X/root_vdm_xx/.etc).
    3. Edit the file vdm.cfg and remove the line corresponding to the NFS export that you want to clean (vi vdm.cfg export "/fs4" anon=0).
    4. Check that the export does not appear anymore in the nas_server -query. Do not reboot the VDM.
30. If the source VNX system is configured with the code page 8859-1 or 8859-15 for the NFSv3 clients, ensure that the code page for the Unity system matches the code page being used on the VNX system. With Unity OE 4.3 and later, the code page of the Unity system can be changed through the svc_nas {<NAS_server_name> | all} -param -facility vdm -modify codepage -value <value> service command.
31. When you perform a VDM import of FLR-enabled file systems, the source VNX Data Mover that is running the DHSM service should also be configured with username and password credentials.