Do you use Copy, or Move to CapTier?
As the Sum of both; not deduplicated, may count same restore point twice. 
The sum shown is the current usage on both tiers, not the unique protected data.
Some restore points may exist on both tiers at the same time (depending on your SOBR offload/copy/move policies and retention settings). For example, if you use "Copy" mode, all new backups are copied to S3 immediately, so during retention overlap, the same restore point could exist on both tiers.

This number can be deceiving due to XFS and the fast clone option if used.  There has always been issues reporting this and with ReFS too.  I am hoping the next versions have better space capacity reporting across all products.  If you find a good way please post it as we use the VSPC API for our reports as well.

Yes we are using Copy + Move to capacity Tier.

So if I follow your interpretation:
If I have same backup files in my performance tier and my capacity tier Veeam count them like one ?
 

Yes we are using FastCloning, I saw a post in the forum about ReFS…. 

The folder size on the XFS, this value doesn’t benefit of block cloning.
 

So the value for the Performance tier seems to be good in the VSPC…

I open a case in parallel

 

This number can be deceiving due to XFS and the fast clone option if used.  There has always been issues reporting this and with ReFS too.  I am hoping the next versions have better space capacity reporting across all products.  If you find a good way please post it as we use the VSPC API for our reports as well.

Yes we are using FastCloning, I saw a post in the forum about ReFS…. 

The folder size on the XFS, this value doesn’t benefit of block cloning.
 

So the value for the Performance tier seems to be good in the VSPC…

I open a case in parallel

Interesting 🤔 

Let us know what the case brings as I am interested since we use VSPC more and more.

Yes we are using Copy + Move to capacity Tier.

So if I follow your interpretation:
If I have same backup files in my performance tier and my capacity tier Veeam count them like one ?
 

This number can be deceiving due to XFS and the fast clone option if used.  There has always been issues reporting this and with ReFS too.  I am hoping the next versions have better space capacity reporting across all products.  If you find a good way please post it as we use the VSPC API for our reports as well.

Yes we are using FastCloning, I saw a post in the forum about ReFS…. 

The folder size on the XFS, this value doesn’t benefit of block cloning.
 

So the value for the Performance tier seems to be good in the VSPC…

I open a case in parallel

Do you have more than one full for at least one backup on the performance tier? Multiple Synthetic fulls is where you’ll see the most block cloning happening. If you’ve configured your Move policy in the SOBR to move all but the most recent backup chain, you won’t see any space savings with XFS.

Yes we are using Copy + Move to capacity Tier.

So if I follow your interpretation:
If I have same backup files in my performance tier and my capacity tier Veeam count them like one ?
 

This number can be deceiving due to XFS and the fast clone option if used.  There has always been issues reporting this and with ReFS too.  I am hoping the next versions have better space capacity reporting across all products.  If you find a good way please post it as we use the VSPC API for our reports as well.

Yes we are using FastCloning, I saw a post in the forum about ReFS…. 

The folder size on the XFS, this value doesn’t benefit of block cloning.
 

So the value for the Performance tier seems to be good in the VSPC…

I open a case in parallel

 

Do you have more than one full for at least one backup on the performance tier? Multiple Synthetic fulls is where you’ll see the most block cloning happening. If you’ve configured your Move policy in the SOBR to move all but the most recent backup chain, you won’t see any space savings with XFS.

Yes I have more than one Full, in VCC we could easly see the used space (without block cloning) and the real capacity allocated to the XFS. 

My capacity Tier policy : we are using a copy+move.

But here my problem I dont understand why I have only 7 TB for this customer while in my performance tier I have this 7 TB and 5,5 in the capacity tier.

Hi ​@Stabz , the difference you are seeing is because you are using Copy mode in SOBR.

That means the same restore point exists in both Performance and Capacity tiers, so the total usage shows both.

But Cloud Repository Usage only shows the unique data used for billing.

To get a clear view per customer, try this PowerShell script from VeeamHub: 🔗 Get-VspcStorageUsage.ps1

It connects to your VSPC server and gives detailed usage for each repository and customer. You just need to provide your VSPC server address and credentials.

Hi ​@waqasali , thanks for your answers, hmm I will try to check this point ! 

I downloaded this script yesterday but I didn’t launch it yet. 

Hey
I'm trying to use the script, but unfortunately I can't get it to work.
I'm getting the following error message:
Write-Error: ERROR: Authorization Failed! Make sure the correct server and port were specified.
Invoke-RestMethod: C:\Sources\Get-VspcStorageUsage.ps1:238
Line |
 238 |  … $response = Invoke-RestMethod $url -Method 'POST' -Headers $headers - …
     |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | No connection could be made because the target machine actively refused it.

Propably I m missing something :D 

Make sure nothing is blocking outbound HTTPS traffic to the VSPC server. 

I mistakenly executed the script on the main VSPC server instead of the WebUI VSPC server. To facilitate automation, I also created a dedicated user account without MFA.

The script returned its first results, which is encouraging. However, the situation appears to be more complex than initially anticipated.

One key issue is that the cloud repository usage reported by VSPC reflects the total backup size for each tenant as seen in VBR, but without accounting for block cloning. This discrepancy makes it difficult to reconcile the figures with actual storage consumption.

In addition if the VSPC count the unique data used for billing… using the invoice provide by the VSPC is not viable.

hI ​@Stabz 

Did you check the comsunption againt the Veeam Calcular just in case?

Usint it you can configure several options, such as XFS/ReFS, copy/move (including the operational restore window) and more.
Try to simulate you envirenment using the Veeam Calculator, here is how it look like.
 

You can install on your machine or use it online https://www.veeam.com/calculators

Hope this help you to find out the consumption!!! :-)

hI ​@Stabz 

Did you check the comsunption againt the Veeam Calcular just in case?

Usint it you can configure several options, such as XFS/ReFS, copy/move (including the operational restore window) and more.
Try to simulate you envirenment using the Veeam Calculator, here is how it look like.
 

You can install on your machine or use it online https://www.veeam.com/calculators

 

Hope this help you to find out the consumption!!! :-)

Hey, we're using the Veeam Calculator to simulate and provide an estimate to our customer.
However, in my case, I need the actual values for invoicing purposes

After several exchanges with Veeam Support, here is the information I have available and can share with you:
 

All information in VPSC about VCC is collected directly from VCC server.

When it comes to overall storage usage, VCC saves this info in its DB, same as quotas. Most of this information can be found in VCC console -> Backup Infrastructure -> Backup Repositories.

Regarding quota usage, it gets calculated as a sum of backup sizes on all tiers:

- For local storage it checks file sizes in backup folders.

- For object storage VCC saves sizes of every offloaded backup file in DB and calculates usage based on saved values (backup_size in Backup.Model.Storages table).

VCC runs these calculations every time tenant’s job ends, additionally while the job is running it updates quota usages incrementally (every time data transfer agent requests new quota chunk).

Even though VCC does not show separate values, it still uses them to calculate quota usages. VSPC just re-uses the same values to create more detailed statistics and reports.

If you are using SOBR, VCC does not count backups copied to capacity tier in its quota usage calculations.

Please note that this applies only to “copy” mode, where Veeam creates copies of existing backups, consider this as an additional layer of protection against backup/storage corruption.

Tenants are not aware of backup placement or additional copies offloaded to object storage and cannot control this from their side. Basically, the main idea behind quota usage calculations to count backups sent by tenants as is, not accounting for any additional operations on VCC side.

Also, VSPC design limitations where it does not include blocks on S3 preserved due to immutability and block generation periods.

For example, if restore point gets removed by retention it gets excluded from quota calculations and tenant stops seeing this restore point. However, unique blocks may remain on S3 for a few days due to immutability, and VSPC does not include these blocks in calculations.
 

Hi ​@Stabz I’ve got your point, tahnk you for the explanation.