Version: 1.22.0 (latest)

Manage migrations

Manage your migrations with Data Migrator using either the WANdisco® UI or CLI.

caution

Don't write to target filesystem paths when a migration is in progress. This could interfere with Data Migrator functionality and lead to undetermined behavior.

Use different filesystem paths when writing to the target filesystem directly (and not through Data Migrator).

Manage migrations with the UI#

The Dashboard displays an overview of migrations and their status, showing what data has been transferred and data added since the migration started.

Select View migration for more detail.

To get an overview of the progress and status of your migrations, you can search and filter for:

Migrations by migration name
Paths by path name

Migration metrics#

Use metrics to view details about your migrations to better understand progress, including their bandwidth usage, migration events, and remaining scanned paths.

In the Dashboard, select a migration.
You will be taken to the Status of the migration tab by default.

Under Migration Metrics, observe the following:

Events yet to be processed: this graph displays the size of the event manager queue across a time period selected in the Filter by dropdown list.
Events yet to be migrated: this graph shows the size of the scheduled actions queue across a time period selected in the Filter by dropdown list.
Paths to be scanned: this graph displays the size of the queue for paths yet to be scanned across a time period selected in the Filter by dropdown list.

Assign exclusions to an existing migration#

Adding exclusions to an existing migration will change the future actions performed for that migration, but will not affect previously migrated content.

In the Dashboard, select a migration.
Under the sidebar that appears, select Exclusions.
Select Add and the appropriate exclusion template from the dropdown list.

Remove exclusions from an existing migration#

In the Dashboard, select a migration.
Under the sidebar that appears, select Exclusions.
Remove any of the exclusions one at a time.

Start a migration#

To start a migration and initiate data transfer, select Start.

Stop a migration#

Once a migration has started, you can select Stop to suspend transferring files indefinitely.

You can resume, reset, and delete a migration that is stopped.

Resume a migration#

Once a migration is stopped, you can select Resume to continue where it paused transferring files.

Delete a migration#

note

You must stop a migration before you can delete it.

To delete a migration:

Select the migration from your Migrations panel.
On the Migration Status page, select Stop.
Select Delete.

Reset a migration#

Reset a migration to set it to the state it was in before it started. This deletes the migration and creates a new migration in its place with the same settings as the previous.

When you stop a migration, a Reset button becomes available next to the Resume button. Select it to open the Reset Migration panel. Configure the following:

Reset Path Mappings: Select this box to erase the migration's path mapping configuration and automatically use your most recent path mapping configuration for Data Migrator. Clear it to continue using the same path mapping configuration from before the reset.
Skip or Overwrite Settings: Select Overwrite if you want the migration to re-migrate any and all files that had already been migrated before the reset, regardless of whether the file sizes are the same at the source and target filesystems. Select Skip If Size Match to skip migrating any files that already exist in the target and have the same file size as the source.

Select Reset to confirm your selection and reset the migration.

Rescan a migration#

Data Migrator tracks changed paths on the source filesystem and rescans paths for any updates when the migration finishes.

Data Migrator collects paths for rescanning automatically during a migration, but you can manually add them if you want the directories to be rescanned after further updates. You can also run the entire migration again by making the root directory the path to be rescanned.

Add paths for rescanning in the UI#

To add a path for rescanning in the UI:

Select the migration you want to add a path for rescanning to in the Dashboard.
Under the sidebar that appears, select Rescan.
Enter the path to the directory in Add rescan directories.
Select which action policy to use (Overwrite or Skip If Size Match).
Select +Add.

Add paths for rescanning in the CLI#

To add a path for rescanning to a migration, run the command migration pending-region add.

Example

migration pending-region add --migration-id myFirstMigration --path /dir1/userA --action-policy com.wandisco.livemigrator2.migration.SkipIfSizeMatchActionPolicy

Data migration states#

Migrations can be in one of the following states:

NONSCHEDULED : A non-scheduled migration has been defined but not yet started. Create a migration in this state by not entering the --auto-start parameter on creation.

RUNNING : A running migration is scanning through source data and transferring data to the target, as well as responding to change notifications from the source, if applicable.

STOPPED : A stopped migration has been stopped by a user manually and is not transferring content or making other changes to the target.

LIVE : A live migration has completed scanning through source data, continues to respond to change notifications from the source, and transfers data and makes changes to the target as required.

COMPLETED : A completed migration has scanned through all source data and finished transferring all applicable data to the target filesystem, and doesn't migrate changes to source data. See One time migrations.

Check your migration#

Check the status of a live migration by going to the migration's screen and selecting Migration Errors from the Migration menu.

The Migration Errors panel provides a Migration Errors Report that lists failed migration operations. The report table lists each failed operation with columns for the Timestamp, Operation type, and Path and Failure, which provides the path to the failed element, along with a description of the failure.

View the current status and results of any verification scans configured to check that all the source data and changes are available on the target and are consistent between the source and target. For more information, see Verify migrations.

Filter and search for failed operations#

You can filter or search for failed operations by using the Operation type dropdown on the Migration Errors Report panel. The filter contains the following operations:

Operation	Description
Create	Create operations set up a new data migration. For more information, see Create a migration.
Migration (Transfer file)	Migration operations handle the transfer of data to be migrated.
Unlink (Delete path)	Unlink operations remove files under migration.
Rescan (retry)	Rescan operations restart an earlier source filesystem scan.
Rename	Rename operation handles name changes in files or directories under replication.
Metadata (Change permissions)	Metadata operations change file metadata, such as file ownership.
Marker (Internal to Data Migrator)	Marker operations are part of Data Migrator's internal migration mechanics. Marker file operation failures may be evidence of a serious problem with your Data Migrator deployment. Contact WANdisco Support with details of the errors.

Advanced search#

Select Advanced search ^ to display Filter Rules for additional search options. Use the following entry fields to create an advanced search rule:

Field: Select Path to search all available migration paths or Failure to search only failed migration paths.
Operator: Select Contains or Does not contain to apply to your search.
Enter Value: Enter the value you want your search to match, according to your chosen operator. If you select the "Does not contain" operator, your search will match with paths or failure paths that don't include the value.

Select + Add Rule to add additional search criteria. Select Apply to view the search results. You can continue to add rules to your current search, but you must select Apply to update the search results.

note

Historical failure information may be garbage collected, so it may not be possible to show all failures. In this case, a warning appears:

"We're unable to show detailed results of failed operations. We only have detailed results from the most recent [number of available failures] results"

Manage migrations with the CLI#

Command	Action
`migration stop`	Stop a migration
`migration reset`	Reset a migration
`migration resume`	Resume a stopped migration
`migration delete`	Delete a migration
`migration exclusion add`	Add an exclusion to a migration
`migration exclusion delete`	Remove an exclusion from a migration
`migration list`	List running and active migrations
`migration start`	Start a migration
`migration show`	Get migration details
`migration pending-region add`	Add a path for rescanning to a migration
`status`	Get migration status