Hello, Does the new bacula amazon driver work with non-amazon s3 endpoints? I ask because I was trying to use the amazon driver with backblaze's s3 compatible API and I got errors like this:
td-bacula-sd JobId 40: Cloud Upload transfers: td-bacula-sd JobId 40: Error: test-group-user-bucket1-0012/part.1 state=error retry=10/10 size=285 B duration=154s msg=/opt/bacula/plugins/aws_cloud_driver upload test-group-user-bucket1-0012 part.1. Invalid endpoint: https://s3.. amazonaws.com Child exited with code 1 I confirmed that volume files were not being uploaded to the test bucket. The errors went away as soon as I switched from the amazon driver to the s3 driver. My cloud configuration from that point in time is below. Cloud { Name = "test-group-user-bucket1" Driver = "Amazon" HostName = "s3.us-east-005.backblazeb2.com" BucketName = "test-group-user-bucket1" AccessKey = "REDACTED" SecretKey = "REDACTED" Protocol = "HTTPS" UriStyle = "VirtualHost" TruncateCache = "No" Upload = "EachPart" } I see that the amazon driver is intended to eventually replace the s3 driver. It would be very disappointing if bacula were to move from theoretically supporting any s3 compatible host to only supporting amazon as a cloud storage provider. Regards, Robert Gerber 402-237-8692 r...@craeon.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
