From 4067d3dd80b95f391cd75dbd7320871ca26ea780 Mon Sep 17 00:00:00 2001 From: JoyinQ <56883733+Joyinqin@users.noreply.github.com> Date: Tue, 8 Sep 2020 15:26:06 +0800 Subject: [PATCH 1/2] cherry pick #3839 to release-3.1 Signed-off-by: ti-srebot --- br/backup-and-restore-faq.md | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/br/backup-and-restore-faq.md b/br/backup-and-restore-faq.md index f3c134fa41b2f..10153808b8619 100644 --- a/br/backup-and-restore-faq.md +++ b/br/backup-and-restore-faq.md @@ -41,11 +41,20 @@ Running BR with the root access might fail due to the disk permission, because t ## What should I do to resolve the `Io(Os...)` error? Almost all of these problems are system call errors that occur when TiKV writes data to the disk. You can check the mounting method and the file system of the backup directory, and try to back up data to another folder or another hard disk. -  + For example, you might encounter the `Code: 22(invalid argument)` error when backing up data to the network disk built by `samba`. +<<<<<<< HEAD +======= +## What should I do to handle the `rpc error: code = Unavailable desc =...` error occurred in BR? + +This error might occur when the capacity of the cluster to restore (using BR) is insufficient. You can further confirm the cause by checking the monitoring metrics of this cluster or the TiKV log. + +To handle this issue, you can try to scale out the cluster resources, reduce the concurrency during restore, and enable the `RATE_LIMIT` option. + +>>>>>>> 04715f3... br: add use constraint with TiCDC and Drainer (#3839) ## Where are the backed up files stored when I use `local` storage? -  + When you use `local` storage, `backupmeta` is generated on the node where BR is running, and backup files are generated on the Leader nodes of each Region. ## How about the size of the backup data? Are there replicas of the backup? @@ -53,3 +62,11 @@ When you use `local` storage, `backupmeta` is generated on the node where BR is During data backup, backup files are generated on the Leader nodes of each Region. The size of the backup is equal to the data size, with no redundant replicas. Therefore, the total data size is approximately the total number of TiKV data divided by the number of replicas. However, if you want to restore data from local storage, the number of replicas is equal to that of the TiKV nodes, because each TiKV must have access to all backup files. + +## What should I do when BR restores data to the upstream cluster of TiCDC/Drainer? + ++ **The data restored using BR cannot be replicated to the downstream**. This is because BR directly imports SST files but the downstream cluster currently cannot obtain these files from the upstream. + ++ Data from BR before v4.0.3 might cause unexcepted DDL executions. Therefore, if you need to perform restore on the upstream cluster of TiCDC/Drainer, add all tables restored using BR to the TiCDC/Drainer block list. + +You can use [`filter.rules`](https://github.com/pingcap/ticdc/blob/7c3c2336f98153326912f3cf6ea2fbb7bcc4a20c/cmd/changefeed.toml#L16) to configure the block list for TiCDC and use [`syncer.ignore-table`](/tidb-binlog/tidb-binlog-configuration-file.md#ignore-table) to configure the block list for Drainer. From 88a17c185b4df4c607e62d88beec6388fd4fde0f Mon Sep 17 00:00:00 2001 From: TomShawn <41534398+TomShawn@users.noreply.github.com> Date: Tue, 8 Sep 2020 15:36:40 +0800 Subject: [PATCH 2/2] Update backup-and-restore-faq.md --- br/backup-and-restore-faq.md | 15 +++------------ 1 file changed, 3 insertions(+), 12 deletions(-) diff --git a/br/backup-and-restore-faq.md b/br/backup-and-restore-faq.md index 10153808b8619..318895ddee7b6 100644 --- a/br/backup-and-restore-faq.md +++ b/br/backup-and-restore-faq.md @@ -44,15 +44,6 @@ Almost all of these problems are system call errors that occur when TiKV writes For example, you might encounter the `Code: 22(invalid argument)` error when backing up data to the network disk built by `samba`. -<<<<<<< HEAD -======= -## What should I do to handle the `rpc error: code = Unavailable desc =...` error occurred in BR? - -This error might occur when the capacity of the cluster to restore (using BR) is insufficient. You can further confirm the cause by checking the monitoring metrics of this cluster or the TiKV log. - -To handle this issue, you can try to scale out the cluster resources, reduce the concurrency during restore, and enable the `RATE_LIMIT` option. - ->>>>>>> 04715f3... br: add use constraint with TiCDC and Drainer (#3839) ## Where are the backed up files stored when I use `local` storage? When you use `local` storage, `backupmeta` is generated on the node where BR is running, and backup files are generated on the Leader nodes of each Region. @@ -63,10 +54,10 @@ During data backup, backup files are generated on the Leader nodes of each Regio However, if you want to restore data from local storage, the number of replicas is equal to that of the TiKV nodes, because each TiKV must have access to all backup files. -## What should I do when BR restores data to the upstream cluster of TiCDC/Drainer? +## What should I do when BR restores data to the upstream cluster of Drainer? + **The data restored using BR cannot be replicated to the downstream**. This is because BR directly imports SST files but the downstream cluster currently cannot obtain these files from the upstream. -+ Data from BR before v4.0.3 might cause unexcepted DDL executions. Therefore, if you need to perform restore on the upstream cluster of TiCDC/Drainer, add all tables restored using BR to the TiCDC/Drainer block list. ++ Therefore, if you need to perform restore on the upstream cluster of TiCDC/Drainer, add all tables restored using BR to the Drainer block list. -You can use [`filter.rules`](https://github.com/pingcap/ticdc/blob/7c3c2336f98153326912f3cf6ea2fbb7bcc4a20c/cmd/changefeed.toml#L16) to configure the block list for TiCDC and use [`syncer.ignore-table`](/tidb-binlog/tidb-binlog-configuration-file.md#ignore-table) to configure the block list for Drainer. +You can use [`syncer.ignore-table`](/tidb-binlog/tidb-binlog-configuration-file.md#ignore-table) to configure the block list for Drainer.