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 RestorationBacking up Data

Backing up Data

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-08-14 16:35:08
This document describes how to set backup parameters and download backup files via the TencentDB for PostgreSQL console.

Operation Scenarios

Currently, TencentDB for PostgreSQL High Availability Edition only supports physical backup:
Full backup: once a day at 01:00.
Incremental backup: for xlog files, backup will be performed once every 15 minutes or when the number of files reaches 60.
Data file retention period:Range: 7 to 1830 days.
Manual Backup: If you initiate a backup task manually, the task will start within one minute after you click OK.

Directions

1. Log in to the TencentDB for PostgreSQL Console and click an Instance ID to enter the instance details page.
2. The system will initiate automatic backups by default. For detailed information, please refer to the Automatic Backup Settings.
3. Backup data is available for download. On the instance management page, navigate to the Backup and Restoration section, then select either the Data Backup List or the Log Backup List. Choose the backup you wish to download and click Download in the Operation column.
Note:
Backup data in the Data Backup List is full backup, while that in the Log Backup List is incremental backup.

4. In the pop-up window, you can choose a VPC address or public network address to download the backup file.
Note:
To ensure data security, an address will be valid for 12 hours. After it expires, please refresh the page to get a new address. Please access a VPC address in a VPC.

5. In addition to automatic system backups, users can initiate manual backup tasks on demand. Simply click the Manual Backup button on the Backup and Restoration page to start a manual backup.
Note:
You can not initiate a manual backup during the execution of the routine auto backup tasks.
Manual backups can be deleted from the backup list to free up backup space, avoiding space waste and occupancy. If not manually deleted, they will be kept forever.

6. In the Manual Backup dialog, click OK.

Note:
The creation time of a manual backup relates to the actual capacity of the instance. Larger capacity results in longer creation time.

FAQs

Can backups exceeding the retention period still be downloaded or restored?

Expired automatic backup sets will be automatically deleted and cannot be downloaded or restored. You can manually backup instance data in the console, and manual backups are always saved.

Can backups be manually deleted?

Automatic backups within 7 days cannot be deleted. Those beyond 7 days can be deleted as needed, and the system will also delete automatic backups based on their corresponding retention durations. Manual backups can be manually deleted from the backup list; otherwise, they will be retained permanently.

Can data and log backups be disabled?

No, they cannot be disabled. However, you can lower the backup frequency and delete unnecessary to reduce the backup space usage.

How can I reduce backup space overhead?

Delete unnecessary manual backup data.
Lower the automatic backup frequency for non-core service data (at least twice a week).
Topik sebelumnya: Backup Principles and SolutionsTopik selanjutnya: Downloading Backup

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan