From 2eed2d8baa661d0f610c060d8a0832a2ff8b9db4 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Tue, 19 Dec 2023 21:26:17 +0800 Subject: [PATCH] Update tidb-lightning/tidb-lightning-physical-import-mode.md --- tidb-lightning/tidb-lightning-physical-import-mode.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-lightning/tidb-lightning-physical-import-mode.md b/tidb-lightning/tidb-lightning-physical-import-mode.md index 708ce5b2a9b40..49b7864e9d884 100644 --- a/tidb-lightning/tidb-lightning-physical-import-mode.md +++ b/tidb-lightning/tidb-lightning-physical-import-mode.md @@ -97,4 +97,4 @@ It is recommended that you allocate CPU more than 32 cores and memory greater th - 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 based on the AWS EBS volume snapshots, TiDB Lightning might fail to import data. - - Point-in-Time Recovery (PiTR) can not back up data imported by TiDB Lightning. + - Point-In-Time Recovery (PITR) can not back up data imported by TiDB Lightning.