Veeam SOS API and MinIO bucket capacity reporting

[kevin.boddy]

Hi,

I have the SOS API working with the latest build of MinIO and the backup repository shows as S3 Integrated.
The issue I am seeing is that when querying the capacity.xml file for the MinIO alias/bucket, the returned values for the capacity, available and used storage are the values for the entire MinIO cluster not just the bucket.

The MinIO developers say this is expected.

Was that the intent of the Veeam SOS API?
Surely it would be more usable to only report on the bucket being queried?

Thanks
Kevin

[sfirmes]

@kevin.boddy MinIO is correct that their implementation of SOSAPI is working as designed. Some platforms have the capability to report the capacity metrics at the bucket level, while others report it at the account or platform level. Based on how they can report on their capacity metrics, they place that value into the capacity.xml file.

I will contact our partners who have implemented the SOSAPI's capacity feature and will update this thread when I have that data.

Hope this answers your question.

[kevin.boddy]

Thank you for the feedback.

Maybe this is a MinIO question but is it possible to then disable this function somehow or are all my customers going to see the clusters entire storage capacity?

[sfirmes]

You are correct and MinIO would need to be engaged to see if they have a method to disable it.

[kevin.boddy]

Hi,

I have blocked this for now using a policy which denies access to the capacity.xml file.

Thanks
Kevin

[kevin.boddy]

There seems to be a problem with the SOS API with regard to the region.
If I set the region on the MinIO cluster to anything other than us-east-1 then the API stops working and no longer reports the capacity information.
Why is this?
I don't recall seeing this in the documentation.

[sfirmes]

@kevin.boddy I am unaware of any references/usage of the region within the SOSAPI. If you are still experiencing issues, please open a support ticket with Veeam and post the case# in this thread.

[kevin.boddy]

Hi,

I do already have a case open #06311191. I have provided screenshots before and after changing the region.

When you change the region and not do set it correctly in Veeam when trying to add the object storage repository, then you cannot select the folder, it gives you a cannot find the bucket error. So there must be some reference to the region being made in the API calls.

Thanks
Kevin

[sfirmes]

Correct.

Our s3 api logic uses the region, but the SOSAPI doesn't. The enforcement of the region value being correct is something that the object storage platform does. Some object storage platforms, mostly the on-prem ones, ignore the region setting or default to us-east-1.

But some, including MinIO, require the region to be properly set.

[Eco]

@sfirmes @kevin.boddy Technically MinIO does not require a region to be set, but if it is set explicitly then it must be used.

[kevin.boddy]

I have set the region in MinIO to something other than us-east-1. When you do that and Veeam is configured with the same region as MinIO, the SOSAPI stops working from Veeam's side.
From MinIO's side the mc cat command shows that the capacity.xml is generated for the bucket with the usage data in it but Veeam does not seem use it.

This looks like a Veeam issue to me.