@@ -158,10 +158,10 @@ they will see the following files created:
158158``` shell
159159s3://backup/bendsave.md
160160s3://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
167167The 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
170170s3://backup/bendsave.md
171171s3://backup/manifests/20250114_201500.manifest
172172s3://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
181181The 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