Help Center/ SAP Cloud/ Best Practices/ Best Practice of Using Block-Level Migration of SMS to Migrate SAP Applications and Databases Running on Linux Servers/ Preparing for the Migration/ (Optional) Preparing a Destination ECS
Updated on 2023-05-29 GMT+08:00
View PDF
Share

(Optional) Preparing a Destination ECS

For Linux block-level migration, you can choose to create an ECS or use the existing ECS as the destination server. Perform the following operations if you choose to use the existing ECS as the destination server.

Linux block-level migration of SMS is used here for the migration between different AZs in the same region. Before the migration, create a destination ECS with the same specifications, including disk quantity and size as well as OS, as those of the source server, and deploy it in the same VPC and region with but different AZs from the source server.

The created destination ECS must meet the following requirements. Otherwise, the migration may fail.

  • A target server running Windows must have at least 2 GB memory.
  • The destination server must have at least as many disks as the source server, and the size of each disk on the destination server must be at least as large as those on the source server.
  • The destination server must run the same OS as the source server, or there will be a server name conflict.
  • The destination server must have been configured with an EIP, VPN, or Direct Connect connection.
  • The security group of the VPC that the destination ECS is in must be correctly configured. If the destination ECS runs Windows, enable the TCP ports 8899 and 8900. If the destination ECS runs Linux, enable ports 8900 and 22.

For details, see How Do I Configure the Security Group Rules for Target Servers?