Feature Request:

[cider-fairy-fan]

Hi all

This is a feature request to solve the issue I've had a chat about with Veeam Support in Case # 08163896.

Calling https://helpcenter.veeam.com/references ... Repository returns precise object size for each item in the object storage repository (in our case that was S3). The attribute for this is "usedSpaceBytes".

Code: Select all

{
    "name": "osr2",
    "sizeLimitEnabled": false,
    "sizeLimitBytes": 0,
    "usedSpaceBytes": 0,
    "freeSpaceBytes": null,
}

However, when retrieving backup repositories https://helpcenter.veeam.com/references ... Repository the return object has a different structure and different data, look at this real example from our veeam one server:

Code: Select all

{
  "name": "GGL_Repo_01_Archiv",
  "capacityBytes": 131941395333120,
  "freeSpaceBytes": 22233998426112
},
{
  "name": "FB_Repo_01_Archiv",
  "capacityBytes": 131941395333120,
  "freeSpaceBytes": 22233998426112
},
{
  "name": "CTX_Repo_02_Archiv",
  "capacityBytes": 131941395333120,
  "freeSpaceBytes": 22233998426112
}

As you can see, capacityBytes and freeSpaceBytes is exactly the same for all repos (this pattern repeats for a dozen repos or so I just picked three as an example). So what we see here is not information about the repository but about the drive itself: These sizes are the disk size total and disk size free and we can't know how big each individual backup is. This is not an assumption, this has been verified in the case I mentioned above after internal discussion about that topic, in the end I was advised to open a post here.

We would very much like this feature to be implemented soon if possible because this is important billing information for us, we need to know how much disk is used by each repository for each customer to create a detailed invoice. And for that we would prefer to use Veeam One given it's marketed as a unified solution for these kind of business cases.

Cheers!

[RomanK]

Hello,
Thanks for the detailed write-up and the case #.

In monitoring, object storage and local disk repositories are different object types with different properties. I recall we had a limitation around this on the VBR side. I'm not sure whether the same applies to VB365, so I'll check with our QA team.
If I remember correctly, the VB365 UI shows the same capacityBytes and freeSpaceBytes numbers for a local disk when they are just different folders on the same disk. From a monitoring perspective we try to stay consistent and this cannot be considered as a Veeam ONE bug.

However, your request to show used space is valid, and I'll look into whether VB365 actually gives us that data. I think the VB365 REST API doesn't return used space for local disk repositories either, but it does for object storage. Your feedback is noted.

Thanks

[cider-fairy-fan]

Thanks for the response. I do understand that due to being different objects they cannot be treated equally, it just seems weird for us and our use case because on the disk we get that info (by just checking the size), in "Veeam Backup for Microsoft 365" we have the "Used" row with the size but when calling objects from Veeam ONE API, it's missing.

We have multiple customers backups on the same drive and even if we hadn't, we need to list each item with its properties (and therefore price) to have a detailed itemized invoice and/or usage report that can be automated via API.

Cheers!