Skip to content

Commit 1585b14

Browse files
Xuanwosoyeric128
authored andcommitted
Make sha256 more clear
Signed-off-by: Xuanwo <[email protected]>
1 parent 00e73cc commit 1585b14

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

docs/en/guides/90-community/02-rfcs/20250109-disaster-recovery.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -158,10 +158,10 @@ they will see the following files created:
158158
```shell
159159
s3://backup/bendsave.md
160160
s3://backup/manifests/20250114_201500.manifest
161-
s3://backup/data/<block_id_0>
162-
s3://backup/data/<block_id_1>
163-
s3://backup/data/<block_id_....>
164-
s3://backup/data/<block_id_N>
161+
s3://backup/data/<sha256_of_block_0>
162+
s3://backup/data/<sha256_of_block_1>
163+
s3://backup/data/<sha256_of_block_....>
164+
s3://backup/data/<sha256_of_block_N>
165165
```
166166

167167
The second time users perform a backup, bendsave will generate the following files and omit existing blocks:
@@ -170,12 +170,12 @@ The second time users perform a backup, bendsave will generate the following fil
170170
s3://backup/bendsave.md
171171
s3://backup/manifests/20250114_201500.manifest
172172
s3://backup/manifests/20250115_201500.manifest
173-
s3://backup/data/<block_id_0>
174-
s3://backup/data/<block_id_1>
175-
s3://backup/data/<block_id_....>
176-
s3://backup/data/<block_id_N>
177-
s3://backup/data/<block_id_....>
178-
s3://backup/data/<block_id_M>
173+
s3://backup/data/<sha256_of_block_0>
174+
s3://backup/data/<sha256_of_block_1>
175+
s3://backup/data/<sha256_of_block_....>
176+
s3://backup/data/<sha256_of_block_N>
177+
s3://backup/data/<sha256_of_block_....>
178+
s3://backup/data/<sha256_of_block_M>
179179
```
180180

181181
The block id is generated by the SHA-256 checksum of the block content. So we can reuse the same block if it has been backed up before.

0 commit comments

Comments
 (0)