tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Release Notes and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Overview
Product Strengths
Use Cases
Storage Engine
Product Series
Product Versions
Specifications and Performance
Read/Write Separation
Multi-AZ Deployment
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
Pricing Center
Instance Purchasing
Renewal (Yearly/Monthly Subscription)
Refund (Yearly/Monthly Subscription)
Overdue Payments
Switching from Pay-as-You-Go to Yearly/Monthly Subscription
Getting Started
Quickly Creating an Instance
Connecting to Redis Instance
Operation Guide
Operation Overview
Connecting to a Database Instance
Managing Instances
Upgrade Instance
Management Node (Redis/ValKey Edition)
Multi-AZ Deployment Management
Backup and Restoration
Managing Accounts
Parameter Configuration
Slow Query
Access Management
Network and Security
Monitoring and Alarms
Event Management (Redis/ValKey Edition)
Data Migration
Global Replication for Redis Edition
Database Audit
Performance Optimization
Sentinel Mode
Development Guidelines
Naming Rules
Basic Usage Guidelines
Design Principles of Key and Value
Command Usage Guidelines
Design Principles of Client Programs
Connection Pool Configuration
Command Reference
Command Reference Overview
Redis Edition and Valkey Edition Command Compatibility
Version Command Usage Differences
Differences Between the Proxy Architecture and Direct Connection Mode
More Command Operations (Redis/Valkey Edition)
Memcached Edition Command Compatibility
Practical Tutorial
Building TencentDB for Redis® Client Monitoring Based on Spring Boot
Redis Client Connection Configuration Policy and Practice
Global SCAN Guide for Cluster Architecture
Eliminating Instances Securely
Hot Key and Big Key
AZ Migration Scheme
Troubleshooting
Connection Exception
Exception Analysis and Solution of Redisson Client Timeout Reconnection
Performance Troubleshooting and Fine-Tuning
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Parameter Management APIs
Other APIs
Backup and Restoration APIs
Region APIs
Monitoring and Management APIs
Log APIs
Data Types
Error Codes
FAQs
General
Connection and Login
Purchase
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Eliminate/Restore Instances

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-04-01 10:51:29

Overview

The "Take Offline or Restore Recycle Bin Instances" feature is used to manage database instances that have been returned or destroyed and are within the retention period in the recycle bin. This operation provides you with an important data security buffer to rectify accidental operations or perform data restoration.
Restore accidentally deleted instance (Restore Instance)
When you accidentally return a yearly/monthly subscription instance or destroy a pay-as-you-go instance, you can fully restore it within the 7-day retention period after the instance enters the recycle bin using the restoration feature. After the database instance is restored, its configuration, data, and connection address will remain unchanged, and services will be immediately available.
Actively and thoroughly destroy data (Decommission Instance)
If you confirm that an instance in the recycle bin and its data are no longer needed at all, you can actively perform the "decommission" operation. This operation will immediately and permanently delete the instance and all its data, release the resources it occupies, and it cannot be restored. It applies to scenarios that require strict implementation of data cleanup policies or immediate release of resources.

Recycle Bin Retention Period Description

Yearly/monthly subscription instances, after the renewal grace period (7 days) is exceeded or they are actively returned, will enter the recycle bin and be retained for 7 days. Pay-as-you-go instances, after the overdue payments period (24 hours) expires or they are actively destroyed, will be retained in the recycle bin for 7 days. During the retention period in the recycle bin, the handling mechanism for instances is as shown in the table below.
Duration
Handling Mechanism
Within 7 days in the recycle bin
Cloud database resources become unavailable after shutdown. The instances are isolated in the recycle bin.
Restorable: The instance can be fully restored using the restoration feature.
Decommissionable: Directly decommission the instance immediately to permanently destroy data.
At the end of the 7th day, cloud database resources in the recycle bin are automatically cleaned up and cannot be manually restored.
Note:
On the 7th day after shutdown, Tencent Cloud will notify the user of the resource release time via voice call (the actual receiving method is subject to the subscription configuration in Message Center). On the 8th day after shutdown, the user will be notified of resource release.
From the 8th to the 15th day in the recycle bin
Cloud database instances are cleared from the recycle bin, and instance backups are stored in the backend for 8 days. To restore instances, contact Tencent Cloud engineers.
At the end of the 15th day after shutdown, all backup data will be deleted and cannot be restored.
15 days after shutdown
Cloud database resources are completely terminated, and all data is deleted and cannot be restored.

Prerequisites

The instance has been released and isolated in the recycle bin.
Your Tencent Cloud account balance is sufficient.

Restoring one isolated instance

2. On the left sidebar, select Tencent Cloud Distributed Cache > Recycle Bin.
3. Above the Instance List page on the right, select the target region.
4. On the Recycle Bin page on the right, you can see the list of instances in the recycle bin, all of which are in the Isolated status.
5. In the instance list in the recycle bin, find the target instance and click Start Up in the Operation column.
6. Confirm the instance information and restore it.
If the instance is a yearly/monthly subscription instance, in the Renew Selected Instances dialog box, you need to perform the following operations and click OK to restore it.
Click View Details to confirm the instance information.
In Renewal Period, select the duration of the instance renewal by full month or full year.
Next to Total Fees, confirm the total amount for the instance renewal.
If the instance is pay-as-you-go, confirm the instance information and click OK in the Start Instance window to restore it.
Note:
As Tencent Cloud Distributed Cache is an in-memory database, to use the batch instance restoration feature, submit a ticket for application.

Restore multiple isolated instances (yearly/monthly subscription)

1. In the instance list in the recycle bin, select all instances that require restoration.

2. Click Renew above the list. In the Renew Selected Instances dialog box, perform the following operations.
Click View Details to confirm the instance information.
In Renewal Period, select the duration of the instance renewal by full month or full year.
Next to Total Fees, confirm the total amount for the instance renewal.
3. Click OK, on the Confirm the Following Product Information page, confirm the product list and verify the renewal amount. Click Submit Order, select a payment method, and click Next. After successful payment, the renewal is completed. The instance will be automatically unisolated and removed from the recycle bin. In the left sidebar, select Instance List to view the unisolated and restored instance in the instance list.

Eliminating an Instance

2. In the left sidebar, choose Distributed Cache (Redis-compatible) > Recycle Bin.
3. Above the Instance List page on the right, select the target region.
4. You can view the list of instances in the recycle bin, all of which are in the Isolated state. Locate the instance to be shut down and click Shut Down Immediately in its Operation column.



5. In the Shut Down Immediately dialog box, confirm the information of the instance to be shut down, and click OK to directly terminate the instance resources.
Note:
After the instance is terminated, all its data will be cleared and cannot be recovered. Back up your data first.

Related APIs

API
Functional Description
Restores an isolated instance.
Shuts down an instance in the recycle bin immediately.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백