Product Introduction

Overview

Concepts

Cluster Architecture

Strengths

Scenarios

Purchase Guide

Billing Overview

Renewal Instructions

Overdue Policy

Refund Instructions

Configuration Adjustment Billing Instructions

Getting Started

Using Tencent Cloud TCHouse-D Through the Console

Using Tencent Cloud TCHouse-D Through a Client

Operation Guide

Cluster Operation

Monitoring and Alarm Configuration

Account Privilege Management

Data Management

Query Management

Modify Configurations

Node Management

Log Analysis

SQL Studio

Enabling Resource Isolation

Development Guide

Design of Data Table

Importing Data

Exporting Data

Basic Feature

Query Optimization

Ecological Expansion Feature

API Documentation

History

Introduction

API Category

Making API Requests

Cluster Operation APIs

Database and Table APIs

Cluster Information Viewing APIs

Hot-Cold Data Layering APIs

Database and Operation Audit APIs

User and Permission APIs

Resource Group Management APIs

Data Types

Error Codes

Cloud Ecosystem

Granting CAM Policies to Sub-accounts

Query Acceleration for Tencent Cloud DLC

Practical Tutorial

Basic Feature Usage

Advanced Features Usage

Resource Specification Selection and Optimization Suggestions

Naming Specifications and Limits to the Database and Data Table

Table Design and Data Import

Query Optimization

Suggested Usage to Avoid

Accessing TCHouse-D via JDBC over the Public Network

Performance Testing

TPC-H Performance Testing

SSB Performance Testing

TPC-DS Performance Testing

FAQs

Common Operational Issues

Common Errors

Glossary

Product Policy

Service Level Agreement

Data Processing And Security Agreement

Data Backup

PDF

Focus Mode

Font Size

Last updated: 2024-06-27 10:50:59

Tencent Cloud TCHouse-D supports the feature of transferring current data as a file through Broker Backup to a remote storage system and restoring the data to any cluster from the remote storage system. This feature can be used for one-time or regular snapshot backups and also implementations of data migration between different clusters.
Operation Guide
1. Enter Cluster List and click Cluster ID/Name you want to back up.
2. On the cluster management page, click Data Management > Backup And Restore on the left to go to the Backup Recovery page. If the Backup service has not been turned on, authorization should be performed first, and a COS bucket for storing data should be selected.
﻿
3. After enabling the Backup service, the available operations include: periodic backup, one-time backup, cross-cluster data migration. The Backup feature allows you to choose any database/table to backup, and the data will be stored permanently after a successful backup.
Note:
One-time Backup does not affect the periodic backup policy, but only one BACKUP or RESTORE task can be executed for the same database table at the same time.
The COS bucket path supports changes. After the changes, the new backup snapshot will be written to the new COS bucket, and the backup snapshot stored in the old COS bucket can still be restored.
After backing up the data to the COS, it will be stored as a single copy.
﻿
Data Backup Feature Description
You can perform data backup and data migration operations on the Backup Recovery page in Tencent Cloud TCHouse-D. Using the data backup feature, you can perform a one-time backup of the data or plan periodic backup tasks.
Note:
If the Backup or Restore task fails due to cluster restart (such as Scale-out, Scale-in, vertical configuration, parameter configuration operations, etc.), try again after system restart.
One-time Data Backup
When creating a one-time backup task, you can choose the execution method: scheduled execution, or immediate execution.
The granularity of backup can be chosen: backup by table, backup by database, or full backup.
﻿
Periodic Data Backup
When creating a periodic backup task, you can configure items including: effective cycle, scheduling cycle, and execution time. After the successful creation, the backup task will be executed at the specified time according to the scheduling cycle, within the effective cycle.
One-time Backup does not affect the periodic backup policy, but only one BACKUP or RESTORE task can be executed for the same database table at the same time.
Supports the creation of multiple periodic backup tasks, but if multiple tasks perform backup on the same table at the same time, subsequent tasks will all report errors. In order to ensure data integrity, you can re-backup through the "One-time Backup Data" feature after the previous backup task ends.
﻿