Isolating/Restoring/Terminating Instances

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

Adjusting Deployed Node

Changing Instance Specification

Restarting Instance

Instance Management

Disaster Recovery Read-Only Instance

Changing Networks

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

An instance can be isolated when you no longer use it. Once isolated, the instance can neither be used nor accessed (but is not eliminated yet), and will be moved to the recycle bin, where you can restore or eliminate it or it will be automatically eliminated when it expires. Even though the instance is isolated, the space occupied by its resources is not freed, and it still has the most basic data replicas.

https://console.tencentcloud.com/mariadb/instance/index

, select the pay-as-you-go instance in the instance list, click 

 to return it manually. After the instance is returned, it is in the 

 status and will be retained for 3 days, during which it cannot be accessed. To restore it, you can do so in the recycle bin list.

After an instance is returned, once its status changes to "isolated", no fees related to it will be incurred.

After an instance is isolated, its IP will be released, and you may not get back the original IP after the instance is restored.

After an instance is isolated, you cannot upgrade it, modify its parameters, create or modify an account for it, roll it back, or rename it.

https://console.tencentcloud.com/tdsqld

. In the instance list, select an instance, and click 

In the pop-up dialog box, indicate your consent and click 


Go to the recycle bin where the instance is in the "isolated" status.

An isolated instance can be restored to its normal running status, which may take several minutes. The restored instance may have a new IP rather than the original IP before isolation.

, locate the instance in the recycle bin list, and click 

If you don't need an instance anymore, you can return it. Once returned, it is in the "isolated" status and moved to the recycle bin, where it will be automatically eliminated when it expires, or you can click 

After an instance is eliminated, its data will not be recoverable. Please back up the data in advance.

After an instance is eliminated, its IP resources will be released simultaneously, and its disaster recovery instance will stop the sync connection and automatically promote to primary instance.

tencent cloud