Skip to content

Commit 589d422

Browse files
authored
br: fix description about case-sensitive and insensitive (#20438)
1 parent e65e0e0 commit 589d422

File tree

1 file changed

+13
-14
lines changed

1 file changed

+13
-14
lines changed

br/backup-and-restore-overview.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -145,26 +145,25 @@ This section introduces the BR compatibility information for all [Long-Term Supp
145145

146146
> **Note:**
147147
>
148-
> Known issue: Starting from version v7.2.0, fields of some system tables in newly created clusters become case-sensitive. However, for clusters that are **upgraded online** from versions earlier than v7.2.0 to v7.2.0 or later, the corresponding fields remain case-insensitive. Backup and restore operations involving system tables between these two types of clusters will fail. For more details, see [Issue #43717](https://github.com/pingcap/tidb/issues/43717).
148+
> Known issue: Starting from version v7.2.0, some system table fields in newly created clusters are case-insensitive. However, for clusters that are **upgraded online** from versions earlier than v7.2.0 to v7.2.0 or later, the corresponding system table fields remain case-sensitive. Backup and restore operations involving system tables between these two types of clusters might fail. For more details, see [Issue #43717](https://github.com/pingcap/tidb/issues/43717).
149149
150-
The following table lists the compatibility matrix for full backups. For clusters upgraded from a version prior to v7.2.0 to v7.2.0 or later, their behavior is consistent with that of backups from v7.1.0.
150+
The following table lists the compatibility matrix for full backups. Note that all information in the table applies to newly created clusters. For clusters upgraded from a version earlier than v7.2.0 to v7.2.0 or later, their behavior is consistent with that of backups from v7.1.0.
151151

152152
| Backup version | Compatible restore versions | Incompatible restore versions |
153-
|:---------|:----------------|:------------------|
154-
| v6.5.0 | 7.1.0 | v7.5.0 and later |
155-
| v7.1.0 | - | v7.5.0 and later |
156-
| v7.5.0 | v7.5.0 and later | - |
157-
| v8.1.0 | v8.1.0 and later | - |
153+
|:--|:--|:--|
154+
| v6.5.0 | 7.1.0 | v7.5.0 and later |
155+
| v7.1.0 | - | v7.5.0 and later |
156+
| v7.5.0 | v7.5.0 and later | - |
157+
| v8.1.0 | v8.1.0 and later | - |
158158

159-
The following table lists the compatibility matrix for log backups. For clusters upgraded from a version prior to v7.2.0 to v7.2.0 or later, their behavior is consistent with that of backups from v7.1.0.
159+
The following table lists the compatibility matrix for log backups. Note that all information in the table applies to newly created clusters. For clusters upgraded from a version earlier than v7.2.0 to v7.2.0 or later, their behavior is consistent with that of backups from v7.1.0.
160160

161161
| Backup version | Compatible restore versions | Incompatible restore versions |
162-
|:---------|:----------------|:------------------|
163-
| v6.5.0 | v7.1.0 | v7.5.0 and later |
164-
| v7.1.0 | - | v7.5.0 and later |
165-
| v7.5.0 | v7.5.0 and later | - |
166-
| v8.1.0 | v8.1.0 and later | - |
167-
162+
|:--|:--|:--|
163+
| v6.5.0 | 7.1.0 | v7.5.0 and later |
164+
| v7.1.0 | - | v7.5.0 and later |
165+
| v7.5.0 | v7.5.0 and later | - |
166+
| v8.1.0 | v8.1.0 and later | - |
168167
> **Note:**
169168
>
170169
> - When only user data is backed up (full backup or log backup), all versions are compatible with each other.

0 commit comments

Comments
 (0)