Update tidb-cloud/backup-and-restore.md

Co-authored-by: Aolin <[email protected]>
pingcap · Nov 27, 2023 · 0b068a7 · 0b068a7
1 parent 6c07312
commit 0b068a7
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md
@@ -14,7 +14,7 @@ This document describes how to back up and restore your TiDB Dedicated cluster d
 
 ## Limitations
 
-- TiDB Dedicated supports restoring user accounts and sql bindings from backups by default from TiDB v6.2.0.
+- For clusters that are v6.2.0 or later, TiDB Dedicated supports restoring user accounts and sql bindings from backups by default.
 - TiDB Dedicated does not support restoring system variables stored in the `mysql` schema. 
 - It is recommended that you import data first, then perform a **manual** snapshot backup, and finally enable Point-in-time Restore. Because the data imported through the TiDB Cloud console **does not** generate change logs, it cannot be automatically detected and backed up. For more information, see [Import CSV Files from Amazon S3 or GCS into TiDB Cloud](/tidb-cloud/import-csv-files.md). 
 - If you turn on and off Point-in-time Restore multiple times, you can only choose a time point within the recoverable range after the most recent Point-in-time Restore is enabled. The earlier recoverable range is not accessible.