Dell PowerStore Importing External Storage to PowerStore Guide

General file-based import restrictions

The following restrictions apply to importing file-based external storage to PowerStore:

• Only Unified VNX2 is supported as import source storage system.
• VDM containing both NFS exports and SMB shares cannot be imported.
• VDM containing multiple SMB servers cannot be imported.
• VDM with the NFSv4 protocol enabled cannot be imported (no NFS ACL import).
• VDM with Secure NFS or pNFS configured cannot be migrated.
• Do not import replication (although replication can be running during the import).
• Do not import checkpoint/snapshot or checkpoint/snapshot schedule.
• Compressed files are uncompressed during import.
• No transparency on cutover for SMB (even in SMB3 with Continuous Availability).
• Changes to the file mobility network configuration or network issues that occur during an import session may cause an import operation to fail.
• Do not change network attributes (such as MTU size or IP address) and source VDM attributes during an import session. These changes can cause an import operation to fail.
• File system limitations:
  • VDM having a Nested Mount File System (NMFS) cannot be imported.
  • A file system mounted directly on DM cannot be imported.
  • A file system that is a replication destination cannot be imported.
  • A file system whose mount path contains more than 2 slashes cannot be imported.
  • The destination file system size may be larger than the source file system size.
• Rollback limitations:
  • Rollback may be disruptive (NFSv3 clients also have to remount).
  • Rollback of the configuration to the source is very limited.
• Do not import FTP or SFTP (File Transfer Protocol), HTTP (Hyper Text Transfer Protocol), and Common Event Publishing Agent (CEPA) and Common Anti-Virus Agent (CAVA) settings.
• Do not import from unhealthy systems.
  NOTE:For example, if a Data Mover (DM) is offline and does not respond during the remote system addition and object discovery for all importable objects, many commands that have to run may fail. Disable the problematic DM in the configuration. This action should allow the import to be created.
• Do not assign the session name of a deleted import session to an import session that is being created. The session name still exists in the file database and is deleted only when the remote system is deleted.
• When you configure an import and select a date and time for the import session to begin, do not schedule the import to begin within 15 minutes of the current time.