On 11/30/23 03:29, Chris Wilkinson wrote:
I use Backblaze B2. It is S3 compliant but about the lowest cost I could find, certainly a fraction of the price of AWS.It works mostly OK except for errors of the kind in the log below. The "no tomes" error is from B2 when there are no upload slots available temporarily. B2 says that the user application is expected to retry the transfer if this occurs. AKAIK the S3 driver doesn’t retry, just gives up. There is a bconsole 'cloud' command to upload volumes to cloud manually. A listing of the cloud volumes shows that the errored volume in the log wasn't uploaded but I could do it manually.Because of this I do not delete the cache after backup, the downside being I have to provision the disc space. Chris
Hello Chris, Bacula S3 by default re-tries 10 times to upload cloud volume parts. There is currently an internal feature request here at Bacula Systems to allow this to be configured, along with a feature request to configure the time between attempts. :)
Additionally, it is recommended to have a Bacula Admin job which runs `cloud upload` commands to make sure that any parts that had failed to upload (ie: due to temporary networking issues during the backup job, etc)
Hope this helps, Bill -- Bill Arlofski w...@protonmail.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
