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 Breaking LUN Import Relationship workflow enables you to break the LUN import relationship.
When you plan 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 smooth transition for importing your data from third-party arrays to NetApp clusters. FLI for third-party LUN data migration includes the following three pre-phases:
This phase involves backing up of foreign LUNs, configuring SAN host, and configuring the foreign array.
This phase involves making the host applications offline, ensuring that there is no further access 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.
This phase involves bringing the host back online, initiating import for one or more foreign LUNs, and breaking the relationship when the import is complete.
The actual LUN import happens in five different phases. The following image illustrates the five phases of SAN data migration.
This workflow automates the breaking of LUN import relationship in the post-cutover phase.
The following sections provide details about the workflow and how to execute the workflow:
You must ensure that certain requirements are met before executing the Breaking LUN Import Relationship workflow. You must be a cluster administrator for executing this workflow.
The Breaking LUN Import Relationship workflow enables you break the relationship between source and destination LUNs after you import them to NetApp cluster.
The following illustration displays the tasks involved in executing the workflow:
After you import third-party LUNs to a NetApp cluster, the Breaking LUN Import Relationship workflow enables you to delete the relationship between the source and destination LUNs.
You should have the following input parameters available for executing the workflow: