Replies inline below. Regards, Robert Gerber 402-237-8692 r...@craeon.net
On Thu, Feb 20, 2025 at 8:40 PM Marcin Haba <ganius...@gmail.com> wrote: > On Fri, 21 Feb 2025 at 03:21, Rob Gerber <r...@craeon.net> wrote: > > I'm using the s3 driver instead of the amazon driver. I read that the > new amazon driver is much better than the s3 driver, but in my testing the > amazon driver didn't seem to want to connect to a non-aws server. > > Hello Rob, > > What error message did you experience with Amazon driver? I saw errors like this: 22-Feb 10:28 td-bacula-sd JobId 97: Error: B2-TGU-Inc-0048/part.1 state=error retry=10/10 size=263 B duration=56s msg=/opt/bacula/plugins/aws_cloud_driver upload B2-TGU-Inc-0048 part.1. Invalid endpoint: https://s3..amazonaws.com Child exited with code 1 Before trying the BlobEndpoint directive, I had concluded that the error message meant that the Amazon driver only supported the AWS cloud, which would have been a very shortsighted and disappointing thing. For Amazon > driver and non-AWS S3 cloud storage in the Cloud configuration > resource you need to define the BlobEndpoint directive. Otherwise it > will not work. > > That, what you read about the Amazon driver is true. This Amazon > driver works much better than S3 and I encourage you to try it again. > > I tried using the BlobEndpoint directive, and the amazon driver works! The manual is not very clear about the need for this directive, or the syntax required (I initially provided "BlobEndpoint = " s3.us-east-005.backblazeb2.com"", matching what I had for "Hostname = " s3.us-east-005.backblazeb2.com"". Errors in bconsole when manually doing a part upload showed me that I needed to use format "BlobEndpoint = " https://s3.us-east-005.backblazeb2.com/""; but this wasn't clear from the manual either. It would definitely be better if we provided some basic configuration information for cloud devices in the manual, including sample configurations and advice on the BlobEndpoint directive and its uses. Right now the BlobEndpoint directive documentation in the manual merely links to an Azure documentation page that doesn't (on the face of it, at least) appear to give any useful information on how the directive is meant to be used, or when we should use it. The manual is very vague about how to even configure a cloud resource. I actually used bacularis to generate an initial cloud resource that I used as a template when setting up my configuration. I do see that bacularis offers the 'BlobEndpoint' directive under advanced options during the cloud device setup wizard. Perhaps a note could be added to indicate that this is important for non-AWS storage providers? Even better would be some sort of logic to detect when a non-AWS provider's hostname is entered, and to automatically apply the BlobEndpoint directive. Alternately, would ALWAYS specifying a BlobEndpoint break things sometimes if the endpoint is an AWS domain? Thank you! I am very excited to be able to use the Amazon driver since it should be more reliable. Thank you thank you thank you!! Best regards, > Marcin Haba (gani) >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
