Skip to main content
ONTAP FLI

Verify ONTAP FLI offline migration results

Contributors netapp-aherbin
PDFs

After a LUN is migrated from the foreign array to your ONTAP storage system, FLI can perform a block-by-block comparison of the source and destination LUNs to verify that the migration is complete and accurate. A migration verification takes approximately the same amount of time as (or slightly more than) the migration.

A migration verification is not required, but is highly recommended.

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. Start the LUN migration verification.

    lun import verify start -vserver <SVM_name> -path <volume_path|storage_unit_path>

    This example shows the command to start the LUN migration verification for LUNs named bootlun, fdrive and gdrive in the winvol volume and the datamig SVM.

    DataMig-ontap::*> lun import verify start -vserver datamig -path /vol/winvol/bootlun

DataMig-ontap::*> lun import verify start -vserver datamig -path /vol/winvol/fdrive

DataMig-ontap::*> lun import verify start -vserver datamig -path /vol/winvol/gdrive

  2. Monitor the verification status.

    lun import show -vserver <SVM_name> -fields vserver, foreign-disk, path, admin-state, operational-state, percent-complete, imported-blocks, total-blocks, estimated-remaining-duration

    This example shows the command to monitor the verification status for the datamig SVM.

    DataMig-ontap::*> lun import show -vserver datamig -fields vserver, foreign-disk, path, admin-state, operational-state, percent-complete, imported-blocks, total-blocks, , estimated-remaining-duration

vserver foreign-disk path               admin-state operational-state percent-complete imported-blocks total-blocks estimated-remaining-duration
------- ------------ ------------------ ----------- ----------------- ---------------- --------------- ------------ ----------------------------
datamig 83017542000E /vol/winvol/fdrive started     in_progress       57               -               4194304      00:01:19
datamig 83017542000F /vol/winvol/gdrive started     in_progress       40               -               6291456      00:02:44
datamig 830175420010 /vol/linuxvol/bootlun
                                        started     in_progress       8                -               41943040     00:20:29
3 entries were displayed.

    You can execute the same command to track the progress of the verification. The operational-state displays a status of completed when the verification job is completed successfully.

  3. Stop the LUN verification.

    lun import verify stop -vserver <SVM_name> -path <volume_path|storage_unit_path>

    This example shows the command to stop the LUN verification for the datamig SVM.

    DataMig-ontap::*> lun import verify stop -vserver datamig -path /vol/esxvol/winrdmplun

    The LUN import verification must be explicitly stopped before bringing the LUN back online. Otherwise, the lun online command fails. This step must be performed manually even if the status shows that the verification is completed.

What's next?

Remove the LUN import relationship.