SOS API (Veeam) system.xml is not compatible with Veeam #17195
Description
Expected Behavior
Veeam recognizes MinIO as providing SOS API, but it does not.
Current Behavior
Manually requesting the system.xml object works, but there are some errors in it, which is why Veeam does not accept it.
Possible Solution
| XML Tag | Change | Description |
|---|---|---|
| ProtocolVersion | add enclosing double quotes | That's how it is described in the documentation and it's not working without it. |
| ModelName | add enclosing double quotes | That's how it is described in the documentation and recommended by Veeam (even if it is currently working without it). |
| APIEndpoints | remove this tag including subtags | The tag is optional. Since IAM and STS processing is not supported it should be removed. |
| SystemRecommendations | remove this tag including subtags | The tag is optional and should not be there, unless there are differences in Veeam defaults that have been previously discussed with Veeam. |
I'll submit a pull request.
Steps to Reproduce (for bugs)
- Follow "Appendix C: Manual plug-in load test" of the "Veeam Smart Object Storage API SOSAPI v1.0" available in the Veeam partner portal
- Notice that in the last step "If everything was implemented correctly you will the capacity information when you create a new backup job" does not work i.e. no capacity is displayed.
After the changes I propose, the capacity is displayed correctly.
Context
Regression
Your Environment
- Version used (
minio --version): RELEASE.2023-05-04T21-44-30Z - Server setup and configuration:
- Operating System and version (
uname -a):