Skip to content

Commit 7b725f1

Browse files
committed
Update br-checkpoint-backup.md
1 parent be56261 commit 7b725f1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

br/br-checkpoint-backup.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ In TiDB v6.5.0, Backup & Restore (B) introduces the checkpoint backup feature to
1212

1313
## Application scenarios
1414

15-
If your TiDB cluster is large and cannot affords to backup again after a failure, you can use the checkpoint backup feature. The br command-line tool (hereinafter referred to as `br`) periodically records the shards that have been backed up. In this way, the next backup retry can use the backup progress close to the abnormal exit.
15+
If your TiDB cluster is large and cannot affords to backup again after a failure, users can use the checkpoint backup feature. The br command-line tool (hereinafter referred to as `br`) periodically records the shards that have been backed up. In this way, the next backup retry can use the backup progress close to the abnormal exit.
1616

1717
## Implementation details
1818

@@ -30,7 +30,7 @@ Checkpoint backup relies on the GC mechanism and cannot recover all data that ha
3030

3131
During the backup, `br` periodically updates the `gc-safepoint` of the backup snapshot in PD to avoid data being garbage collected. When `br` exits, the `gc-safepoint` cannot be updated in time. As a result, before the next backup retry, the data might have been garbage collected.
3232

33-
To avoid this situation, `br` keeps the `gc-safepoint` for about one hour by default when `gcttl` is not specified. You can set the `gcttl` parameter to extend the retention period if needed .
33+
To avoid this situation, `br` keeps the `gc-safepoint` for about one hour by default when `gcttl` is not specified. Users can set the `gcttl` parameter to extend the retention period if needed .
3434

3535
The following example sets `gcttl` to 15 hours (54000 seconds) to extend the retention period of `gc-safepoint`:
3636

@@ -42,7 +42,7 @@ tiup br backup full \
4242

4343
> **Note:**
4444
>
45-
> The `gc-safepoint` created before backup is deleted after the snapshot backup is completed. You do not need to delete it manually.
45+
> The `gc-safepoint` created before backup is deleted after the snapshot backup is completed. Users do not need to delete it manually.
4646
4747
### Some data needs to be backed up again
4848

0 commit comments

Comments
 (0)