Creating a Server Migration Workflow

Precautions

Before creating a server migration workflow, read and understand the following precautions.

Prerequisites

• You have discovered servers by referring to Discovering Resources – Simple Project.
• Servers to be migrated have been added to an application, and the application servers have been assessed. For details, see Grouping Resources as Applications and Getting Target Recommendations. After the assessment is complete, you can purchase recommended target servers in batches. For details, see Purchasing Resources. Servers with targets associated do not need to be assessed. For details, see Associating Source Servers with Target Servers.

Procedure

1. Log in to the MgC console.
2. In the navigation pane on the left, choose Migrate > Workflows. Select a migration project in the upper left corner of the page.
3. Click Create Workflow in the upper right corner of the page.
4. In the Server Migration card, click Preview Steps to view the steps predefined in the template and the detailed description of each step. If the type of a step is Automated, the step is automatically performed by MgC. If the type of a step is Manual, you need to perform the step manually. Click Next: Configure Workflow in the lower right corner.
5. Configure the workflow parameters based on Table 1.

   Table 1 Parameters for configuring a server migration workflow

   Area	Parameter	Description
   Workflow Details	Name	Enter a name.
   	Description
   	Select Source Resources	By application: Servers in the selected application will be migrated together. By migration plan: Servers in the selected migration plan will be migrated together.
   Application	Application	If Select Source Resources is set to By application, select the application that contains the servers to be migrated.
   Migration Plan	Migration Plan	If Select Source Resources is set to By migration plan, select the plan that contains the servers to be migrated. For details about how to create a migration plan, see Creating a Server Migration Plan.
   Migration Network	Network Type	If you select Public, ensure that all target servers have EIPs bound. These EIPs will be used for the migration.
   		If you select Private, configure Direct Connect connections, VPN connections, VPC peering connections, or subnets in the target VPC in advance to ensure that the source environment can access the target environment. If the source environment cannot access the Internet, you need to enter the private IP address of the source proxy server and the proxy port used by the proxy software. If the source proxy server cannot access the Internet, put the SMS-Agent installation package at a location where the source servers can access directly or over a proxy. You can download the SMS-Agent installation package from the SMS console.
   Target Environment	Region	The target region. It defaults to the one you selected when you assessed the application.
   	Project	A project in the target region.
   	VPC	If the source IP address is 192.168.X.X, you are advised to create a VPC and a subnet that both belong to network range 192.168.0.0/16. If the source IP address is 172.16.X.X, you are advised to create a VPC and a subnet that both belong to network range 172.16.0.0/12. If the source IP address is 10.X.X, you are advised to create a VPC and a subnet that both belong to network range 10.0.0.0/8.
   	Subnet	The subnet has to be in the same network segment as the VPC.
   	Security Group	If there are Windows source servers, the security group must be configured to allow access on ports 8899, 8900, and 22. If there are Linux source servers, the security group must be configured to allow access on port 22. CAUTION: For security purposes, you are advised to only allow traffic from the source servers on these ports. The firewall of the target servers must allow traffic to these ports.
   Advanced Settings	Start Target After Migration	If you select No, the target servers will be stopped after the migration is complete. If you select Yes, the target servers will be started after the migration is complete.
   	Set Bandwidth Limit	If you select No, the migration traffic is not limited. If you select Yes, you can limit the bandwidth that can be used for migration based on the source bandwidth and service requirements. CAUTION: Consider the migration scale to set an appropriate bandwidth limit. If the bandwidth allocated to the workflow is too small, migration tasks in the workflow may preempt the limited bandwidth resource, and some servers may fail to be migrated.
   	Install rsync on Source	If you select No, the rsync component will not be installed on the source servers. If you select Yes, the rsync component will be automatically installed on the source servers. CAUTION: Linux migrations depend on rsync. If rsync is not installed on a source server, the server will fail to be migrated.
   	Retain IP Address	Enable this option to retain the private IP addresses of the source servers on the target servers. Enabling it may cause risks. You need to evaluate and bear the risks.
   	Enterprise Project	Select the enterprise project you want to migrate to. The enterprise project default is selected by default.

6. Click Next: Confirm.
7. Confirm the workflow settings, and click Confirm. The Run Workflow dialog box is displayed, which indicates that the workflow has been created.
   • If you want to start the migration immediately, click Confirm to run the workflow.
   • If you want to add a stage or step to the workflow, click Cancel. The workflow enters a Waiting state, and the migration is not started. To start the migration, click Run in the Operation column.

8. On the migration workflow details page, view the workflow settings and the migration progress. After the step for starting the migration Agent is completed, a migration task is automatically created on the SMS console. For details about the server information mapping between MgC and SMS, see What Are the Information Mappings Between MgC and SMS?
   • Move the cursor to the migration progress bar. In the box that is displayed, view more migration details.
   • When the migration progress bar reaches a step that requires manual confirmation, move the cursor to the progress bar and click Confirm next to the step status in the displayed window, so that the subsequent migration steps can be executed.
   • When the workflow reaches the ResizeDiskPartition step, the system identifies whether disk capacity reduction has been performed on the target server.
     • If yes, go to SMS console and resize disks and partitions for the target server. For details, see the Partition Resizing parameter in Configuring a Target Server. After the adjustment is complete, go back to the MgC console and click Confirm next to the step status so that the workflow can continue.
     • If no, skip this step.
   • The StartSynchronization step is repeated before you verify your services on the target server.
   • When the progress bar reaches Cutover, the migration is complete. You need check whether your service systems are running properly on the target server. If they are, manually switch services to the target server. After the switchover is complete, click Confirm in the workflow. The system automatically performs the following steps SourceClear and MigrationTaskClear.