Create a one-time migration

One-time migrations don't track activity in your data during a migration. If you create a one-time migration, your LiveData Migrator instance won't scan your source storage for updates to the data as the migration progresses.

A one-time migration does not write a marker file to the source storage. Once the scan of the source completes (to determine which files and directories are to be migrated), the migration will enter a COMPLETED data migration state and won't perform any further scans.

You can only create one-time data migrations. You can't create one-time metadata migrations.

Create a one-time migration with the Azure Portal

1. In the Azure Portal, navigate to the LiveData Migrator resource page.
2. From the LiveData Migrator menu on the left, select Migrations.
3. Select Add.
4. Complete the details under the Basics section:
   • Target storage: your ADLS Gen2 storage account.
   • Path: the directory on your Hadoop edge node to migrate data from.
5. Select Next: Migration Settings.
6. Complete the Migration settings:
   • Target Action Policy: overwrite all the content (Overwrite) or only migrate new content that isn't already there (Skip).
   • Automatically Start Migration: start the migration right away, or start it manually later.
   • Enable Live Migration: change this option from the default 'Yes' to 'No'.
7. Select Review and create.
8. Select Create.

Your created one-time migration will display the parameter Live Migration: No in the migration overview.

Create a one-time migration with the CLI

Specify the scan-only flag when you create the migration:

az livedata migrator migration create  -g <resource_group> --migrator-name <migrator_name> --target-name <target_name>--migration-name <new_migration_name> --path <path_to_migrate> --scan-only