From 0b068a7da04605e8efcb47f7d4f86e4fb6b7f271 Mon Sep 17 00:00:00 2001 From: Cathy <24819510+benmaoer@users.noreply.github.com> Date: Mon, 27 Nov 2023 15:17:08 +0800 Subject: [PATCH] Update tidb-cloud/backup-and-restore.md Co-authored-by: Aolin --- tidb-cloud/backup-and-restore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/backup-and-restore.md b/tidb-cloud/backup-and-restore.md index be7a10f2cfafd..827f43f90b1a9 100644 --- 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.