Table of Contents

Migrating Third-party LUNs to a Cluster

The Migrating third-party LUNs to a Cluster workflow enables you to mark the disks as foreign, create a LUN and take it offline, map the newly created LUN to an existing igroup, set up LUN import, and verify if the LUN is imported.

When you plan for storage consolidation in your data center, you should migrate data from one array to another. Foreign LUN import (FLI) is a storage-array based migration method that enables a minimally disruptive transition for importing your data from third-party arrays to NetApp clusters.

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

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 planning phase of the data migration in which you can schedule and verify the LUN import.

The following sections provide details about the workflow and how to execute the workflow:

Prerequisites for executing the Migrating Third-party LUNs to a Cluster workflow

You must ensure that certain requirements are met before executing the Migrating Third-party LUNs to a Cluster 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 and later.
  • OnCommand Workflow Automation (WFA) 3.0 or later must be installed.
  • You must have added OnCommand Unified Manager 6.2 or later as a data source in WFA and obtained the latest Unified Manager data.
  • You must be using fabric that enables a NetApp to cluster discover the back-end LUNs from third-party arrays.
  • The destination Storage Virtual Machine (SVM) and igroup must already exist.
  • The destination FlexVol volume must already exist.
  • You must have ensured that paths to the foreign disks from all the nodes in the cluster are reachable.
  • You must have ensured that the FC logical interface is available on all nodes.

What happens when you execute the Migrating Third-party LUNs to a Cluster workflow

The Migrating Third-party LUNs to a Cluster workflow enables you to organize source LUNs (third-party LUNs) and destination LUNs (NetApp LUNs) for migration. The workflow enables you to create LUNs and take them offline, map the LUNs to the igroup, set up LUN import, and verify that LUN import is complete.

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


The image displays the tasks performed in the Migrating Third-party LUNs to a Cluster workflow.

Executing the Migrating Third-party LUNs to a Cluster workflow

The Migrating Third-party LUNs to a Cluster workflow enables you to set up LUN import and verify the LUN import to a cluster.

Before you begin

  • The workflow pack must be downloaded 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
  • Foreign disks
  • Storage Virtual Machine (SVM) name
  • Volume name
  • LUN prefix name
  • OS type
  • igroup name

Steps

  1. Log in to WFA by providing the necessary credentials.
  2. Click Portal > Migration > Migrating Third-party LUNs to a Cluster.
    Tip: You can use the filter () to locate the workflow.
  3. Click the Execute icon ().
    The Execute Workflow 'Migrating Third-party LUNs to a Cluster' dialog box is displayed.
  4. Select the cluster.
  5. Select the node.
  6. Select the required foreign disks.
  7. Specify whether you want to start the LUN import and whether you want to verify the LUN imports.
  8. Provide LUN details such as the SVM name, volume name, LUN prefix, operating system type, and the igroup name.
  9. Optional: Click Preview to validate your workflow before executing it.
  10. 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.