Skip to main content
ONTAP FLI

Verify and delete the FLI LUN import relationship

Contributors netapp-aherbin
PDFs

After the import copy has completed and the import state is complete, you can finalize the migration by removing the import pairing with lun import delete, which safely deletes the import relationship after the source LUN is no longer in use and the destination LUN is now the active copy for host I/O. In an offline FLI workflow, you typically bring the destination LUN online after the import and any validation so the host can rediscover and resume access to the migrated LUN.

If you require a data-integrity confirmation before deleting the relationship, you can run lun import verify, which performs a block-by-block compare but is disruptive because verification must be performed offline (meaning the LUN must be taken offline and inaccessible to hosts for the duration of verify). Post migration operations, such as host remediation, zoning and initiator cleanup, documentation, and operational validation, are handled in the post migration phase, and are intentionally out of scope for this section.

About this task

Beginning with ONTAP 9.17.1, data migration of foreign LUNs using FLI offline migration is supported with ASA r2 systems. ASA r2 systems vary from other ONTAP systems (ASA, AFF, and FAS) in the implementation of its storage layer. In ASA r2 systems, volumes are automatically created when a storage unit (LUN or namespace) is created. Each volume contains only one storage unit. Therefore, for ASA r2 systems, you do not need to include the volume name in the -path option when creating the LUN; you should include the storage unit path instead.

Steps

  1. Set the privilege level to advance:

    set -privilege advanced

  2. Confirm import state (must be completed or stopped before delete):

    lun import show -vserver <SVM_NAME> -path /vol/<VOL>/<LUN_NAME>

  3. If import is still in progress state and completed % 100:

    lun import stop -vserver <SVM_NAME> -path /vol/<VOL>/<LUN_NAME>

  4. Delete the import relationship (finalize):

    lun import delete -vserver <SVM_NAME> -path /vol/<VOL>/<LUN_NAME>

  5. Verify the relationship is removed:

    lun import show -vserver <SVM_NAME> -path /vol/<VOL>/<LUN_NAME>

  6. Confirm the import is not actively running (should be stopped or completed):

    lun import show -vserver <SVM_NAME> -path /vol/<VOL>/<LUN_NAME>

  7. Take the LUN offline (verification must be done offline):

    lun offline -vserver <SVM_NAME> -path /vol/<VOL>/<LUN_NAME>

  8. Start block-by-block verification (optional but recommended):

    lun import verify start -vserver <SVM_NAME> -path /vol/<VOL>/<LUN_NAME>

  9. Monitor verification progress:

    lun import show -vserver <SVM_NAME> -path /vol/<VOL>/<LUN_NAME>

  10. Stop verification (required before bringing the LUN online):

    lun import verify stop -vserver <SVM_NAME> -path /vol/<VOL>/<LUN_NAME>

  11. Bring the LUN online (disruption window ends here):

    lun online -vserver <SVM_NAME> -path /vol/<VOL>/<LUN_NAME>