Release Notes
Product Announcements
Terminating Instance
Scenarios
According to your workload requirements, you can return the pay-as-you-go instances and yearly/monthly subscription instances by yourself in the console.
After a yearly/monthly subscription instance is returned, the instance will be moved to the cloud database recycle bin and retained for seven days. During this period, the instance will be inaccessible. If you want to restore the instance, you can renew it in the recycle bin.
After a Pay-as-you-go instance is returned, the instance is moved to the cloud database recycle bin and retained for 24 hours. During this period, the instance is inaccessible. If you want to restore the instance, you can renew it in the recycle bin.
After a self-service return, once the instance status changes to "Isolated", it will no longer incur fees associated with the instance.
Precautions
After instance termination protection is enabled, terminating instances is not supported. To terminate an instance, disable instance termination protection first. For details, see Setting Instance Termination Protection.
After the instance status enters "Isolated", the instance will be inaccessible. If the instance has associated read-only instances: The read-only instances can still be accessed normally.
After the instance is terminated, its data cannot be retrieved, and its backup files will also be terminated. Data recovery on the cloud is impossible. Transfer your backup files to a safe location in advance. It is suggested to configure backup retention.
After an instance is terminated, its IP resources will also be released. If the instance has related read-only or disaster recovery instances:
The read-only instances will also be terminated.
The disaster recovery instance will disconnect the synchronization connection and automatically upgrade to the primary instance.
Refund processing after instance termination:
The five-day unconditional self-service refund is returned to the Tencent Cloud account.
The common self-service refund is returned to your Tencent Cloud account based on the proportion of cash and free credits used for the purchase.
For promotion channel orders, 25% of the actually paid order amount will be charged as the refund fee. Such orders do not support self-service refunds. You can submit a ticket to apply for a refund.
Operation Steps
1. Log in to the MySQL console. On the instance list page, select the target instance. In the Operation column, choose More > Terminate/Return or Terminate Instance.
2. In the pop-up dialog box, complete the Backup File Retention settings, and click Confirm Termination.
Note:
The read-only analysis engine does not involve setting the backup file retention feature.
Backup File Retention | Description |
Do not retain | If you select Do not retain, backups will be terminated simultaneously after instance termination and will not be saved. |
Retain | If you select Retain, backups within the specified scope will be retained after the instance is terminated. The scope options are as follows: Retain all: Retain all backups generated by the instance in the current region. You can choose whether to retain the binlog files. Retain the latest one: Retain the latest 1 backup generated by the instance in the current region. By default, binlog files cannot be retained. Retain those within the specified time range: Retain backups generated by the instance in the current region and after the selected time. You can choose whether to retain the binlog files. For example, you can retain backups generated after April 28, 2025. |
3. After the operation is completed, the instance is moved to the recycle bin, and its status changes to Isolating.
Note:
If you choose to retain backup files, after the instance is taken offline from the recycle bin, the retained backup files can be queried and downloaded under Database Backup > Backup List > Backups of Terminated Instances. Subsequent instructions regarding querying and downloading retained backup files are as follows:
After instance termination, backup files that comply with the retention policy will not immediately appear in the list under Database Backup > Backup List > Backups of Terminated Instances.
After instance termination, the system requires time to transfer the backup files in the background, which delays the display of backup files for terminated instances. If you cannot find the target backup file in the list under Backups of Terminated Instances, please refresh and check later.
During the delay, you can still view the backup files in Database Backup > Backup List > Data Backup List.
If the backup file is still not listed under Backups of Terminated Instances after 24 hours, please submit a ticket for assistance.
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback