About tasks and action tables

Nondisruptive Migration User Guide

Version
9.6.0
Audience
anonymous
Part Number
MK-92RD8086-11

Under normal circumstances, when a migration job fails, you can simply resolve the problem that caused the failure and restart the task using the Restart Task button in the Task Detail dialog. If the task fails to restart, you will need to intervene manually as described in Troubleshooting a migration job so that you can continue the migration process.

For example, in following diagram, the third subtask of Step 3 has failed. After fixing the error that caused the failure, you can continue the migration either by undoing each of the subtasks and start over from Step 3, or by completing the third subtask and continuing with Step 4.

Figure. Example of failed migration task
Note: Depending on the nature of the task, it may not be possible to complete a failed subtask. In such as case, repeating the entire step is the only option.

To aid you in this process, this guide includes a series of action tables. An action table contains all the tasks and subtasks associated with a step in the migration workflow.

Figure. Using action tables

The first column contains the operations necessary to move backward (to the previous state) and the second to move forward (and complete the task). The third column consists of commands you can execute verify that the actions you have taken have been successful.

To troubleshoot a failed migration job, locate the task or subtask that failed in the table. To return to the previous state, perform the operations above the failed task by starting from the row immediately above and working upward. When completing the task, perform the operations immediately below, working downward.

The same action tables are used to a different end in Backing out of a migration, with a separate workflow that can be used to reverse the entire migration process.