From 0ff4b9c70741b4dba6456e077ea7f30815733feb Mon Sep 17 00:00:00 2001 From: Jianjun Liao Date: Thu, 26 Jun 2025 13:00:15 +0800 Subject: [PATCH 1/2] pitr restore mode Signed-off-by: Jianjun Liao --- br/br-pitr-guide.md | 2 ++ br/br-snapshot-guide.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/br/br-pitr-guide.md b/br/br-pitr-guide.md index 2b0e7b202b7c3..30cd3f55237b0 100644 --- a/br/br-pitr-guide.md +++ b/br/br-pitr-guide.md @@ -117,6 +117,8 @@ Restore KV Files <-------------------------------------------------------------- *** ["restore log success summary"] [total-take=xxx.xx] [restore-from={TS}] [restore-to={TS}] [total-kv-count=xxx] [total-size=xxx] ``` +During the restore, the `Table Mode` of the restored table will be set to `restore`, and users will be prohibited from performing any read and write operations on the table in `Restore Mode`. When the data restore is completed, the Table Mode will be automatically reset to the `normal` state, and users can read and write the table normally, thereby improving task stability and data consistency during data restore. + ## Clean up outdated data As described in the [Usage Overview of TiDB Backup and Restore](/br/br-use-overview.md): diff --git a/br/br-snapshot-guide.md b/br/br-snapshot-guide.md index 170df2f4602ee..f0aba02fab1df 100644 --- a/br/br-snapshot-guide.md +++ b/br/br-snapshot-guide.md @@ -103,6 +103,8 @@ Restore Pipeline <-------------------------------------------------------------- *** ["Full Restore success summary"] [total-ranges=20] [ranges-succeed=20] [ranges-failed=0] [merge-ranges=7.546971ms] [split-region=343.594072ms] [restore-files=1.57662s] [default-CF-files=6] [write-CF-files=14] [split-keys=9] [total-take=4.344617542s] [total-kv=5] [total-kv-size=327B] [average-speed=75.27B/s] [restore-data-size(after-compressed)=4.813kB] [Size=4813] [BackupTS=435844901803917314] ``` +During the restore, the `Table Mode` of the restored table will be set to `restore`, and users will be prohibited from performing any read and write operations on the table in `Restore Mode`. When the data restore is completed, the Table Mode will be automatically reset to the `normal` state, and users can read and write the table normally, thereby improving task stability and data consistency during data restore. + ### Restore a database or a table BR supports restoring partial data of a specified database or table from backup data. This feature allows you to filter out unwanted data and back up only a specific database or table. From 1d76624aff2e4e9e954644c4be67f2d6600ede12 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 27 Jun 2025 09:41:33 +0800 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- br/br-pitr-guide.md | 2 +- br/br-snapshot-guide.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/br/br-pitr-guide.md b/br/br-pitr-guide.md index 30cd3f55237b0..7750ca6f3bcbd 100644 --- a/br/br-pitr-guide.md +++ b/br/br-pitr-guide.md @@ -117,7 +117,7 @@ Restore KV Files <-------------------------------------------------------------- *** ["restore log success summary"] [total-take=xxx.xx] [restore-from={TS}] [restore-to={TS}] [total-kv-count=xxx] [total-size=xxx] ``` -During the restore, the `Table Mode` of the restored table will be set to `restore`, and users will be prohibited from performing any read and write operations on the table in `Restore Mode`. When the data restore is completed, the Table Mode will be automatically reset to the `normal` state, and users can read and write the table normally, thereby improving task stability and data consistency during data restore. +During restore, the restored table's table mode is set to `restore`, which prevents you from performing any read or write operations. After data restore completes, the table mode is automatically reset to `normal`, and you can read and write the table normally. This improves task stability and data consistency. ## Clean up outdated data diff --git a/br/br-snapshot-guide.md b/br/br-snapshot-guide.md index f0aba02fab1df..18a868c310572 100644 --- a/br/br-snapshot-guide.md +++ b/br/br-snapshot-guide.md @@ -103,7 +103,7 @@ Restore Pipeline <-------------------------------------------------------------- *** ["Full Restore success summary"] [total-ranges=20] [ranges-succeed=20] [ranges-failed=0] [merge-ranges=7.546971ms] [split-region=343.594072ms] [restore-files=1.57662s] [default-CF-files=6] [write-CF-files=14] [split-keys=9] [total-take=4.344617542s] [total-kv=5] [total-kv-size=327B] [average-speed=75.27B/s] [restore-data-size(after-compressed)=4.813kB] [Size=4813] [BackupTS=435844901803917314] ``` -During the restore, the `Table Mode` of the restored table will be set to `restore`, and users will be prohibited from performing any read and write operations on the table in `Restore Mode`. When the data restore is completed, the Table Mode will be automatically reset to the `normal` state, and users can read and write the table normally, thereby improving task stability and data consistency during data restore. +During restore, the restored table's table mode is set to `restore`, which prevents you from performing any read or write operations. After data restore completes, the table mode is automatically reset to `normal`, and you can read and write the table normally. This improves task stability and data consistency. ### Restore a database or a table