From 38438ed6780b6a758e142d6735beb3c5866c4496 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Wed, 20 Dec 2023 11:54:22 +0800 Subject: [PATCH] Update tidb-lightning-physical-import-mode.md (#15792) (#15804) --- tidb-lightning/tidb-lightning-physical-import-mode.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/tidb-lightning/tidb-lightning-physical-import-mode.md b/tidb-lightning/tidb-lightning-physical-import-mode.md index 1615f1f884d63..1cc3ad215d66c 100644 --- a/tidb-lightning/tidb-lightning-physical-import-mode.md +++ b/tidb-lightning/tidb-lightning-physical-import-mode.md @@ -93,3 +93,9 @@ It is recommended that you allocate CPU more than 32 cores and memory greater th - When you use TiDB Lightning with TiCDC, note the following: - TiCDC cannot capture the data inserted in the physical import mode. + +- When you use TiDB Lightning with BR, note the following: + + - When BR backs up snapshots of tables that are being imported by TiDB Lightning, it might result in inconsistent backup data for those tables. + - When BR backs up data using AWS EBS volume snapshots, TiDB Lightning might fail to import data. + - Point-in-time recovery (PITR) cannot back up data imported by TiDB Lightning.