• Configure import using Unisphere

    PDF

    Configure import using Unisphere

    Configure protection and mobility interfaces

    Before you begin

    Protection and mobility (import) interfaces can be shared between replication and import. For import, only VDM imports require interfaces. Block imports do not require interfaces.

    Protection and mobility (import) interfaces are configured to support VDM imports and must be created prior to creating an import connection. A mobility interface IP address is assigned to SPA and SPB on the target Unity system. Once the mobility interface is configured, you can create the import connection between the Unity system and the VNX system. Mobility interfaces are not used for block import sessions.

    Ensure the following:

    • The interface port is cabled and connected to a network switch.
    • Both SPs are up and running.

    Obtain the following information for each Storage Processor (SP):

    • IP address associated with the interface (replication or import). Although you can specify an IPv4 or IPv6-based address, ensure that you specify the same type of address for both SPs.
    • IP address mask or prefix length that identifies the associated subnet.
    • Gateway IP address associated with the interface.
    • If applicable, the VLAN ID (between 1 and 4095) you want to associate the interface with.
      For the network to continue functioning properly, ensure that you set the VLAN ID only when you have configured the network switch port to support VLAN tagging of multiple VLAN IDs.
    Procedure
    1. Under Protection & Mobility, select Interfaces.
    2. Perform one of the following actions:
      • To create an interface, select the Add icon. On the Create Interface window, specify the relevant information:
        • For asynchronous replication or import, from the Ethernet Port list, select an available Ethernet port.
        • For synchronous replication, from the Ethernet Port list, select Sync Replication Management Port.
          Do not use Sync Replication Management Port for asynchronous replication or import interfaces.
      • To modify an interface, select the interface, and then select the Edit icon. On the Interface Properties window, specify the relevant information.
      • To delete an interface, select the interface, and then select the Delete icon.
        Before you delete an interface, ensure that the interface is not being used by any replication or import session.

    Configure import connection

    Before you begin

    Once the mobility interfaces have been configured (required for file import only), you can create a single import connection between the Unity system and the source VNX system. The import connection supports either block or file import sessions. You need to enter the IP address of the source SPA or SPB and the credentials of a user with administrator privileges on the source system when you create the connection. After creating the import connection, you are ready to create your file or block import session.

    Ensure the following:

    • For a source VNX system with two control stations, the home directory of a user with the Administrator role, which is used in configuring the import connection, must exist on the primary control station of the VNX.
    • An import connection does not already exist to the source system.
    • If the connection will be used for a VDM import, ensure mobility interfaces are configured on each SP of the target system.
    • The relevant SP pair (source and target SPAs or source and target SPBs) are up and running.
    • For block:
      • If using Fibre Channel, Zoning between VNX and Unity SP pairs is configured. Avoid using VNX MView ports or Unity Synchronous Replication ports.
      • If using iSCSI, iSCSI interface IP addresses on both SPs on the VNX and Unity systems are configured.
      • The iSCSI connection pairs between the VNX SPs and the Unity SPs are created.
        Highlight the system name and right click iSCSI, then select Connections Between Storage Systems > Connections > Add. Select iSCSI IP on SPA, enter the Target Portal IP address for Unity SPA, then repeat for SPB, and assign a name for the Connection.

    Obtain the SP IP management address and associated user credentials that will be used to connect to the source system.

    Procedure
    1. Under Protection & Mobility, select Import > Connections.
    2. Perform one of the following actions:
      • To create an import connection, select the Add icon. On the Create Connection window, specify the relevant information.
      • To modify an import connection, select the import connection, and then select the Edit icon. On the Connection Properties window, specify the relevant SP (SPA or SPB) IP address, username, and password to authenticate to the SP of the source storage system.
      • If new import interfaces were added, or existing import interfaces were deleted, the source system connection may become outdated. Select the relevant import connection, and then select Verify and Update to update the source system connection to pick up the latest import interface changes on the target and source systems.
      • If new source storage resources were added, or existing source storage resources were deleted or modified after you create an import connection and before you create an import session to the source system, you need to re-discover the source storage system resources. Select the relevant import connection, and then select Discover Import Objects to re-discover the source system resources.
      • To delete a mobility interface, select the import interface, and then select the Delete icon.
        Before you delete an import connection, ensure that the state of the associated import session is either cancelled or completed.

    Create an import session for file

    Before you begin

    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 or CIFS (SMB)) 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 you want to assign as the import source system. This is based on the import connection 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 or CIFS 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 will be able to 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 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.
    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 need to discover these objects before starting an import session. In Unisphere under PROTECTION & MOBILITY , select Import > Connections and select the import connection and More Actions > Discover Import Objects.
    Procedure
    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.
      Mixed NFS and CIFS import is not supported. For CIFS, the source VDM must be CIFS only (for example, no exports) and have only one CIFS server.
    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.
      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, keep No selected if you prefer not to import any file system that is using FileRetention.

      If you prefer to import file systems that are configured for FileRetention, select Yes to override this selection, with the understanding that FileRetention settings themselves are not supported on the target Unity system and will not be imported.
      For NFS import, once you specify the necessary information, the system will generate a summary of the import session information. Go to Step 7. For CIFS import, go to Step 6.
    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 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 Step 7.
    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.

    Manage import sessions for file

    An import session establishes an end-to-end path for an import operation between a source and target. The import source and target are remote to each other, so the session establishes the path that the data follows as it moves from source to target.

    To set up an import session for file, see Configure import .

    Procedure
    1. Under Protection & Mobility, select Import > Sessions.
    2. Perform one of the following actions:
      Action Description
      Modify a session
      Select a session and click the pencil (View/Edit) icon or double click a session to modify the name of the session. The file system to pool mapping and the interface to port mapping cannot be changed through Unisphere once the target resources (NAS server, file system, and interface) are created; however, the CLI does allow you to make these changes to a session's configuration before the start of import or during an initial copy failed state.
      Pause and resume a session
      Select a session and under More Actions, click Pause or Resume. Use Pause to pause an import session that is in either the Initial Copy or Incremental Copy state. Use Resume to start an import session that is in the Initialized state, or resume an import session that has been paused and is in the Initial Copy or Incremental Copy state.
      Cutover
      Select a session that is in the ready to cutover state, and under More Actions, click Cutover to cut over an import session to promote the target to production mode.
      Client accesses are switched from the source VDM, to the target NAS Server. During the cutover of a CIFS-only VDM migration, hosts will have I/O interrupted and see a short period of data unavailability (DU).
      Cancel
      Select a session and under More Actions, click Cancel. You can cancel an import session that is in any state (with the exceptions of Cancelling, Cancelled, Cutting Over, or Committed) before the commit state. The cancel operation rolls back the VDM and related file systems to the source VNX.
      This operation is not transparent. The host needs to be remounted to the NFS. For CIFS, hosts will see DU (disconnection and no access) and may need to re-connect.
      Commit
      Select a session and under More Actions, click Commit. You can commit an import session that is in the Ready to Commit state to finish the import process.
      Download summary report
      Select a session and under More Actions, click Download Summary Report.

    Create an import session for block

    Before you begin

    Although all import sessions are listed on 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 or a LUN or consistency group (CG). This procedure is pertinent to a LUN or consistency group (CG). To create an import session for a NAS server, see Create an import session for file.

    Ensure that you have first configured FC zoning for the source and target systems or created an iSCSI connection between the source and target systems and, if necessary, created relevant interfaces and import connection, and then determine the following:

    • The import source system, which is based on the import connection configured on the storage system.
    • The name, pool, storage provisioning, and tiering policy you want to use for the import storage resource and, depending on the type of pool, whether data reduction is enabled. The system will automatically create a target storage resource as part of this process.
      For storage provisioning, determine whether to convert a thin LUN to a non-thin (thick) LUN, or a thick LUN to a thin LUN. Also, determine whether to enable data reduction on a thin LUN in an All-Flash pool. Data reduction is only supported on All-Flash pools.
    Procedure
    1. Under Protection & Mobility, select Import > Sessions.
    2. To create an import session, select the Add icon.
      The Create Import Session wizard appears.
    3. Step through the wizard and specify the relevant information to select the source to import, configure the target LUN or CG and, if necessary, configure the host access and session throttle settings for the import session.

      The name of the import session will default to import_sess_<sourceResourceName>_<sourceSystemSerialNumber>_<targetSystemSerialNumber>.

      In the Target step, the LUN or CG name is the same as the source LUN or CG name. In case of a naming conflict, the source system name will be appended with the next available number, such as 01. You should always see a suggested pool selection based on capacity unless there are no valid pools available. If necessary, the Target Name and Pool, Tiering Policy, Thin, and Data reduction of the associated LUN or LUNs can be modified.

      If Thin is not selected, Data Reduction cannot be selected and is disabled. If Thin is selected, Data Reduction can be selected. Data reduction is only supported on All-Flash pools.

      In the Access step, select or add a host or hosts that can access the storage resource.

      In the Setting step, specify whether to throttle the import transfer. Transfer throttle impacts the import speed and host latency for the related LUNs and file systems that are in use on the source and target storage systems. The default is set to throttle (checkbox is checked), which means that the session is throttled. If set to unchecked, import transfer would be unthrottled and allowed to function at the highest rate possible.

      Once you specify the necessary information, the system will generate a summary of the import session information.
    4. Verify that the import session information appearing in the summary is accurate and complete.
    5. 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.

    Manage import sessions for block

    An import session establishes an end-to-end path for an import operation between a source and target. The data follows the path as it moves from source to target.

    To set up an import session for block, see Configure import .

    Procedure
    1. Under Protection & Mobility, select Import > Sessions.
    2. Perform one of the following actions:
      Action Description
      Modify a session
      Select a session and click the View/Edit icon or double click a session to modify the name of the session or change the configuration settings for the transfer throttle and the cutover threshold percent.
      Pause and resume a session
      Select a session and under More Actions, click Pause or Resume. Use Pause to pause an import session that is in either the Initial Copy or Incremental Copy state. Use Resume to start an import session that is in the Initialized state, or resume an import session that has been paused and is in the Initial Copy or Incremental Copy state, or when a session fails and the cause of the failure has been fixed.
      Cutover
      Select a session and under More Actions, click Cutover to cut over an import session to promote the target to production mode.
      Cancel
      Select a session and under More Actions, click Cancel. You can cancel an import session that is in any state (with the exceptions of Cancelling, Cancelled, or Cutting Over) before the commit state. The cancel operation deletes the SAN Copy session for each set of LUN pairs in the import session and disables SAN Copy access to the target LUN. It also deletes the target LUN or CG associated with the import session.
      Commit
      Disabled since a separate commit action is not needed for a block import session. This action is performed automatically at the end of cutover for a block import session.