@andrewreid Yes, I can't wait to share it with everybody.

@s-pam I answered on the ticket and deployed the fix.

@s-pam I answered on the ticket and deployed the fix.

@s-pam this issue caused quite a few tickets, which one is yours ? I can connect right away

@s-pam it's a great choice
If you can launch a backup , I can connect through a support tunnel and deploy the fix

then you can launch the backup and we can celebrate the success of this fix

@pnunn @S-Pam If you use the sources, can you try to use this branch feat-add-debug-backup it's master with additionnal debug and a potential fix ( potential , because I can't reproduce it regularly in our lab)

Then you can activate more debug by this

[logs]
# Display all logs matching this filter, regardless of their level
filter = 'xo:backups'

# Display all logs with level >=, regardless of their namespace
level = 'debug'

in your config file ( should be in ~/.config/xo-server/config.toml

@stevewest15 I don't have any advice of the fiability of b2
Their design require us to make a minor modification to our upload service .

During a full xva backup to a S3 like service, each part uploaded is uploaded along its hash and that is used to control the integrity

thank you @stevewest15
I don't have the info I wanted inside, but I think we'll have to handle the 500 error of b2 with a retry . Theses errors are uncommon on S3, but are here by design in b2

@stevewest15

there isn't much documentation online, but I found here ( https://www.reddit.com/r/backblaze/comments/bvufz0/servers_are_often_too_busy_is_this_normal_b2/ ) that we should retry when this error occurs

can you copy the full log of this backup ? It would be easier If we could get a machine code ( probably a http code like 50x ) as explained here : https://www.backblaze.com/blog/b2-503-500-server-error/

You can get it by clicking on the second icons from the left in your job report

@olivierlambert never heard of this one . I will search if it's a backblaze or a xo message
since it use uploadPartCopy , it should be during a full (xva ) backup

@andrewreid Yes, I can't wait to share it with everybody.