Using minIO as a S3 Cloud Storage Device on Synology NAS
Has anyone had luck installing minIO on a Synology NAS as s3 storage? I have followed some instructions that I found for another backup product using minIO which has you install Docker on the Synology NAS and then install the minIO Image.
I then installed a new Cloud Instance in the Backup Exec Command Line and set the User to match the assigned Access Key ID and the Password to match the assigned Secret Key. We are using port 9000 on the minIO server.
When I try to then add Cloud Storage in Backup Exec I get the error:
The server was unable to complete the requested operation. Unable to connect to the CloudStorage device. Ensure that the network is properly configured between the device and the Backup Exec server. BEMSDK Failure Code: E0009B3F.
See the following Wireshark trace sent to and from Backup Exec to the minIO server when the error occurs:
GET / HTTP/1.1
Host: redacted.bgibson.com:9000
Accept: */*
Date:Fri, 03 Feb 2023 21:54:10 GMT
Authorization: AWS Redacted :/swUqJpyTy9cvIJItoOyDtxNEd0=
user-agent:APN/1.0 Veritas/1.0 BackupExec/21.3
I then see the following reply from the minIO server:
HTTP/1.1 400 Bad Request
Accept-Ranges: bytes
Content-Length: 239
Content-Security-Policy: block-all-mixed-content
Content-Type: application/xml
Server: MinIO
Strict-Transport-Security: max-age=31536000; includeSubDomains
Vary: Origin
Vary: Accept-Encoding
X-Amz-Id-2: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
X-Amz-Request-Id: 17406EE9229F98CF
X-Content-Type-Options: nosniff
X-Xss-Protection: 1; mode=block
Date: Fri, 03 Feb 2023 21:50:08 GMT
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>MissingFields</Code><Message>Missing fields in request.</Message><Resource>/</Resource><RequestId>17406EE9229F98CF</RequestId><HostId>090c0eb5-9a28-4741-80d3-36c5388de3cc</HostId></Error>
Any ideas?
Thanks,
Brett Gibson
