When will BR support partitioned table backup by partition?

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 请问什么时候br支持分区表按分区备份

| username: tidb狂热爱好者

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots / Logs / Monitoring]

There is an archiving business. Using TiDB for archiving. Hope to use partitioned tables for partitioned backups. This makes data analysis more convenient.

Currently, it is one table per month. Then each month, it is backed up to S3.
So, create new table; rename current table to old table; rename new table to current table; backup old table.

| username: tidb狂热爱好者 | Original post link

The data volume is relatively large, 10T to 20T per month. I hope it can support BR backup for partitioned tables. Creating monthly tables is not good for data analysis.

| username: 这里介绍不了我 | Original post link

Good question, keep following.

| username: Kongdom | Original post link

Mark it, it is indeed a good feature request~

| username: Jellybean | Original post link

BR does not support backup and recovery of partitions; the smallest granularity is table-level backup and recovery.

| username: YuchongXU | Original post link

Not supported, looking forward to the update.

| username: redgame | Original post link

There are not many applications for this kind of scenario. It’s very niche.

| username: 小于同学 | Original post link

It is not supported.

| username: DBAER | Original post link

Mark

| username: porpoiselxj | Original post link

Just write a program to dump it according to the protocol that Lightning can recognize. When needed, you can use Lightning to restore it to a single table directly. That’s what we do.

| username: TiDBer_rvITcue9 | Original post link

Not supported

| username: gary | Original post link

Not supported

| username: WalterWj | Original post link

Currently, I have submitted an FRM internally, :thinking: and changed it to a product requirement.

| username: TiDBer_5cwU0ltE | Original post link

I feel it can also be done this way:
Backup; truncate table; put the backup on S3. Would this be more efficient for the database?

| username: Soysauce520 | Original post link

Marking this for later, waiting for implementation.

| username: tidb狂热爱好者 | Original post link

Can you elaborate?

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.