From 6836c67a2b4d4f70fdd42cf1165aaba124a2ebd5 Mon Sep 17 00:00:00 2001 From: Lilian Lee Date: Tue, 4 Mar 2025 18:16:19 +0800 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Grace Cai --- br/br-log-architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/br/br-log-architecture.md b/br/br-log-architecture.md index 64ffbbdbb4a18..c3c7a38ab44fb 100644 --- a/br/br-log-architecture.md +++ b/br/br-log-architecture.md @@ -122,7 +122,7 @@ Log backup generates the following types of files: Explanation of the backup file directory structure: -- `backupmeta`: contains backup metadata. The `resolved_ts` in the filename indicates the backup progress, meaning that data before this TSO has been fully backed up. However, note that this TSO only reflects the progress of certain shards. +- `backupmeta`: stores backup metadata. The `resolved_ts` in the filename indicates the backup progress, meaning that data before this TSO has been fully backed up. However, note that this TSO only reflects the progress of certain shards. - `global_checkpoint`: represents the global backup progress. It records the latest point in time to which data can be restored using `br restore point`. - `{date}/{hour}`: stores backup data for the corresponding date and hour. When cleaning up storage, always use `br log truncate` instead of manually deleting data. This is because the metadata references the data in this directory, and manual deletion might lead to restore failures or data inconsistencies after restore.