This response from Backblaze. The SD would have to retry but that didn't seem to happen in the example I posted, it just moved on to the next part file.
"The "No Tomes Available" error refers to a potential and common http 500/503 response from our api. This error indicates that after the client authorized, and was directed to a storage location, the location then reported it was full/unavailable and a new upload location assignment is needed. You can read more about that in this blog post. https://www.backblaze.com/blog/b2-503-500-server-error/ Typically retrying the upload after waiting up to 30 seconds will result in a successful upload. Please let us know if there's anything further we can assist with." On Tue, 17 Jan 2023, 4:28 pm Chris Wilkinson, <winstonia...@gmail.com> wrote: > Backblaze provides an integration checklist for developers. > > https://www.backblaze.com/b2/docs/integration_checklist.html > > I’m wondering if anyone could comment on whether the S3 driver is > compliant with this? > > I’ve asked the question of Backblaze what the S3 driver is supposed to do > when this error occurs and will report the response. > > Best > -Chris- > > > > > On 17 Jan 2023, at 15:12, Heitor Faria <hei...@bacula.com.br> wrote: > > Hello Chris, > > This new upload error occurred today. > > "No tomes available" is expected to occur sometimes and the client is > expected to retry. This doesn't seem to be working. > > Could this be a bug with the S3 driver? > > A while ago, Backblaze didn't have S3 support, having to rely on adaptors > such as mini.io. Ref.: > https://www.backblaze.com/blog/how-to-use-minio-with-b2-cloud-storage/ > Nowadays, I suppose they already deployed native S3 integration, but we > can never be sure it is 100% compliant with the S3 standard. I found some > "no tomes available" errors reports from other applications, as follows. > "does S3QL stop or is this just a warning? Looks like a "tome" is a > storage unit ( > https://help.backblaze.com/hc/en-us/articles/218485257-B2-Resiliency-Durability-and-Availability > ) and B2 had none available there for a while." Ref.: > https://groups.google.com/g/s3ql/c/H1EGYyw6mWs > That said, I think you should contact the Backblaze support first, before > putting efforts in the Bacula SD debug. > > Rgds. > -- > > MSc Heitor Faria (Miami/USA) > Bacula LATAM CIO > mobile1: + 1 909 655-8971 > mobile2: + 55 61 98268-4220 > <https://www.linkedin.com/in/msc-heitor-faria-5ba51b3> > <logo_bacula_brasil_2022.jpg> <http://www.bacula.com.br/> > bacula.lat | bacula.com.br <http://www.bacula.com.br/> > > > >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
