Table of Contents

FLI Status and Restart workflow

Online Foreign LUN import (FLI) involves many LUN migration jobs such as migration in progress, failed, paused, stopped, resume, modify throttle, state change, verify, and completed migrations. The FLI Status and Restart workflow enables you to effectively manage these LUN migration jobs.

You can use the FLI Setup and Import Job workflow to have all your setup ready for migration, and then use the FLI Status and Restart workflow to perform LUN migration and also keep track of all the jobs involved during migration.

Migration of block-level data is a common scenario when you plan for storage consolidation in your data center, purchase or lease new storage arrays, or perform technology refreshes. This requires data migration from one array to another, usually from one vendor array to another. FLI is a storage-array based migration method that enables a minimally disruptive transition for importing your data from third-party array LUNs to NetApp LUNs.

FLI can be done in two ways, offline FLI or online FLI. The offline FLI functionality supported in Data ONTAP 8.3 and later does not allow applications to access LUNs that are being migrated while FLI is active. The online FLI functionality supported in Data ONTAP 8.3.1 allows applications to continue to access data while the corresponding LUNs are being imported.

FLI for migrating data from third-party LUNs includes the following three initial phases:

Pre-cutover phase
This phase involves backing up foreign LUNs, configuring the SAN host, and configuring the foreign array.
Cutover phase
This phase involves taking the host applications offline, ensuring that no further access is available from the SAN host to the foreign LUNs outside of clustered Data ONTAP, and presenting NetApp LUNs to the SAN host by adding them to the igroup.
Post-cutover phase
This phase involves bringing the host back online, initiating the import of one or more foreign LUNs, and breaking the import relationship when the import is complete.

The LUN import process occurs in five different phases. The following image illustrates the five phases of SAN data migration:

The image displays the phases in SAN data migration.

This workflow automates the verification phase of the data migration in which you can monitor the progress of the LUN migration.

Prerequisites for executing the FLI Status and Restart workflow

You must ensure that certain requirements are met before executing the FLI Status and Restart workflow. You must be a cluster administrator for executing this workflow.

  • Your system must be running clustered Data ONTAP.
    Note: This workflow is qualified to work with Data ONTAP 8.3.1 and later.
  • OnCommand Workflow Automation (WFA) 3.1 or later must be installed.
  • You must have added OnCommand Unified Manager 6.3 or later as a data source in WFA and obtained the latest Unified Manager data.
  • Data migration of third-party LUNs must have been initiated using the FLI Setup and Import workflow.

What happens when you execute the FLI Status and Restart workflow

The FLI Status and Restart workflow enables you to effectively manage LUN migrations jobs using Online FLI functionality. Migration jobs are: migration in progress, failed, paused, stopped, and completed migrations.

The migration jobs are as follows:

  • Pause/resume LUN import

    You might want to temporarily pause the LUN import when the system load is high. After the system load become low, you can resume the LUN import.

  • Failed LUN import

    If any failure occurs in the system during the LUN import, you can check which LUN import failed and take necessary actions.

  • Started LUN import

    You can initiate the data migration.

  • Stopped LUN import

    After the import is complete, you can stop the data migration.

  • Completed LUN import

    You can keep track of all the completed LUN import operations.

  • Verified LUN import

    You can keep track of all the verified LUN import operations.

  • Modified throttle

    You can keep track of any throttle changes made to the LUN.

  • State change

    You can keep track of LUN operational state changes.

The following illustration displays the tasks involved in executing the workflow:

The image displays the tasks performed in the Managing LUN Migration Jobs workflow.

Executing the FLI Status and Restart Jobs workflow

The FLI Status and Restart Jobs workflow enables you to manage LUN migration jobs using the online FLI functionality.

Before you begin

  • Based on the operating system selected for Unified Manager 6.3 and 6.4, you must have downloaded and placed the data-collector_lun_import_ext.conf configuration file in the following location:
    • Windows user: C:\Program Files\NetApp\ocum\etc\data-collector
    • Linux user(with root login): /opt/netapp/ocum/etc/data-collector/
    • N.B.: Data collector functionality is not supported when Unified Manager (version: 6.3, 6.4) is hosted as a Virtual Appliance (vApp)

    You can access the configuration file from here.

  • From 7.0 Unified Manager onwards, Data collector functionality will be supported for Windows, Linux, and vApp workflows. Unified Manager DataCollector file manager workflow places the DataCollector configuration files in the appropriate operating system folders for OnCommand Unified Manager.
  • You must have downloaded the workflow pack from the Storage Automation Store.
  • You must have reviewed the prerequisites for executing the workflow.
  • About this task

    You should have the following input parameters available for executing the workflow:

    • Cluster name
    • Node name
    • Storage Virtual Machine (SVM) name
    • Maximum throughput limit

      This specifies the limit at which the import is throttled.

    • LUN import action such as resume, start, or pause
    • LUN paths


    1. Log in to WFA by providing the necessary credentials.
    2. Click Portal > Migration > FLI Status and Restart Jobs.
      Tip: You can use the filter () to locate the workflow.
    3. Click the Execute icon ().
      The Execute Workflow 'FLI Status and Restart Jobs' dialog box is displayed.
    4. Select the cluster.
    5. Select the node.
    6. Select the SVM.
    7. Specify the LUN migration job.
    8. Specify the maximum throughput limit at which the LUN import is throttled.
      If not specified, the default value of 0 is assigned.
    9. Select the appropriate LUN import relationship for which you want run the specified migration job.
    10. Specify whether you want to verify the LUN imports.
    11. Optional: Click Preview to validate your workflow before executing it.
    12. Click Execute.
      You can also schedule the workflow for execution at a later date and time by selecting the Choose Date and Time for Execution check box.