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

PDF

Create an import session for file

Prerequisites

Although all import sessions are listed and created from the same starting point in the UI, the steps that appear in the related wizard are based on whether the resource type for the import session is a NAS server (for NFS, CIFS/SMB, or both, in a multiprotocol session) or a LUN or consistency group (CG). This procedure is pertinent to a NAS server. To create an import session for a LUN or CG, see Create an import session for block.

Ensure that you have first created relevant mobility interfaces and import connection, and then determine the following:

  • The system that you want to assign as the import source system. This is based on the import connection that is configured on the storage system.
  • The name, pool, storage provisioning, and tiering policy you want to use for the import storage resource. The system will automatically create a target storage resource as part of this process.
  • The source NFS, CIFS, or multiprotocol VDM server must be configured with a separate, non-production interface, that has the prefix "nas_migration_xxx", which is used during the import session to migrate the VDM and file system data through the Unity system's mobility interface.
  • 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. This ensures that the source Data Mover can provide uninterrupted Name Services for the remaining file servers. The VDM import session will fail if this additional interface is not present.
  • 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.
NOTE: If you change settings on the source system (such as attaching an interface to the source VDM or mounting a file system to the source VDM), you must discover these objects before starting an import session. In Unisphere under PROTECTION & MOBILITY , select Import > VNX Connections and select the import connection and More Actions > Discover Import Objects.

Steps

  1. Under Protection & Mobility, select Import > Sessions.
  2. To create an import session, select the Add icon.
    The Select Source to Import screen of the Create Import Session wizard appears.
  3. Select the appropriate Source System, select NAS Server as the Resource Type, and the VDM by name for the Resource.
    OE 5.1.0 supports multiprotocol migration from a VNX source VDM to a Unity destination VDM. For multiprotocol migrations, choose Multiprotocol NAS Server as the source.

    The source VDM name in the Resource field indicates whether that VDM supports multiprotocol migration. If you want to initiate multiprotocol migration, the source VDM must have a multiprotocol-migration enabled configuration.

  4. For the Configure Target NAS Server screen, the NAS Server Name is the same as the source VDM name. Select the target Pool to use for the NAS server, the target SP Owner (SPA or SPB), and the appropriate Target Storage Pool for the imported file systems, if different from the pool used for the NAS server. You can specify the Target Type as File System or VMware NFS data store (VMNFS) for each file system.
  5. For the Modify Target Production Port screen, select the appropriate Ethernet port under the Target Port column. Leave Allow comparison of Server Parameters checked, unless you prefer to override the parameter comparison between the source VNX and the target Unity file servers.
    NOTE: Skipping the server parameters comparison could lead to a disruptive cutover during import.

    Select the Target Import Interface from the list. For Import File System with FileRetention Enabled, which is applicable only to Unity systems running OE version 4.4 or earlier, keep No selected if you prefer not to import any file system that is using File Level Retention.

    NOTE: If you prefer to import file systems that are configured for File Level Retention, select Yes to override this selection.
    • For Unity systems with OE versions earlier than 4.5, File Level Retention settings themselves are not supported on the target Unity system and will not be imported.
    • For Unity systems with OE versions 4.5 and later, for the subsequent Specify DHSM Credentials screen, specify the username and password to use to connect to the source DHSM HTTP server.
      NOTE: If DHSM is not already configured on the source file system, see the VNX system Unisphere online help or the VNX Command Line Interface Reference for File for information about setting up the DHSM configuration on the source VNX system.
  6. For Specify Source CIFS Server Credentials, specify the username and password to use to connect with the remote CIFS server. These are for the local user who is a member of the administrators local group.
    Ensure that the prerequisites for the source CIFS server configuration have been completed. See Prerequisites for CIFS-only VDM import.
    Once you specify the necessary information, the system will generate a summary of the import session information. Go to the next step.
  7. Verify that the import session information appearing in the summary is accurate and complete.
  8. Click Finish to create and start the import session.
    The Results window appears and shows the progress of the creation and start of the import session.

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: <>()\