Creating a Cross-AZ Batch Server Migration Workflow

Operation Process

Figure 1 shows the process of creating a workflow for cross-AZ server migration.

Figure 1 Cross-AZ server migration process

Step	Operation
Preparations	Create an IAM user and obtain the required permissions and an access key for the user. For details, see Preparations.
Create an application migration project.	Create a project to segregate and manage your migration resources. For details, see Creating an Application Migration Project.
Discover source servers.	Discover source servers and collect their details. MgC provides the following methods for you to do this work. Online Discovery Manual Addition
Create a cross-AZ server migration plan.	Create a migration plan to outline the servers to be migrated together and configure the target servers. For details, see Creating a Cross-AZ Batch Server Migration Plan.
Creating a cross-AZ migration workflow	After the preceding steps are complete, create a cross-AZ migration workflow.

Create a cross-AZ migration workflow.

1. Sign in to the MgC console. In the navigation pane, under Project, select your application migration project from the drop-down list.
2. In the navigation pane, choose Migration Workflows (NEW).
3. On the Workflows tab, click Create Workflow to open the Select Creation Method page.
4. Select the created cross-AZ migration plan from the Migration Plan drop-down list and click OK. Only complete migration plans can be selected. For details about how to create a migration plan, see Creating a Cross-AZ Batch Server Migration Plan.
5. In the Workflow Basics area, specify a workflow name or use the name preset by the system and enter a description (optional).
6. In the Resource Settings and Migration Settings areas, check whether the resource and migration settings inherited from the selected migration plan meet your requirements. If you need to modify these settings, click Modify Migration Plan in the lower right corner of the page and update the migration plan settings.
7. Confirm the settings and click Create Workflow in the lower right corner of the page. The Start Workflow dialog box is displayed, indicating that the workflow has been created.
   • If you want to start the migration immediately, click Confirm to run the workflow.
   • If you want to save the migration workflow without starting the migration, click Cancel. The migration workflow will move to a Waiting status, and the migration has not started yet. To run the workflow, click Run in the Operation column to manually start the migration. If you need to add checkpoints to the workflow to control the migration process, see Adding a Stage or Step.

8. In the workflow list, click the workflow name. On the Workflow Details page, you can review the workflow status, progress, and migration progress of the resources contained in the workflow. You can perform the following operations on the resources included in the workflow:
   • Click a resource name. On the Resource Details page displayed on the right, you can review the basic information, migration status, and migration progress of the resource.
   • When the workflow on a resource reaches a step requiring manual confirmation, choose Confirm in the Operation column, or click the resource name. In the displayed page, click Confirm. The workflow will then continue with the remaining migration steps.

Deleting Workflow Resources

• Only resources in the Failed, Paused, or Completed state can be deleted.
• You can delete all resources to be migrated in a workflow. After all resources in a workflow are deleted, the workflow will be deleted together.

1. Click the workflow name to view its details.
2. In the resource list, select the resources to be deleted and click Delete above the list.
3. Confirm the selected resources, enter DELETE, and click Confirm.
   

   To prevent resource deletion failures caused by disconnection of the workflow from related services (such as SMS, OMS, and OBS), you can select Force Delete to forcibly delete the resources. However, this operation only deletes the resource data from MgC. It may not delete the related tasks and resources in the related cloud services like SMS, OMS, and OBS. After the deletion, you need to manually delete the related tasks and resources in the related cloud services.