From 3ef96757dc03b157fb3b76297ffcb609138fac45 Mon Sep 17 00:00:00 2001 From: TomShawn <41534398+TomShawn@users.noreply.github.com> Date: Fri, 4 Sep 2020 13:16:39 +0800 Subject: [PATCH] cherry pick #3833 to release-4.0 Signed-off-by: ti-srebot --- br/backup-and-restore-tool.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/br/backup-and-restore-tool.md b/br/backup-and-restore-tool.md index 0e77baf0851df..cc6440be62a8b 100644 --- a/br/backup-and-restore-tool.md +++ b/br/backup-and-restore-tool.md @@ -11,9 +11,9 @@ aliases: ['/docs/stable/br/backup-and-restore-tool/','/docs/v4.0/br/backup-and-r ## Usage restrictions - BR only supports TiDB v3.1 and later versions. -- Currently, TiDB does not support backing up and restoring partitioned tables. -- Currently, you can perform restoration only on new clusters. +- BR supports restore on clusters of different topologies. However, the online applications will be greatly impacted during the restore operation. It is recommended that you perform restore during the off-peak hours or use `rate-limit` to limit the rate. - It is recommended that you execute multiple backup operations serially. Otherwise, different backup operations might interfere with each other. +- When BR restores data to the upstream cluster of TiCDC/Drainer, TiCDC/Drainer cannot replicate the restored data to the downstream. - BR supports operations only between clusters with the same [`new_collations_enabled_on_first_bootstrap`](/character-set-and-collation.md#collation-support-framework) value because BR only backs up KV data. If the cluster to be backed up and the cluster to be restored use different collations, the data validation fails. Therefore, before restoring a cluster, make sure that the switch value from the query result of the `select VARIABLE_VALUE from mysql.tidb where VARIABLE_NAME='new_collation_enabled';` statement is consistent with that during the backup process. - For v3.1 clusters, the new collation framework is not supported, so you can see it as disabled.