Running migrations
To see when the next iteration will run for a migration path, go to the Jobs module and click Running.
Figure 43. Running job options
Manually start a migration iteration
We can start the next iteration or a special iteration of a migration path by selecting the path from the list and clicking the Start button under the table.
Figure 44. Manually start a migration
The start iteration wizard will first ask you to specify which type of iteration you would like to start:
- Incremental: The goal of an incremental iteration is to detect if any changes were made on the source since the previous iteration and if there are any, apply them to the target. Any open files are skipped during the iteration. Any such skipped files are verified and copied during subsequent incremental iterations.
Figure 45. Incremental iteration
- Normal: Applies all source changes that occurred since the previous iteration to the target.
- Force metadata copy: Recopies all metadata from source to target for all items in the migration, even if it has not changed.
- Force overwrite of external modifications on target: Overwrites the files that have been modified on the target before a migration has been switched over.
Figure 46. Incremental type
- Retry items with errors (xx): Allows you to run an incremental iteration limited to a subset of items that gave errors during the migration, instead of a normal iteration that runs for all items.
- Verification: A verification iteration compares the content and metadata of all items in order to check that they are consistent and that there is no data corruption.