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!