Re: [Bacula-users] Troubles with AWS [Possibly solved]

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 a

Re: [Bacula-users] Troubles with AWS [Possibly solved]

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

Re: [Bacula-users] Troubles with AWS [Possibly solved]

I don't specify "max concurrent uploads" so it defaults to 3 per manual. I have differing max part size for the jobs but the ones that frequently fail are 500Mb. I'm bandwidth limited to 6MB/sec so I don't see any benefit from trying to run uploads concurrently. My largest backup is 350GB that tak

Re: [Bacula-users] Troubles with AWS [Possibly solved]

On 1/13/23 18:26, Andrea Venturoli wrote: Then I upgraded every package (don't think it matters, still no harm) and now I'm trying with "cloud upload" manually. I'll see how this goes. Still troublesome, but now the error is more verbose: 3000 Cloud Upload: Full0116/part.195 state=error

Re: [Bacula-users] Troubles with AWS

On 1/13/23 18:04, Chris Wilkinson wrote: There's been a couple of threads on this topic recently and I posted I looked, but I thought they were a different problem. similar question late last year. I get this error sporadically... I can only assume that network errors are responsible which

Re: [Bacula-users] Troubles with AWS

There's been a couple of threads on this topic recently and I posted a similar question late last year. I get this error sporadically and haven't found any resolution yet. I just rerun the job, delete the failed one and it usually works. The job log shows that the backup completed with error. Since