tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary

Setting Instance Termination Protection

PDF
Focus Mode
Font Size
Last updated: 2025-12-01 19:04:19

Scenarios

In most cases, when you no longer need an instance, you can terminate the instance through the console or an API. To prevent accidental termination of the instance, you can enable the instance termination protection feature. If the feature is enabled, you cannot terminate the instance through the console or an API. If you confirm that the instance needs to be terminated, you can disable the feature first and then proceed with the termination.
You can enable instance termination protection to prevent accidental termination of the instances that contain your business data. This document introduces how to enable or disable instance termination protection through the console.

Feature Description

Instance termination protection is disabled by default for newly purchased and existing instances. You can enable it as needed.
After instance termination protection is enabled for the primary instance, the feature will be automatically enabled for all its associated read-only instances, disaster recovery instances, and read-only analysis engines, including both existing and newly purchased ones. You can disable instance termination protection individually for specific associated instances. For example, you can disable instance termination protection for a read-only instance.
After instance termination protection is disabled for the primary instance, the feature will be automatically disabled for all its associated read-only instances, disaster recovery instances, and read-only analysis engines.
When instance termination protection is disabled for the primary instance, you can independently enable the feature for the associated read-only instances, disaster recovery instances, or read-only analysis engines. When the feature is independently enabled for these instances, it is not automatically enabled for the primary instance.

Must-Knows

Instance termination protection does not apply to system-level termination, such as the termination of pay-as-you-go instances that are shut down due to overdue payments and the termination of yearly/monthly subscription instances that have expired and remained in the recycle bin for more than 7 days.

Fee Description

Currently, the feature is free of charge.

Supported Architectures

The feature is supported for TencentDB for MySQL instances with single-node, two-node, three-node, and Cluster Edition architectures, as well as the read-only analysis engine.

Feature Status Description

After instance termination protection is enabled, the status of related instances in the instance list and instance details page will become Termination Protection Enabled. You can quickly determine whether this feature is enabled by this status.
After instance termination protection is enabled, all feature buttons associated with instance termination for the instance will be grayed out and unavailable for clicking.

Operation Steps

Enabling Instance Termination Protection

For Existing Instances
For New Instances
Enable instance termination protection for a single instance.
1. Log in to the MySQL console, select the required instance in the instance list, and choose More > Set Instance Termination Protection in the Operation column.

Note:
You can also choose More > Set Instance Termination Protection on the top-right corner of the instance details page.
2. In the pop-up instance termination protection window, select Enable and click OK to enable instance termination protection.
Enable instance termination protection for instances in batches.
1. Log in to the MySQL console, select multiple instances in the instance list, and choose More > Set Instance Termination Protection above the instance list.
2. In the pop-up instance termination protection window, select Enable and click OK to enable instance termination protection.
2. Complete the parameter configuration for the instance purchase, check "Prevent accidental instance termination through the console or an API" under the instance termination protection option, and click Buy Now.

Note:
For more information about complete purchase parameter configurations, see Purchase Methods.

Disabling Instance Termination Protection

If you have confirmed that an instance can be terminated, you can perform the following steps to disable instance termination protection before terminating the instance:
Disable instance termination protection for a single instance.
1. Log in to the MySQL console, select the required instance in the instance list, and choose More > Set Instance Termination Protection in the Operation column.

Note:
You can also choose More > Set Instance Termination Protection on the top-right corner of the instance details page.
2. In the pop-up instance termination protection window, select Disable and click OK to disable instance termination protection.
Disable instance termination protection for instances in batches.
1. Log in to the MySQL console, select multiple instances in the instance list, and choose More > Set Instance Termination Protection above the instance list.
2. In the pop-up instance termination protection window, select Disable and click OK to disable instance termination protection.

Documentation

Related APIs

API
Description
This API is used to create a TencentDB for MySQL instance in yearly/monthly subscription mode.
This API is used to create a TencentDB for MySQL instance in pay-as-you-go mode.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback