All Products
Search
Document Center

PolarDB:Migrate a PolarDB-X 1.0 instance of the classic network architecture

Last Updated:Nov 08, 2024

This topic describes how to migrate a PolarDB-X 1.0 (formerly known as DRDS) instance of the classic network architecture to a destination zone and switch the network type from classic network to Virtual Private Cloud (VPC).

Overview

To migrate a PolarDB-X 1.0 instance of the classic network architecture to a destination zone and switch the network type from classic network to VPC, follow these steps:

  1. Check whether the PolarDB-X 1.0 instance that you want to migrate is a dedicated instance. If the instance is a shared instance, contact us to migrate the shared instance to a dedicated instance.

  2. Check the version of your PolarDB-X 1.0 instance. If your instance is earlier than 5.2.8, it is automatically upgraded to the latest version of 5.2.8 during the migration.

  3. Change the network type of the PolarDB-X 1.0 instance from classic network to VPC. If ApsaraDB RDS instances are attached to the PolarDB-X 1.0 instance, change the network type of the ApsaraDB RDS instances from classic network to VPC. After you change the network type, you must also fix the database shard connections. For more information, see Change the network type of an ApsaraDB RDS instance and Fix database shard connections.

  4. Change the instance from the classic network architecture to the classic network and VPC hybrid architecture. Create an endpoint of the VPC type. This way, the instance has two types of endpoints: classic network and VPC. Switch your business to the ECS instance of the VPC type and use the endpoint of the VPC type to access the PolarDB-X 1.0 instance. For more information, see Change the instance from the classic network architecture to the classic network and VPC hybrid architecture.

  5. Migrate all nodes of the PolarDB-X 1.0 instance from classic network to VPC. For more information, see Migrate an instance of the classic network and VPC hybrid type.

    Note

    During migration, a transient connection may occur for a few minutes. Make sure that your application can automatically reconnect to the instance.

Procedure

  1. Change the instance from the classic network architecture to the classic network and VPC hybrid architecture.

    1. Log on to the PolarDB-X 1.0 console.

    2. In the top navigation bar, select the region where the instance is deployed.

    3. In the left-side navigation pane, click Instances.

    4. Find the instance and click the instance ID to go to the Basic Information page.

    5. In the Common Actions section, click Switch to VPC.

    6. In the Switch to VPC dialog box, select the VPC and vSwitch.

    7. (Optional) Select Retain Original Classic Network Endpoint and configure the Expiration Time parameter.

      Note

      If you select Retain Original Classic Network Endpoint, the classic network endpoint is retained for a period of time after the VPC endpoint is generated. During this period, you can continue using the classic network endpoint to access the database. To ensure optimal security and performance, we recommend that you use the VPC endpoint at the earliest opportunity to prevent database access failure when the classic network endpoint expires.

    8. Click OK.

  2. Change the instance from the classic network VPC hybrid architecture to the VPC architecture.

    For more information, see Migrate an instance of the classic network and VPC hybrid type.