From af045ad89b25ea1afb44abcab559b364d5983553 Mon Sep 17 00:00:00 2001 From: Ran Date: Mon, 11 Dec 2023 10:08:01 +0800 Subject: [PATCH 1/3] Add temp.md --- temp.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 temp.md diff --git a/temp.md b/temp.md new file mode 100644 index 0000000000000..af27ff4986a7b --- /dev/null +++ b/temp.md @@ -0,0 +1 @@ +This is a test file. \ No newline at end of file From fb4835b2f08caac7f09f41c306bcb3cd14dbd703 Mon Sep 17 00:00:00 2001 From: Ran Date: Mon, 11 Dec 2023 10:08:06 +0800 Subject: [PATCH 2/3] Delete temp.md --- temp.md | 1 - 1 file changed, 1 deletion(-) delete mode 100644 temp.md diff --git a/temp.md b/temp.md deleted file mode 100644 index af27ff4986a7b..0000000000000 --- a/temp.md +++ /dev/null @@ -1 +0,0 @@ -This is a test file. \ No newline at end of file From a837b2d675ecaf6d8d4772dcb596ab01518a2953 Mon Sep 17 00:00:00 2001 From: Ran Date: Mon, 11 Dec 2023 10:11:36 +0800 Subject: [PATCH 3/3] remove redundant quotation marks Signed-off-by: Ran --- br/br-pitr-guide.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/br/br-pitr-guide.md b/br/br-pitr-guide.md index 63332f97d37ca..e1455cc20a5b0 100644 --- a/br/br-pitr-guide.md +++ b/br/br-pitr-guide.md @@ -22,7 +22,7 @@ To start a log backup, run `br log start`. A cluster can only run one log backup ```shell tiup br log start --task-name=pitr --pd "${PD_IP}:2379" \ ---storage 's3://backup-101/logbackup?access-key=${access-key}&secret-access-key=${secret-access-key}"' +--storage 's3://backup-101/logbackup?access-key=${access-key}&secret-access-key=${secret-access-key}' ``` After the log backup task starts, it runs in the background of the TiDB cluster until you stop it manually. During this process, the TiDB change logs are regularly backed up to the specified storage in small batches. To query the status of the log backup task, run the following command: @@ -51,7 +51,7 @@ The snapshot backup can be used as a method of full backup. You can run `br back ```shell tiup br backup full --pd "${PD_IP}:2379" \ ---storage 's3://backup-101/snapshot-${date}?access-key=${access-key}&secret-access-key=${secret-access-key}"' +--storage 's3://backup-101/snapshot-${date}?access-key=${access-key}&secret-access-key=${secret-access-key}' ``` ## Run PITR @@ -60,8 +60,8 @@ To restore the cluster to any point in time within the backup retention period, ```shell br restore point --pd "${PD_IP}:2379" \ ---storage='s3://backup-101/logbackup?access-key=${access-key}&secret-access-key=${secret-access-key}"' \ ---full-backup-storage='s3://backup-101/snapshot-${date}?access-key=${access-key}&secret-access-key=${secret-access-key}"' \ +--storage='s3://backup-101/logbackup?access-key=${access-key}&secret-access-key=${secret-access-key}' \ +--full-backup-storage='s3://backup-101/snapshot-${date}?access-key=${access-key}&secret-access-key=${secret-access-key}' \ --restored-ts '2022-05-15 18:00:00+0800' ``` @@ -93,7 +93,7 @@ The following steps describe how to clean up backup data that exceeds the backup 3. Delete log backup data earlier than the snapshot backup `FULL_BACKUP_TS`: ```shell - tiup br log truncate --until=${FULL_BACKUP_TS} --storage='s3://backup-101/logbackup?access-key=${access-key}&secret-access-key=${secret-access-key}"' + tiup br log truncate --until=${FULL_BACKUP_TS} --storage='s3://backup-101/logbackup?access-key=${access-key}&secret-access-key=${secret-access-key}' ``` 4. Delete snapshot data earlier than the snapshot backup `FULL_BACKUP_TS`: