tencent cloud

TencentDB for PostgreSQL

Release Notes and Announcements
Release Notes
Product Announcements
Product Introduction
Overview
Features
Strengths
Scenarios
Information Security
Regions and AZs
Product Feature List
Large version lifecycle description
MSSQL Compatible Version
Billing
Billing Overview
Instance Type and Specification
Purchase Methods
Refund
Overdue Payments
Backup Space Billing
Database Audit Billing Overview
Getting Started
Creating TencentDB for PostgreSQL Instance
Connecting to TencentDB for PostgreSQL Instance
Managing TencentDB for PostgreSQL Instance
Importing Data
Migrating Data with DTS
Kernel Version Introduction
Kernel Version Overview
Kernel Version Release Notes
Viewing Kernel Version
Proprietary Kernel Features
Database Audit
Audit Service Description
Activating Audit Service
View Audit Logs
Modify audit services
Audit Performance Description
User Guide
Instance Management
Upgrading Instance
CPU Elastic Scaling
Read-Only Instance
Account Management
Database Management
Parameter Management
Log Management and Analysis
Backup and Restoration
Data Migration
Extension Management
Network Management
Access Management
Data Security
Tenant and Resource Isolation
Security Groups
Monitoring and Alarms
Tag
AI Practice
Using the Tencentdb_ai Plug-In to Call Large Models
Building Ai Applications with the Tencentdb Ai Plug-In
Combining Supabase to Quickly Build Backend Service Based on TencentDB for PostgreSQL
Use Cases
postgres_fdw Extension for Cross-database Access
Automatically Creating Partition in PostgreSQL
Searching in High Numbers of Tags Based on pg_roaringbitmap
Querying People Nearby with One SQL Statement
Configuring TencentDB for PostgreSQL as GitLab's External Data Source
Supporting Tiered Storage Based on cos_fdw Extension
Implement Read/Write Separation via pgpool
Implementing Slow SQL Analysis Using the Auto_explain Plugin
Using pglogical for Logical Replication
Using Debezium to Collect PostgreSQL Data
Set Up a Remote Disaster Recovery Environment for PostgreSQL Locally on CVM
Read-Only Instance and Read-Only Group Practical Tutorial
How to Use SCF for Scheduled Database Operations
Fix Table Bloat
Performance White Paper
Test Methods
Test Results
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Read-Only Instance APIs
Backup and Recovery APIs
Parameter Management APIs
Security Group APIs
Performance Optimization APIs
Account APIs
Specification APIs
Network APIs
Data Types
Error Codes
FAQs
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us
DokumentasiTencentDB for PostgreSQLUser Guide Backup and RestorationCloning Instance

Cloning Instance

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2026-03-31 11:41:25
If you need to perform data recovery, you can use the clone PostgreSQL instance feature to quickly recover instance data from a backup to a newly purchased PostgreSQL instance. This article introduces you to how to perform the clone operation via the TencentDB for PostgreSQL console.

Scenarios

TencentDB for PostgreSQL provides the clone instance feature, which supports restoring an instance to any point in time within the log backup retention period through cloning, and also supports restoring to specified physical backup sets. The cloning process first creates a new instance based on the user-selected point in time using backup data. After the new instance is verified, users can migrate data back to the source instance via the DTS data transmission service, or directly use the cloned new instance.

Cloning Method

Point-in-time cloning: Restores the instance to any point in time. The selection range for the point in time is determined by the log retention period you configured.
By backup set cloning: Restores the instance to any physical backup set. The selection range for backup sets is determined by the data backup retention period you configured.

New Instance Fees

The billing mode for the new clone instance can be selected by the user during cloning, consistent with the purchase of an instance.
Billing for the new cloned instance commences only after the cloning process completes successfully.

Prerequisites

The source instance status must be running.
If the clone method is selected as by backup set, the source instance must have completed physical backups. The backup status can be viewed in the backup list on the console.
The account balance must be greater than 0.

Must-Knows

The disk space size of the new cloned instance must be greater than the data size to be cloned; otherwise, cloning may result in failure.
Note:
To leave sufficient space for restoring compressed backup files, the system defaults to the new instance specifications being at least four times the size of the compressed files. After cloning is complete, scale-in can be performed. For specific steps, see How to Scale In.
The database version of the new cloned instance must be the same as that of the source instance.
For instances with used capacity exceeding 6TB, please submit a ticket for data recovery.

Operation Steps

1. Log in to the PostgreSQL Console. In the instance list, click Instance ID or Manage in the Operation column to go to the instance management page.
2. On the instance management page, choose Backup and Restoration > Data Backup List page, and click Clone in the upper-left corner.

3. Go to the purchase page, select the clone method and corresponding configurations for the cloned instance. After confirming the information, click Buy Now.
Point-in-time recovery: allows restoring a database instance from the source database instance to a specific point in time, with the selectable time range being the last 7 days.
Backup set-based recovery: allows restoring a new instance from a specified backup set. The selectable range of backup sets is determined by your configured data backup retention period.
Note:
The backup retention period can be viewed in the backup list in the console.
4. After the purchase is successful, you can view the details of the cloned instance on the instance list page.

FAQs

Will the cloning process impact access to the source instance?

The cloning process uses the original backup set and log files uploaded to COS for recovery, which does not affect access to the source instance.

What to Do If the Disk Space of the Newly Cloned Instance Is Too Large?

To leave sufficient space for restoring compressed backup files, the system defaults to the new instance storage specifications being at least four times the size of the compressed files. After cloning is complete, scale-in can be performed to avoid space waste. You can log in to the console, go to the instance details, click Adjust Configuration in the configuration information, and modify the instance specifications and disk capacity.

Topik sebelumnya: Downloading BackupTopik selanjutnya: Automatic Backup Settings

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan