From b6e792c7f72074477b89180ca2836a5792106603 Mon Sep 17 00:00:00 2001 From: Jianjun Liao Date: Thu, 26 Jun 2025 13:00:15 +0800 Subject: [PATCH 1/3] 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 27aecb8b9e196..fce5cab29fb7e 100644 --- a/br/br-pitr-guide.md +++ b/br/br-pitr-guide.md @@ -100,6 +100,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 80e04a2207e4c..e636f989fd93f 100644 --- a/br/br-snapshot-guide.md +++ b/br/br-snapshot-guide.md @@ -83,6 +83,8 @@ Full Restore <------------------------------------------------------------------ *** ["Full Restore success summary"] *** [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 d1e1d6a09ad56b404dc091df8fba595f7444d8cc Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 27 Jun 2025 09:41:33 +0800 Subject: [PATCH 2/3] 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 fce5cab29fb7e..7f258241689cf 100644 --- a/br/br-pitr-guide.md +++ b/br/br-pitr-guide.md @@ -100,7 +100,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 e636f989fd93f..0434b25d36d00 100644 --- a/br/br-snapshot-guide.md +++ b/br/br-snapshot-guide.md @@ -83,7 +83,7 @@ Full Restore <------------------------------------------------------------------ *** ["Full Restore success summary"] *** [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 From cc534c755756383cf325f08992aa2acf805b9e50 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 7 Nov 2025 12:12:22 +0800 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: Lilian Lee --- 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 7f258241689cf..19ea71c6fceae 100644 --- a/br/br-pitr-guide.md +++ b/br/br-pitr-guide.md @@ -100,7 +100,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 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. +During data restore, the table mode of the target table is automatically set to `restore`. Tables in `restore` mode do not allow any read or write operations. After data restore is complete, the table mode automatically switches back to `normal`, and you can read and write the table normally. This mechanism ensures task stability and data consistency throughout the restore process. ## Clean up outdated data diff --git a/br/br-snapshot-guide.md b/br/br-snapshot-guide.md index 0434b25d36d00..d2602b418e2db 100644 --- a/br/br-snapshot-guide.md +++ b/br/br-snapshot-guide.md @@ -83,7 +83,7 @@ Full Restore <------------------------------------------------------------------ *** ["Full Restore success summary"] *** [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 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. +During data restore, the table mode of the target table is automatically set to `restore`. Tables in `restore` mode do not allow any read or write operations. After data restore is complete, the table mode automatically switches back to `normal`, and you can read and write the table normally. This mechanism ensures task stability and data consistency throughout the restore process. ### Restore a database or a table