Migration Solutions

Last updated: 2021-08-09 18:05:33

    This document describes how to migrate a CVM, TencentDB for MySQL instance, and TencentDB for Redis instance from the classic network to a VPC.

    Background

    • The classic network is a public network resource pool for all Tencent Cloud users. The private IPs of all CVMs are assigned by Tencent Cloud. You cannot customize IP ranges or IP addresses.
    • A VPC is a logically isolated network space in Tencent Cloud. In a VPC, you can customize IP ranges, IP addresses, and routing policies, making it more suitable for use cases requiring custom configurations.

    As the classic network resources become increasingly scarce and cannot be expanded, starting from June 13, 2017, all new-registered Tencent Cloud accounts can only create instances (including CVM and TencentDB instances) in a VPC rather than the classic network. More and more users are migrating their instances from the classic network to VPC.

    Directions

    Check the instructions below according to your resource type.

    Resource Type Characteristics Limitation Instruction
    CVM The migrated CVM instances are the same as those being created in the VPC.
  • Migrating from classic network to VPC CANNOT be reverted. After the migration, the CVM instance cannot communicate with Tencent Cloud services in the classic network
  • The CVM instance needs to be restarted
  • The private IP changes from the classic network IP to VPC IP
  • Switch to VPC
    TencentDB for MySQL
  • The VPC access takes effect immediately after the migration.
  • The original classic network remains accessible for up to 7 days after the migration.
  • The database connection is not affected during the migration.
  • Migrating from the classic network to VPC CANNOT be reverted. After the migration, the TencentDB for MySQL instance cannot communicate with Tencent Cloud services in the classic network
  • The private IP changes from the classic network IP to VPC IP.
  • Switch Network
    TencentDB for Redis
  • The VPC access takes effect immediately after the migration.
  • The original classic network remains accessible for up to 7 days after the migration.
  • The database connection is not affected during the migration.
  • Migrating from the classic network to VPC CANNOT be reverted. After the migration, the TencentDB for Redis instance cannot communicate with Tencent Cloud services in the classic network
  • The private IP changes from the classic network IP to VPC IP.
  • Change Redis Network

    Migration Sample

    Note:

    This example is only for reference. Before your actual migration, please assess the impact on your business and develop a detailed migration plan .

    Description

    Suppose a classic network-based service uses four Tencent Cloud services, including CLB, CVM, TencentDB for MySQL, and TencentDB for Redis. Their relationship is shown below:

    • The public CLB is bound with two CVMs as the backend servers.
    • TencentDB for MySQL and TencentDB for Redis act as databases for applications deployed in the two CVMs.

    Migration Directions

    1. Migrate TencentDB instances to a VPC. After the migration, the original classic network access remains available for a certain period, thus maintaining the database connection and your service availability. During this period, you can complete the migration of other services.
    2. Create two CVMs and deploy services as needed in the VPC where the databases are migrated to. Then test whether the CVMs can access TencentDB instances.
    3. Create a public CLB in the VPC of databases, and associate it with the two CVMs created in the previous step. Perform a health check to avoid service interruption due to an exception.
    4. Wait for the migration to complete. Release the original public network CLB and CVM resources in the classic network.