Table of Contents

FLI Post-Jobs workflow

For storage consolidation in your data center, after you have migrated data from third-party LUNs to a NetApp cluster, you should break the source and destination LUN relationship. The FLI Post-Jobs workflow enables you to break the LUN import relationship and delete any failed LUNs from Data ONTAP.

When you plan storage consolidation in your data center, you should migrate data from one array to another. Online foreign LUN import (FLI) is a storage array based migration method that enables a smooth transition for importing your data from third-party arrays to NetApp clusters, and enables you to continue to have access to your LUNs during data migration.

FLI can be done in two ways, offline FLI (supported in Data ONTAP 8.3) or online FLI (supported in Data ONTAP 8.3.1). The offline FLI functionality does not allow applications to access LUNs that are being migrated while FLI is active. The online FLI functionality 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 initiator group (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 break the LUN import relationship and delete any failed LUNs.

Prerequisites for executing the FLI Post-Jobs workflow

You must ensure that certain requirements are met before executing the FLI Post-Jobs 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 either using the Preparing LUN Migration Job workflow or Managing LUN Migration Jobs workflow.

What happens when you execute the FLI Post-Jobs workflow

The FLI Post-Jobs workflow enables you break the relationship between source and destination LUNs after you import them to the NetApp cluster. The workflow also enables you to delete any LUN from a failed LUN import operation.

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

Executing the FLI Post-Jobs workflow

After you imported third-party LUNs to a NetApp cluster, the FLI Post-Jobs workflow enables you to delete the relationship between the source and destination LUNs. This workflow also enables you to delete any LUNs from a failed LUN import operation.

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
    • LUN operational state
    • LUN import relationships for deletion


    1. Log in to WFA by providing the necessary credentials.
    2. Click Portal > Migration > FLI Post-Jobs.
      Tip: You can use the filter () to locate the workflow.
    3. Click the Execute icon ().
      The Execute Workflow 'FLI Post-Jobs' dialog box is displayed.
    4. Select the cluster.
    5. Select the node.
    6. Select the SVM.
    7. Select an appropriate LUN operation state.
      The operational states are verified, imported, stopped, and failed.
    8. Select the LUN import relationships that you want to break.
    9. Specify if you want to delete a LUN whose import has failed.
    10. Optional: Click Preview to validate your workflow before executing it.
    11. 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.