tencent cloud

PrevNext

피드백

키워드를 검색하세요

Recent Pages

문서
Virtual Private Cloud
    문서
    Download PDF

    Migration Solutions

    마지막 업데이트 시간:2024-10-22 16:43:46
    PDF 다운로드
      This document describes how to migrate from your resources from the classic network to VPC.
      Note: Before switching the network, you need to create a VPC in the same region as the classic network instance to be migrated and create a subnet in the same AZ as the instance. For more information, see Creating VPCs.
      Tencent Cloud provides the two migration solutions below:
      Migrating a ingle instance: Choose this if you only need to migrate instances one by one.
      Hybrid access: if your business involves CVM, CLB, and TencentDB instances, you can use this solution to ensure a smooth business migration.

      Migrating a Single Instance

      You can easily migrate a instance from the classic network to a VPC. See below for details.
      Instance
      Features
      The instance needs to be restarted
      The classic network IP is immediately changed to the VPC IP, with no retention time
      If the CVM instance has a public IP, the public IP will stay unchanged after the network switch, which will not affect the access at domain name
      Dual-IP access is maintained for a certain period of time. The original classic network IP retention time is as follows:
      MySQL: 24 hours (1 day) by default and up to 168 hours (7 days)
      MariaDB: 24 hours (1 day)
      TDSQL: 24 hours (1 day)
      Redis: you can choose to expire immediately, release after 1 day, release after 2 days, release after 3 days, or release after 7 days
      MongoDB: the original IP on v4.0 or above will expire immediately. For other versions, you can choose to expire immediately, release after 1 day, release after 2 days, release after 3 days, or release after 7 days
      You can configure up to two networks for each instance, both of which can be used for business access. The IPs of different networks can be the same.
      Note:
      If you want to keep the resource IP addresses unchanged after the network switch, try to create a VPC that covers the classic network IP.
      Create a private DNS service and resolve its domain name. After migrating the resources to a VPC, use Tencent Cloud Private DNS.
      Access using the public IP.

      Hybrid Access Solution During the Migration

      Hybrid access means the services being migrated can access both the classic network and a VPC. Tencent Cloud provides the following hybrid access solutions:
      TencentDB: the accessibility of classic network IP and VPC IP ensures the hybrid access at the TencentDB instance level.
      COS: access through domain name naturally provides the hybrid access capability.
      CVM:
      Classiclink: allows the classic network-based CVMs to interconnect with VPC resources such as CVM, TencentDB, and CLB instances.
      Peering connection: allows the instances in a VPC to communicate with resources in the classic network (except CVMs).
      Note:
      To use peering connection, submit a ticket.
      To configure Classiclink, see Classiclink.
      For migration of CLB instances, see Example: Migrating a Public Network CLB and Example: Configuring Hybrid Access for a Private Network CLB.
      문의하기

      고객의 업무에 전용 서비스를 제공해드립니다.

      문의하기
      기술 지원

      더 많은 도움이 필요하시면, 티켓을 통해 연락 바랍니다. 티켓 서비스는 연중무휴 24시간 제공됩니다.

      티켓 제출
      연중무휴 24시간 전화 지원
      Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
      개인정보 처리방침서비스 약관쿠키 정책