Changing Networks

Overview

Strengths

Use Cases

Sharding

Read/Write Separation

Elastic Expansion

Strong Sync

Basic Principles

Instance Architecture

Regions and AZs

Product Introduction

Billing Overview (InnoDB)

Product Pricing (InnoDB)

Purchase and Upgrade

Refund

Payment Overdue

Backup Space Billing

Purchase Guide

Creating Instance

Connecting to Instance

Managing Sharded Table

InnoDB Engine

Getting Started

Renaming Database Instance

Specifying Project for Instance

Isolating/Restoring/Terminating Instances

Adjusting Deployed Node

Changing Instance Specification

Restarting Instance

Instance Management

Disaster Recovery Read-Only Instance

Creating Account

Modifying Account Permissions

Cloning Account

Configuring Read/Write Separation

Resetting Account Password

Deleting Account

Account Management

Access Management

Security Group Configuration

Transparent Data Encryption (TDE)

Security Management

Slow Query Analysis

Backup Mode

Downloading Backup File

Backup Encryption

Rolling Back Database

Backup and Rollback

Data Migration

Enabling Database Audit

Viewing Audit Logs

Modifying Log Retention Period

Database Audit

Operation Guide（InnoDB）

Import from Standalone Instance to TDSQL Instance

Import Between TDSQL Instances

Selection of TDSQL Instance and Shard Configuration

Practical Tutorial

Platform Security Design

Tenant Security Features

Security White Paper

Use Limits

Compatibility

Connecting Database

Join and Subquery

Sequence

Frequently Used DML Statements

Distributed Transaction

Creating Table

Connection Protection

Globally Unique Field

Exporting/Importing Data

Database Management Statements

Passthrough SQL

Preprocessing

Subpartitioning

Error Codes and Messages

InnoDB

Development Guide

History

Introduction

API Category

AssociateSecurityGroups

DescribeDBSecurityGroups

DescribeProjectSecurityGroups

DisassociateSecurityGroups

ModifyDBInstanceSecurityGroups

Security Group APIs

DescribeBackupFiles

DescribeDBEncryptAttributes

KillSession

ModifyAccountPrivileges

ModifyInstanceNetwork

ModifyDBEncryptAttributes

CreateOnlineDDLJob

Other APIs

Request Structure

Common Params

Signature v3

Signature

Responses

Making API Requests

ActiveHourDCDBInstance

CancelDcnJob

CloneAccount

CloseDBExtranetAccess

CopyAccountPrivileges

CreateAccount

CreateDedicatedClusterDCDBInstance

DeleteAccount

DescribeAccountPrivileges

DescribeAccounts

DescribeDBLogFiles

DescribeDBParameters

DescribeDBSlowLogs

DescribeDBSyncMode

DescribeDBTmpInstances

DescribeDCDBInstanceNodeInfo

DescribeDCDBInstances

DescribeDCDBPrice

DescribeDCDBShards

DescribeDatabaseObjects

DescribeDatabaseTable

DescribeDatabases

DescribeDcnDetail

DescribeFileDownloadUrl

DescribeFlow

DescribeLogFileRetentionPeriod

DescribeOrders

DestroyDCDBInstance

DestroyHourDCDBInstance

GrantAccountPrivileges

InitDCDBInstances

IsolateDedicatedDBInstance

IsolateHourDCDBInstance

ModifyAccountDescription

ModifyDBInstanceName

ModifyDBInstancesProject

ModifyDBParameters

ModifyDBSyncMode

ModifyInstanceVip

ModifyInstanceVport

ResetAccountPassword

SwitchDBInstanceHA

TerminateDedicatedDBInstance

UpgradeDedicatedDCDBInstance

UpgradeHourDCDBInstance

CreateDCDBInstance

CreateHourDCDBInstance

DescribeDCDBInstanceDetail

ModifyAccountConfig

OpenDBExtranetAccess

IsolateDCDBInstance

TDSQL APIs

Data Types

Error Codes

API Documentation

General

Disk Overuse

IO Metric Exception

FAQs

Performance Comparison Data for Strong Sync

General References

Glossary

Alarm Upgrade

Announcements

Contact Us

TDSQL for MySQL

This document describes how to change the instance network type and modify the instance access address.

Modifying the network configurations of an instance is highly risky. Do so only during off-peak hours. After modification, unless the original IP is assigned to another service or a custom IP repossession time is set, the original IP will remain valid for another 24 hours by default. We recommend you modify your business configuration accordingly as soon as possible.

You can modify the private network address of a TencentDB instance in VPC.

https://console.tencentcloud.com/tdsqld

 and click an instance ID in the instance list to enter the instance details page.

 to modify it. You can do so only when the current subnet has available IPs.


In the pop-up window, modify the private network address and click 

You can switch a TDSQL for MySQL instance's network between VPC subnets.

In the pop-up window, select the subnet to switch to under the VPC, select 

The original IP address remains valid for another 24 hours by default after the network is changed. Change your business IP address accordingly within 24 hours.

 to 0–168 hours. If it is set to 0 hours, the IP is released immediately after the network is changed. This may affect your business.

As the product supports an intra-region active-active architecture, we recommend you choose a VPC subnet in the same region as your business server or the source node.

In the pop-up window, select the VPC to switch to, select 

The original VIP address remains valid for another 24 hours by default after the network is changed. Change your business IP address accordingly within 24 hours.

In the pop-up window, select a VPC, select 

The switch from classic network to VPC is irreversible.

After the switch, VPC access will take effect immediately. The original classic network access will be retained for 24 hours; therefore, other instances associated to the instance should be migrated to VPC within 24 hours so as to guarantee uninterrupted access.

tencent cloud