Backblaze backup fails to upload all chunks

N

nathanwoodburn

New Member
Apr 16, 2026
5
0
1
I've got my PVE server backing up to a backblaze S3 bucket. When it is backing up, it gets marked as having warnings and verifying the backup fails.

If anyone has any suggestions that would be great. Thanks a ton
Code: 
2026-04-01T03:25:45+11:00: Upload statistics for 'drive-scsi0.img.fidx'
2026-04-01T03:25:45+11:00: Checksum: 076c9d650b42415890d72154e533435feab9fb3fed361d404d49e50990d2eec0
2026-04-01T03:25:45+11:00: Size: 161614921728
2026-04-01T03:25:45+11:00: Chunk count: 38532
2026-04-01T03:25:45+11:00: Upload size: 156791472128 (97%)
2026-04-01T03:25:45+11:00: Duplicates: 1150+150 (3%)
2026-04-01T03:25:45+11:00: Compression: 26%
2026-04-01T03:25:47+11:00: Uploaded fixed index file to object store: drive-scsi0.img.fidx
2026-04-01T03:25:47+11:00: successfully closed fixed index 1
2026-04-01T03:25:47+11:00: add blob "/mnt/backblaze/vm/124/2026-03-31T15:39:39Z/index.json.blob" (324 bytes, comp: 324)
2026-04-01T03:25:47+11:00: syncing filesystem
2026-04-01T03:25:47+11:00: successfully finished backup
2026-04-01T03:25:47+11:00: backup finished successfully
2026-04-01T03:25:47+11:00: TASK WARNINGS: 66

When I look through my logs I find these errors.
Code: 
2026-04-01T03:22:01+11:00: Upload new chunk 011c000db805c2cb3599e6a50acf9a66b7484a6a7743eac72a4419f51115ad7a
2026-04-01T03:22:01+11:00: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
    <Code>ServiceUnavailable</Code>
    <Message>no tomes available</Message>
</Error>
2026-04-01T03:22:01+11:00: Upload new chunk 28795bc1c223340bc8ea6142a11b34961a6d7f5a805ce94538378a43fcb67212
2026-04-01T03:22:01+11:00: Upload new chunk f3beab334078a35721d14ce07944808a1c9908678b95ba5c58f11deea06af326


Code: 
2026-04-01T02:40:14+11:00: Caching of chunk 1cdb79d3f9eb97942f40b1b94c1681eb9cdf53b8381c0698ed8487846c063516
2026-04-01T02:40:14+11:00: Caching of chunk 2f793b4ba7f2c79b9a519e10eec189413075ee55bcdc6c929eb9bebc61cbc4b7
2026-04-01T02:40:14+11:00: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
    <Code>InternalError</Code>
    <Message>An internal error occurred.  Please retry your upload.</Message>
</Error>

2026-04-01T02:40:14+11:00: Caching of chunk fd35a80791565c0c6c90eb1649a8ef5a776c5398566e955752c5bb6fa0d33cad
2026-04-01T02:40:14+11:00: Upload new chunk 17762c9893edf43235b2a99e65fe8186cb4e1ae4b2fd6a1c8a567c46a2ebc8b7
2026-04-01T02:40:14+11:00: Caching of chunk d7e63ba6e9edebd9422591c50ca15a004e3b2c9f43d903f433407f11a305b29f

Code: 
2026-04-01T03:06:47+11:00: Upload new chunk 8379c8a1977a8bc37860b17e47e0034400341d0746e54527aeeaed5a424bcd05
2026-04-01T03:06:47+11:00: Upload new chunk f836617bd3181ded34d03e72ea76ba92c7705142b5884c2f92ad12863cf70da4
2026-04-01T03:06:47+11:00: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
    <Code>ServiceUnavailable</Code>
    <Message>Service temporarily unavailable, please try again.</Message>
</Error>

2026-04-01T03:06:47+11:00: Upload new chunk 5dee78fe0b8759b5b78e0c110746ab903da31873e087ff67e5f42311c33dc633
2026-04-01T03:06:47+11:00: Caching of chunk d441594f9c3ed45521e83889be41bc6410cc00e4a568d7b2cb4a955ab74945a1
2026-04-01T03:06:47+11:00: Caching of chunk 6a07b63d42c4a055ee209964921ff9c1bfcc9968405842fab1e79d3174c54c3a
 
Last edited:
What's version are you running, please post the output of proxmox-backup-manager version --verbose. Further, this seems to have been an incremental backup. Make sure the previous backup snapshot does verify, otherwise you might have a corrupt backup snapshot chain for this group.

The errors you are seeing in the log are transient errors, which since version 4.1.6 of proxmox-backup-server get handled as such and retired. So make sure to run an up-to-date version. For details see https://git.proxmox.com/?p=proxmox.git;a=commit;h=ef4b0e26435fdb8ab7cadb49034980204f960845
 
Make sure however that you are not running an incremental backup, if you have a corrupt chain, it might get extended. The previous snapshot must be either verified ok or show a verification error.
 
By running a verification of the last backup snapshot of a group before starting a new backup to that group. I fverification passed, you are okay and it is fine for the next backup run to reuse chunks and perform an incremental backup. If verification fails, the next backup run will not be incremental.
 
Last edited:
Chris said:
By running a verification of the last backup snapshot of a group before starting a new backup to that group. I fverification passed, you are okay and it is fine for the next backup run to reuse chunks and perform an incremental backup. If verification fails, the next backup run will not be incremental.
Click to expand...
Ok. I'll run that. Thanks
 
You must log in or register to reply here.
Top Bottom
Back