JetBackup Community Forums

I installed JetBackup on my cloud server today in cPanel, linked to BackBlaze (note: I had to use Custom Vendor since BackBlaze key wouldn't work otherwise).

The backup ended up failed, stating that it couldn't send the file(s). But, there were some accounts that show completed, but most are failed.

Here's part of what is in the log file:

[29/Apr/2021 14:13:28 +0000] [PID 5860] Transferring account "test" backup to destination "BackBlaze"
[29/Apr/2021 14:14:07 +0000] [PID 5860] [ERROR] Failed transferring account "test" backup to destination "BackBlaze". Error: Unable to upload file /home/test/public_html/administrator/components/com_admin/sql/updates/sqlazure/3.7.0-2016-09-29.sql
[29/Apr/2021 14:14:07 +0000] [PID 5860] [ERROR] Failed account "test" transferring backup to all destinations
[29/Apr/2021 14:14:07 +0000] [PID 5860] Backup Failed
[29/Apr/2021 14:14:07 +0000] [PID 5860]


But on another account:

[29/Apr/2021 14:50:05 +0000] [PID 5860] Transferring account "test2" backup to destination "BackBlaze"
[29/Apr/2021 14:50:34 +0000] [PID 5860] Backup Completed

What could possibly cause this? Is there some logs that show more in depth what the problem may have been?

Hello omcreations,

I would like to start off by thanking you for using JetBackup 5 and its brand new S3 Compatible Plugin. Please note that the S3 Compatible Plugin v1.0.16 is currently still EXPERIMENTAL as we continually push more updates for its stability and new features. There have been many reports of failed backups to S3 destinations and these failures are typically caused by HTTP Request Errors. You can find more information about which specific errors are causing your failed backup by checking the s3.log located at the following path:
With that said, our developers are aware of many common HTTP Request Errors (40X/50X) that can be worked around by retrying the upload. This retry feature will be available in our next S3 Compatible Plugin update for v1.0.17. The update for the S3 Compatible Plugin will be released to the EDGE tier first within the next 2 weeks.

(note: I had to use Custom Vendor since BackBlaze key wouldn't work otherwise)

This is the first we have seen of this issue. Was there a specific region missing from our pre-determined Backblaze Configurations that caused this issue? We would like to hear more about this issue if you have any more information. If you would like us to take a more detailed look, I would highly suggest opening a support ticket by emailing [email protected]

Thank you for your continued support and we hope to hear from you soon.