Minio, Backblaze B2 and Veeam adding a slash

[schewee]

Has anyone gotten this configuration working?

Veeam Update 9.5 4b -> Minio B2 Gateway -> Backblaze B2?

I've read here that Minio is unofficially supported by Veeam: object-storage-f52/unoffizial-compatibi ... 56956.html

I have everything up and running, and have tried its with Minio running on Windows and Linux, and when I try to create a directory in the Backblaze B2 bucket I get the following:

Code: Select all

Amazon REST error: 'S3 error: Object name contains unsupported characters.
Code: XMinioInvalidObjectName', error code: 400
Other: Key: 'Veeam/', BackupName: 'VeeamCloudRepo'
Resource: '/VeeamCloudRepo/Veeam/', HostID: ''"

On the Minio Gateway I get:

Code: Select all

API: HeadObject(bucket=VeeamCloudRepo, object=Veeam/Archive/VeeamRepo//)
Time: 11:51:03 PDT 08/30/2019
RequestID: 15BFC7F7F559C15B
RemoteHost: 192.168.0.12
Host: localhost:9000
UserAgent: APN/1.0 Veeam/1.0 Backup/10.0
Error: b2_download_file_by_name: 400: File names must not end with '/'
       3: cmd/gateway/b2/gateway-b2.go:465:b2.(*b2Objects).GetObjectInfo()
       2: cmd/object-handlers.go:497:cmd.objectAPIHandlers.HeadObjectHandler()
       1: net/http/server.go:1995:http.HandlerFunc.ServeHTTP()

The issue appears to be that Veeam is adding a "/" (behind the scenes) to the end of the folder name because I'm certainly not adding one.

[Gostev]

Please note that non-S3 compatible object storage is not supported even through S3-compatible gateways (there's a note about that in the same topic). AFAIK, Backblaze is not S3-compatible. Thanks!