Switching from Classic Network to VPC

Last updated: 2020-09-07 16:43:13

    This document describes how to migrate Cloud Virtual Machine (CVM), TencentDB for MySQL, and TencentDB for Redis from a classic network to VPC.

    Background

    • The classic network is the 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 Virtual Private Cloud (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.

    Due to the growing scarcity and non-expansion of the classic network resources, Tencent Cloud accounts registered after June 13, 2017 can only create instances (including CVM and TencentDB) in a VPC, but not in 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 24 hours after the migration
  • The database connection is not affected during the migration
  • Migrating from 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
  • Network Switch
    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 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
  • Configure Network

    Migration Sample

    Description

    This example is only for reference. In actual migration, please carefully assess the impact and develop the migration plan in advance.
    Suppose a classic network-based service uses four Tencent Cloud services, including CLB, CVM, TencentDB for MySQL, and TencentDB for Redis, as shown below:

    • The public CLB is bound with two CVMs as the backend servers.
    • TencentDB for MySQL and 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, so as to maintain the database connection and and your service availability. During this period, you can complete migration of other services.
    2. In the VPC where the databases are migrated to, create two CVMs and deploy services as needed. Then test whether the CVMs can access TencentDB instances.
    3. In the VPC of databases, create a public CLB and associate it with the two CVMs created in the previous step. Perform 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.

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help