From 78def35e41911ea19733ac5b118056a7657fd01d 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 b577997c60af685133dd4148792e25da7aad2eff 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 ed1e8d68ba55fe7f47476115020a051b20960268 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 00b0b5d8b23f9..56426e8733cf6 100644 --- a/br/br-pitr-guide.md +++ b/br/br-pitr-guide.md @@ -23,7 +23,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: @@ -52,7 +52,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 @@ -61,8 +61,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' ``` @@ -94,7 +94,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`: