Overview

The user can migrate one or more migration sources to Baidu AI Cloud. This feature can realize the migration of systems, application programs, etc. on the source server to Baidu AI Cloud from the self-built machine room (IDC) or cloud platform and other source environments. It facilitates enterprise cloudification, cross-cloud platform migration, and other business needs.

Basic Concept

• Migration source： The migration sources (source servers) refer to the IDC server, virtual machine, and virtual machines of other cloud platforms to be migrated by the users.
• Migration task： You can view the migration source information of the specific server, and the information and migration progress of the current migration server.
• Migration center： It helps to realize the resource migration among the user's intranets, extranets, Baidu AI Cloud accounts, and different regions for Baidu AI Cloud resources. The current document only involves the migration of the user's extranet resources.

Usage Scenarios

The online migration applies to the following scenarios, (including but not limited to):

• Cloudification of IT architecture
• Deployment of hybrid cloud architecture
• Cross-cloud migration
• Cross-account or cross-region migration

Use Restriction

• Your source host and target cloud server should both have the public network addressing capabilities.
• To guarantee the normal operation of migrated BCC cloud server, the users are recommended to install cloud-init on the migration source before migration. Refer to Install cloudbase init for details.

• The versions of migration source operating system supported by the current migration center include:

  	 CentOS 6(i386|x86_64)  
  	 CentOS 7(i386|x86_64)  
  	 Ubuntu 14.04|16.04|18.04(i386|x86_64)  
  	 Debian 8.11|9.9  

• Please ensure the Python version is 3.4 or above before use. Meanwhile guarantee the pip corresponding to Python is installed and the rsync with the version of 3.1.0 or above is installed at the migration source.

Notes

Before migration

• Before the official migration, please add ingress rules in the default security group. Select SSH fast template. The port range is 22.

• Before using the migration tasks, please apply for the large image white list (Ticket Application) to realize the association of large images with related snapshots. It is convenient to smoothly find your migration resources after completion of migration tasks.

After migration

• After successful migration, we generate the large image, associated snapshot and snapshot chain of the corresponding migration tasks. The snapshot chain is charged from March 2020. If you need to remove the snapshot chain, you should first delete the associated large images and snapshots.

Migration Steps

Install the migration tool

1. Download Baidu AI Cloud Migration Tool to your source server.
2. Use tar xvf Baidu_Migrate_Tool.tar for decompression.

3. Enter the agent installation directory cd migrate-center-agent/. Use setup.sh to install the corresponding dependences required by agent running by one key.

sh setup.sh 

4. The installation is completed when the following output shows.

Run the migration tool

1. Before running, please fill in the AK/SK of the user to which the image created by the migration belongs in the user_cfg.json.

2. Before running, please fill in the AK/SK of the user to which the image created by the migration belongs in the user_cfg.json. The console and transfer virtual machine should coordinate in running. Please maintain the open status of terminal window during the migration process. After the migration is completed, you can see the log output executed by agent in the migrate-center.log.

./migrate-center start 

3. Start agent by ./migrate-center start. Please ensure the migration source currently has no virtual machines in the mistake status.

4. After startup, the log is stored in the migrate-center.log file. The agent is started successfully when you see the rolling log output by the tail -f migrate-center.log. The user can go to the console for operation.

Manage migration sources

Precondition

• The migration tool agent is run successfully.

Operation steps

1. Log in to Baidu Cloud Compute (BCC) Console to enter the instance list.
2. Click Server Migration Center in the left navigation of the console to enter the server migration center.

3. When the migration tool agent is started successfully, the migration source is created automatically. The migration source information is automatically displayed in the list.

   • The migration tasks can be created for the migration source in the Online status.
   • Only the migration source without any migration tasks can be deleted. To delete the migration source, you should first delete the migration task.

   

Manage migration tasks

Precondition

• The migration tasks can be created when the migration source status is "online".

Restriction Description

Limit and description of starting/stopping/deleting migration tasks:

• Enable: Verify whether the account is in arrears. If the account is in arrears, the prompt is given that the tasks can't be started. If the user selects the process of automatic creation of proxy server, the started verification is the verification of the created postpaid resources.
• PAUSING: Stop the migration task. The task status changes to paused. The total time consumption is recorded normally.
• Deletion: If the migration task status is [Migrating], the migration task can't be deleted. You should first stop the migration task; delete the migration task, the deleted migration task disappears from the list, and the created automatic proxy server is removed as the task is deleted.

Description of transfer server creation

To migrate resources, we create a postpaid transfer server resource for you. The configuration is shown as below:

• Transfer virtual machine:
  • Cpu： 1 core
  • Memory: 1G
  • CPU model:
    2.4HZ Intel Xeon(Skylake) Gold 6148
    2.4HZ Intel Xeon E5-2680v4
    Intel Xeon Silver 4110/Intel Xeon E5-2620 V4/Intel Xeon E5-2650 V4/Intel Xeon E5-2620 V3/Intel Xeon E5-2620 V2
  We select the server types according to the degree of resource remaining, and create the servers successively.
• Transfer disk: it is created according to the data disk at the migration source. The data disks with the capacity less than 5G are not displayed.
• Transfer EIP: it is created according to the size filled in by the user. If the user fills in 0 or nothing, it created according to the maximum bandwidth 200.
• Network type: Default VPC, default subnet and default security group.

Release:

• BCC instance (paid)
• EIP Resource (paid)
• Disk instance (paid)

Retain:

• Snapshot chain (paid)
• Large image instance
• Snapshot instance

Operation steps

1. Log in to Baidu Cloud Compute (BCC) Console to enter the instance list.
2. Click Server Migration Center in the left navigation of the console to enter the server migration center.
3. Select Migration Task in the left navigation bar of Server Migration Center to enter the migration task list.
4. Click Create Migration Task.

5. In the Select Source page, configure the following information and click Next.

6. In the Select Destination page, configure the following information and click Next.

7. Confirm the migration task information in the Confirm Information page, and click Next to complete the creation of the migration task.
8. After creating the migration task, you can click the migration task name and migration task ID to view the migration task details.

Exception handling

If your migration task status is abnormal, you can check from the following situations. Several situations of abnormal migration task status:

• The migration task abnormality may be caused by network instability. If the heartbeat is lost for over 3 minutes, the migration task is abnormal.
• When the migration task is abnormal, you can query whether the migration source status is abnormal.
• The migration failure may be caused by change of configuration of transfer server in the transport process, or setting of no ssh access 22 port in the default subnet in advance. Please view Description of Transfer Server Creation.
• The migration task is in the "migrating" status all the time. The reason may be insufficient resources in the creation of transfer server. Please confirm whether the post-paid resources of transfer example are created successfully.