One-time migrations do not track activity in your data during a migration. If you create a one-time migration, Data Migrator doesn't scan your source filesystem for updates to the data as the migration progresses.
A one-time migration does not write a marker file to the source filesystem. When the scan of the source filesystem is finished (to determine which files and directories are to be migrated), the data migration state changes to completed. Data Migrator doesn't scan the source again.
Although no marker file will be written,
hdfs superuser access remains a requirement for migration from a HDFS source filesystem.
Create a one-time migration with the UI
To create a one-time migration with the UI, select the One-time option under Migration Type when creating a migration. Unlike a live migration, one-time migrations won't display a Live state in the UI.
A successful one-time migration appears in the UI as completed.
You can't rerun a completed migration. To detect new changes to the source, you can add a specific path for rescanning.
Create a one-time migration with the CLI
There are two ways to create a one-time migration through the CLI:
- Start a migration with a source filesystem configured for one-time migrations.
- Enter the
--scan-onlyflag when you create the migration.
For more information, see the migration add and the optional parameters sections of the Command reference.