Shulou(Shulou.com)06/02 Report--

This article mainly introduces how to obtain VPC intranet migration cloud, has a certain reference value, friends in need can refer to. I hope you will learn a lot after reading this article. Next, let the editor take you to learn about it.

VPC private network migrates to cloud

If you can access the proprietary network VPC in a certain Ali cloud region directly from the self-built data center (Integrated Data Center,IDC), virtual machine environment or CVM, it is recommended that you use the cloud migration solution where the source server is interconnected with the VPC private network. Cloud migration in VPC private network can achieve faster and more stable data transmission than through public network, and improve the efficiency of cloud migration.

prerequisite

Cloud migration via VPC private network requires that you can access the target VPC from IDC, virtual machine environment or CVM. The specific implementation scheme can choose high-speed channel service or VPN gateway service, make use of the special line access function of high-speed channel or build a VPN gateway in the target VPC.

Description: high-speed tunnel or VPN gateway is a billing service. For more information, please see the billing method of high-speed tunnel and VPN gateway.

Client_data description

VPC private network migration cloud requires you to edit the client_data file yourself. Client_data records the data files during cloud migration and contains the following information:

Attributes such as ID, name, public network bandwidth and IP address of the cloud transfer instance.

Migrate the process information of the data disk.

The name of the generated custom image.

The region and network type of the transit instance deployment.

The VPC, virtual switch, and security group used by the transit instance.

For more details, please see the client_data file for downloading the post-migration cloud tool.

Note: to avoid the failure of cloud migration, do not modify the configuration file client_data if you do not have the need for cloud migration via VPC private network. Otherwise, it will affect the work of moving the cloud, process stutters and other phenomena.

After downloading the cloud relocation tool and opening the client_data file, you need to modify the following parameters:

The source server can access the specified VPC

The following steps apply to net_mode=1 situations. The cloud migration project is divided into three phases, in which phase 1 (Stage 1) and phase 3 (Stage 3) are completed in the standby server, which requires the standby server to access the public network; and phase 2 (Stage 2) data transfer is carried out in the source server to be migrated.

Log in to a server A where you can access the public network.

Edit the client_data file of the cloud migration tool: set net_mode=1 and enter the vpc_id, vswitch_id and zone_id parameters that have been configured with high-speed tunnel service or VPN gateway.

(optional) configure the security_group_id parameter in the client_data file, but the security group entry direction must release proxy ports 8080 and 8703. For more information, see adding Security Group rules.

Follow the public network cloud migration steps to run the cloud migration tool in server A until you prompt Stage 1 Is Done!.

Log in to the source server you need to migrate, copy the cloud migration tool configuration of server A, including user_config.json, rsync and client_data files, and keep the content of the configuration file consistent.

Follow the public network cloud migration steps to run the cloud migration tool in the source server to be migrated until you are prompted Stage 2 Is Done!.

Log in to server An in step 1 and copy the cloud migration tool configuration of the source server to be migrated in step 5, including user_config.json, rsync, and client_data files, which must be consistent.

Follow the steps of public network cloud migration and run the cloud migration tool again in server A until the prompt Stage 3 Is cloud migration indicates that VPC private network cloud migration is completed successfully.

The source server can access the public network and specify VPC

The following steps apply to the case of net_mode=2, and the operation process is the same as that of net_mode=0, that is, the public network is moved to the cloud. During net_mode=2, data is automatically migrated to the cloud from VPC, and other processes go to the public network, and the transfer speed is slightly slower than that of cloud migration via VPC private network (net_mode=1).

Log in to the source server where you can access the public network, and follow the steps of public network cloud migration to run the cloud migration tool.

Edit the client_data file of the cloud migration tool. Set net_mode=2 and enter the vpc_id, vswitch_id and zone_id parameters that have been configured for high-speed tunnel service or VPN gateway.

(optional) configure the security_group_id parameter in the client_data file, but the security group entry direction must release proxy ports 8080 and 8703. For more information, see adding Security Group rules.

Follow the steps of cloud migration on public network to run the cloud migration tool.

Thank you for reading this article carefully. I hope it is helpful for everyone to share how to get the content of VPC intranet relocation. At the same time, I also hope that you can support us, pay attention to the industry information channel, and find out if you have any problems. Detailed solutions are waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.