On Sat, 22 Feb 2025 at 18:01, Rob Gerber <r...@craeon.net> wrote: >> 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
Hello Rob, Thanks for your response and feedback. Yes, this is the error that I expected to see :-) >> 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! That's fantastic! > 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? You are right. I will add to the Bacularis wizard the description about using the BlobEndpoint with non-AWS cloud storage if Amazon driver is selected. In the Bacularis documentation we already have a chapter about creating the Bacula cloud storage and there is included a video guide. In this video guide this BlobEndpoint directive is explained for non-AWS cloud storage, but definitely the video can be not noticeable by all users. So, adding info in Bacularis will be helpful, and probably in that doc chapter as well. Thanks! This doc is here: https://bacularis.app/doc/bacula-basics/create-bacula-cloud-storage.html Best regards, Marcin Haba (gani) _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
